chore(protocol): switch default to /api/v1/dsp

Author: wolf4ood

charts/tractusx-connector-azure-vault/values.yaml

@@ -110,7 +110,7 @@ controlplane:
       # -- port for incoming api calls
       port: 8084
       # -- path for incoming api calls
-      path: /api/v1/ids
+      path: /api/v1/dsp
     # -- metrics api, used for application metrics, must not be internet facing
     metrics:
       # -- port for incoming api calls

charts/tractusx-connector-memory/values.yaml

@@ -112,7 +112,7 @@ runtime:
       # -- port for incoming api calls
       port: 8084
       # -- path for incoming api calls
-      path: /api/v1/ids
+      path: /api/v1/dsp
     # -- observability api with unsecured access, must not be internet facing
     observability:
       # -- port for incoming API calls

charts/tractusx-connector/values.yaml

@@ -110,7 +110,7 @@ controlplane:
       # -- port for incoming api calls
       port: 8084
       # -- path for incoming api calls
-      path: /api/v1/ids
+      path: /api/v1/dsp
     # -- metrics api, used for application metrics, must not be internet facing
     metrics:
       # -- port for incoming api calls

docs/migration/Version_0.3.4_0.4.0.md

@@ -1,4 +1,4 @@
-# Migration from 0.3.3 to 0.3.4
+# Migration from 0.3.3 to 0.4.0
 
 ## Switching to DSP
 
@@ -10,9 +10,16 @@ From the Tractus-X EDC perspective this causes breaking changes in the following
   The old Management API is now deprecated and is **not** tested for compliance. Please upgrade using the `/v2/` path
   for every endpoint, e.g. `<PATH>/management/v2/assets`. Please also refer to
   the [EDC OpenAPI spec](https://app.swaggerhub.com/apis/eclipse-edc-bot/management-api/0.0.1-SNAPSHOT#/).
+  An updated postman collection with the `v2` flow is available [here](../development/postman/collection.json)
+
 - modules: all `*ids*` modules are deprecated and cannot be used anymore. Please migrate over
   to `org.eclipse.edc:dsp:0.0.1-milestone-9`.
 
+- path: the default protocol path is now `/api/v1/dsp` instead of `/api/v1/ids`
+
+- `edc.participant.id`: new mandatory configuration for the participant id in the dataspace. (BPN number). 
+  It's configured via mandatory property in the charts with object ```yaml participant: id: "id"```. 
+
 **Please note that this is not a complete documentation of the DSP Protocol, please refer to
 the [official documentation](https://docs.internationaldataspaces.org/dataspace-protocol/overview/readme)**
 
@@ -27,3 +34,62 @@ The Business tests were brittle, consumed a lot of resources and were quite cumb
 
 Since the old Control-Plane-Adapter is incompatible with DSP, a new iteration was created.
 **Due to time constraints with this release documentation for this feature will to be published subsequently**
+
+
+## Other changes
+
+- When using the EDR [HttpDynamicReceiverExtension](https://github.com/eclipse-edc/Connector/tree/main/extensions/control-plane/transfer/transfer-pull-http-dynamic-receiver) in the transfer process initiation
+  the properties for configuring the receiver on single transfer process has been changed to:
+  
+  ```json
+  "privateProperties": {
+        "receiverHttpEndpoint": "{{BACKEND_SERVICE}}"
+  }
+  ```
+  instead of:
+
+  ```json
+  "properties": {
+        "receiver.http.endpoint": "{{BACKEND_SERVICE}}"
+  }
+  ```
+
+
+## New Catalog 
+
+The DSP catalog is expressed as [DCat Catalog](https://www.w3.org/TR/vocab-dcat-3/), when querying the catalog a response like this will return:
+
+```json
+{
+    "@id": "5a3207ae-bd0d-4a3b-bc8a-05adfbe75d95",
+    "@type": "dcat:Catalog",
+    "dcat:dataset": {
+        "@id": "e6279569-17a9-4ba3-9401-a8ae4100e4eb",
+        "@type": "dcat:Dataset",
+        "odrl:hasPolicy": {
+            "@id": "2:1:535def6e-8321-4c0e-a595-aabdd9c18eed",
+            "@type": "odrl:Set",
+            "odrl:permission": [],
+            "odrl:prohibition": [],
+            "odrl:obligation": [],
+            "odrl:target": "1"
+        },
+        "dcat:distribution": [
+         ...
+        ],
+        "edc:description": "Product EDC Demo Asset",
+        "edc:id": "1"
+    },
+    "dcat:service": {
+      ...
+    },
+    "edc:participantId": "participantId",
+    "@context": {
+    }
+} 
+```
+
+When starting a new contract negotiation for an asset:
+
+- the `@id` of `odrl:hasPolicy` object should be passed in the `offerId` field
+- the `edc:participantId` should be passed in the `providerId` and `connectorId` fields. `connectorId` it's still needed for backward compatibility and it will probably be removed in the next versions.

edc-extensions/postgresql-migration/src/main/resources/org/eclipse/tractusx/edc/postgresql/migration/contractdefinition/V0_0_6__Alter_ContractDefinition_Rename_selector_expression.sql

@@ -1,5 +1,5 @@
 --
---  Copyright (c) 2022 Mercedes-Benz Tech Innovation GmbH
+--  Copyright (c) 2023 Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
 --
 --  This program and the accompanying materials are made available under the
 --  terms of the Apache License, Version 2.0 which is available at
@@ -8,7 +8,7 @@
 --  SPDX-License-Identifier: Apache-2.0
 --
 --  Contributors:
---       Mercedes-Benz Tech Innovation GmbH - EDC Snapshot 20221201 Update
+--       Bayerische Motoren Werke Aktiengesellschaft (BMW AG) - initial API and implementation
 --
 
 -- add columns