The Dataspace Protocol is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data in a data space
While, generally speaking, using RDF properties in a way violating their rdfs:domains isn't forbidden, it still shouldn't be encouraged. The puml for the Catalog response looks like this:
However, it should only point to an IRI that has rdf:typedcterms:Standard which would be an object in the json world. Same issue seems to occur with dcat:endpointDescription
Closing as I overlooked that the value of dct:conformsTo is coerced into an object by the remote context https://w3id.org/dspace/2024/1/context.json. Same for dcat:endpointDescription
While, generally speaking, using RDF properties in a way violating their
rdfs:domain
s isn't forbidden, it still shouldn't be encouraged. The puml for theCatalog
response looks like this:https://github.com/International-Data-Spaces-Association/ids-specification/blob/63e5a401192336177f1d547ebd1f8e8f6f129269/catalog/message/diagram/catalog.puml#L15
However, it should only point to an IRI that has
rdf:type
dcterms:Standard
which would be an object in the json world. Same issue seems to occur withdcat:endpointDescription