Closed arnoweiss closed 4 months ago
Hi @arnoweiss Thank you for raising this issue. I was not aware of this change. We will fix this ASAP.
More information about the standard can be found in section 3.1.4 EDC Data Asset Structure of CX-0002
Fixed in https://github.com/eclipse-tractusx/item-relationship-service/pull/647
ready for testing @ds-kgassner
successfully tested - approved from my side.
LGFM. PO acceptance in behalf of @jzbmw
Description
Since R23-12, standard CX-0002 has mandated the use of the property
http://purl.org/dc/terms/type
to be used as signal the type of adcat:Dataset
in adcat:Catalog
. In an EDC, the corresponding resource must be added during with thePOST /v3/assets
call, for instance like this [1]. Since its introduction, the propertyasset:prop:type
was due for removal with the next breaking release.Current behaviour
The IRS relies on the deprecated and (starting R24-05) optional property
asset:prop:type
[2].Expected behavior
The IRS (as a Consumer application) should use the Property
http://purl.org/dc/terms/type
to discover Digital Twin Registries (and Submodels, despite not strictly necessary) in a Provider's catalog. This can be done, for instance, via EDC-Catalog-Filtering, see example [3]. Please note that this property holds an object with an@id
property which is why the filter is nested.If the IRS looks for either or both is an implementation detail. What matters is that Data Providers, adhering only to the current version of the standard are found by the IRS.
[1]
POST /v3/assets
[2] https://github.com/eclipse-tractusx/item-relationship-service/blob/31ed8b8b38996640ec1d39d921c48bda434abad0/irs-edc-client/src/main/java/org/eclipse/tractusx/irs/edc/client/asset/EdcAssetService.java#L156
[3]
POST /catalog/request