Fix issues in management api walkthrough (#2578)

Signed-off-by: Lars Geyer-Blaumeiser <lars.blaumeiser@cofinity-x.com>

Author: lgblaumeiser

docs/usage/management-api-walkthrough/04_catalog.md

@@ -174,7 +174,7 @@ The returned payload is a `dcat:Catalog` as specified by the DSP version used in
         "action": "use",
         "constraint": {
           "leftOperand": "FrameworkAgreement",
-          "operand": "eq",
+          "operator": "eq",
           "rightOperand": "DataExchangeGovernance:1.0"
         },
         "prohibition": [],

docs/usage/management-api-walkthrough/05_contractnegotiations.md

@@ -34,9 +34,9 @@ Content-Type: application/json
     "@id": "{{OFFER_ID}}",
     "target": "{{ASSET_ID}}",
     "assigner": "{{PROVIDER_IDENTIFIER}}",
-    "permission": {{OFFER_ODRL_PERMISSION}},
-    "prohibition": {{OFFER_ODRL_PROHIBITION}},
-    "obligation": {{OFFER_ODRL_OBLIGATION}}
+    "permission": [],
+    "prohibition": [],
+    "obligation": []
   },
   "callbackAddresses": [
     {
@@ -61,7 +61,9 @@ section which refers to an existing published context definition.
 - `protocol` is the providers' supported protocol
 - In the `policy` section, the Data Consumer specifies the Data Offer for the negotiation. As there may be multiple
   Data Offers for the same DataSet, the Data Consumer must choose one.
-  It must hold an identical copy of the Data Offer's contract policy as provided via the catalog-API in the `odrl:hasPolicy` field plus:
+  It must hold an identical copy of the Data Offer's contract policy as provided via the catalog-API in the `odrl:hasPolicy`
+  field. Especially the `permission`, `prohibition` and `obligation` fields must contain the exact same `odrl` clauses as
+  found in the offer. In addition, two more properties are required:
     - `assigner` must hold the identifier of the Provider (BPN OR DID, as returned in the catalog response)
     - `target` must be the id of the EDC-Asset/dcat:DataSet that the offer was made for.
 - `callbackAddresses` is a list of Consumer-side endpoints that the Provider's Data Plane writes events to.

docs/usage/management-api-walkthrough/06_transferprocesses.md

@@ -42,13 +42,11 @@ Content-Type: application/json
     "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
   },
   "@type": "TransferRequest",
-  "assetId": "{{ASSET_ID}}",
   "contractId": "{{CONTRACT_AGREEMENT_ID}}",
   "counterPartyAddress": "{{CONNECTOR_ADDRESS}}",
   "dataDestination": {
     "type": "<supported-transfer-type>"
   },
-  "privateProperties": {},
   "protocol": "dataspace-protocol-http:2025-1",
   "transferType": "HttpData-PULL",
   "callbackAddresses": [
@@ -68,7 +66,6 @@ Content-Type: application/json
 }
 ```
 
-- `assetId` is the id of the [asset](01_assets.md) that a transfer process should be triggered for.
 - `counterPartyAddress` is the DSP-endpoint of the Data Provider (usually ending on /api/v1/dsp).
 - `contractId` represents the Contract Agreement that the Provider and Consumer agreed on during the [Contract Negotiation](05_contractnegotiations.md)
   phase.