fix: fiori docs to reflect cds10 reality (#2628)

Co-authored-by: Daniel Hutzel <daniel.hutzel@sap.com>

Author: johannes-vogel

.github/CODEOWNERS

@@ -2,15 +2,15 @@
 # We start with defining ownership globally and later on can get more granular.
 
 # General content
-* @renejeglinsky
+* @renejeglinsky @danjoa
 
-node.js/ @smahati @renejeglinsky
-java/    @smahati @renejeglinsky
+node.js/ @smahati @renejeglinsky @danjoa
+java/    @smahati @renejeglinsky @danjoa
 
 # Infra
 .github/    @chgeo @swaldmann
-.vitepress/ @chgeo @swaldmann
-public/     @chgeo @swaldmann
+.vitepress/ @chgeo @swaldmann @danjoa
+public/     @chgeo @swaldmann @danjoa
 
 # allow dependencies updates through renovate w/o code owners
 package.json

guides/uis/fiori.md

@@ -307,27 +307,24 @@ Draft locks are not applied when creating drafts for new entities, as there is n
 Fiori clients send the following HTTP requests for draft operations:
 
 ```php:line-numbers [Requests to <i>draft</i> data]
-POST   /Foo/draftNew                                //> NEW
+POST   /Foo                                         //> NEW
 POST   /Foo(ID,IsActiveEntity=true)/draftEdit       //> EDIT
 GET    /Foo(ID,IsActiveEntity=false)                //> READ
 PATCH  /Foo(ID,IsActiveEntity=false) {...}          //> PATCH
 POST   /Foo(ID,IsActiveEntity=false)/draftActivate  //> SAVE
 DELETE /Foo(ID,IsActiveEntity=false)                //> DISCARD
 ```
 
- The key parameter `IsActiveEntity=false` addresses draft data, with the exception of `draftNew`, which is an _unbound_ action, and `draftEdit` for semantic reasons.
-
-::: details `draftNew` actions are used <Since package="@sap/cds" version="v10" /> and <Since package="CAP Java" version="v5" />
-Previously, regular `POST /Foo` requests without an `IsActiveEntity` parameter created new drafts, which caused ambiguities with requests to active data.
-Can be disabled with <Config>cds.fiori.draft_new_action: false</Config>.
-:::
+The key parameter `IsActiveEntity=false` addresses draft data, with the exception of the empty POST and `draftEdit` for semantic reasons.
 
 ::: details Full HTTP requests ...
 The requests above are abbreviated for clarity. The actual HTTP requests include the service path, content-type headers, and JSON bodies as shown below.
 
 ```http
-POST /odata/v4/TravelService/Travels/draftNew
+POST /odata/v4/TravelService/Travels
 Content-Type: application/json
+
+{}
 ```
 ```http
 POST /odata/v4/TravelService/Travels(ID=a11fb6f1-36ab-46ec-b00c-d379031e817a,IsActiveEntity=true)/draftEdit
@@ -364,15 +361,21 @@ While this was always possible in CAP Java before, it's available for CAP Node.j
 
 #### Draft-agnostic Requests
 
-Taking this further, `IsActiveEntity=true` is assumed by default, so clients that are unaware of drafts or don't need to handle them can ignore all draft-specific requests and parameters:
+Taking this further, through <Config>cds.fiori.draft_new_action: true</Config> `IsActiveEntity=true` is assumed by default, so clients that are unaware of drafts or don't need to handle them can ignore all draft-specific requests and parameters:
 
 ```php:line-numbers [Draft-agnostic requests to <i>active</i> data]
+// creation of active instances
 POST   /Foo            //> CREATE
 GET    /Foo(ID)        //> READ
 PATCH  /Foo(ID) {...}  //> UPDATE
 DELETE /Foo(ID)        //> DELETE
+// creation of draft instances
+POST   /Foo/draftNew   //> CREATE new draft [!code ++]
+...
 ```
 
+The previously used `POST /Foo` requests without an `IsActiveEntity` parameter to create new drafts is now replaced by the collection bound action `draftNew` to resolve the ambiguities with requests to active data.
+
 ::: details Available for CAP Node.js <Since package="@sap/cds" version="v10" /> – not yet for CAP Java
 Draft-agnostic requests as above assume `IsActiveEntity=true` by default for all requests that don't explicitly specify it.
 This was possible in CAP Node.js, but not in CAP Java, which is still bound by the [*Olingo*](https://olingo.apache.org) library. For CAP Java, explicitly add `IsActiveEntity=true` as a key parameter to address active data

node.js/core-services.md

@@ -396,18 +396,19 @@ var srv.options : { //> from cds.requires config
 
 
 
-### . entities {.property alt="The following documentation on actions also applies to entities. "}
-### . events {.property alt="The following documentation on actions also applies to events. "}
 ### . actions {.property}
+### . events {.property}
+### . types {.property}
+### . entities {.property}
 ###### srv-entities
 
 ```tsx
-var srv.entities/events/actions : Iterable <{
+var srv.entities/events/actions/types : Iterable <{
   name : CSN definition
 }>
 ```
 
-These properties provide convenient access to the CSN definitions of the *entities*, *events* and *actions* (incl. *functions*) exposed by this service. They return instances of [`LinkedDefinitions`](cds-reflect#iterable) which you can use in all of these ways:
+These properties provide convenient access to the CSN definitions of the *entities*, *types*, *events*, and *actions* (incl. *functions*) exposed by this service. They return instances of [`LinkedDefinitions`](cds-reflect#iterable) which you can use in all of these ways:
 
 ```js
 // Assumed `this` is an instance of cds.Service