-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
- https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/common/shape/odrl-shapes.ttl#L35 says that
odrl:targetshould be a literal with datatypexsd:anyURI. - This would make it impossible for
odrl:targetto point to the asset (dcat:Dataset) in the same JSONLD response. - In https://w3id.org/dspace/2024/1/context.json it's correctly defined as a URL (
@id) - https://docs.internationaldataspaces.org/ids-knowledgebase/dataspace-protocol/catalog/catalog.protocol#id-1.1-dcat-vocabulary-mapping states
Offers must NOT contain any explicit target attributes. The target of an Offer is the associated Dataset. (through
hasPolicy)
- The JSON schema https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2024-1/negotiation/message/schema/contract-schema.json#/definitions/Offer:
not: {required: ["odrl:target"]}
- But the EDC and Sovity implementations include
odrl:target, see - So the SHACL should forbid it, or define it as object prop with range
Dataset - And the JSONLD context should omit it
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels