The Information Model of the International Data Spaces implements the IDS reference architecture as an extensible, machine readable and technology independent data model.
We have the use case to directly consume IDS Endpoints based on the Self-Description. While the IM already announces Endpoints (hasEndpoint), the endpoint itself does not state which IDS Binding or IDS Protocol specification it supports. Therefore, I propose to add the following property and enum:
ids:apiSpecifiation a owl:ObjectProperty ;
rdfs:label "follows API specification" ;
rdfs:comment "Declares which endpoint specification is supported by this IDS endpoint." ;
rdfs:domain ids:Endpoint ;
rdfs:range ids:IdsProtocolSpecification ;
.
ids:IdsProtocolSpecification a owl:Class ;
rdfs:label "Protocol Specification" ;
rdfs:comment "List of all defined Protocol Specifications, for instance IDS-CP or IDS over Multipart."@en ;
.
idsc:IDS-REST a ids:IdsProtocolSpecification ;
rdfs:label "IDS REST" ;
rdfs:comment "The REST specification of the IDS interactions."@en ;
rdfs:seeAlso <https://github.com/International-Data-Spaces-Association/path/to/ids/rest/spec/> ;
.
idsc:IDS-CP a ids:IdsProtocolSpecification ;
rdfs:label "IDS-CP" ;
rdfs:comment "The IDS-CP specification of the IDS interactions."@en ;
rdfs:seeAlso <https://github.com/International-Data-Spaces-Association/path/to/idscp/spec/> ;
.
idsc:QUERY a ids:IdsProtocolSpecification ;
rdfs:label "Query" ;
rdfs:comment "Queries conforming to IDS specifications."@en ;
rdfs:seeAlso <https://www.w3.org/TR/sparql11-overview/> ;
.
idsc:MULTIPART a ids:IdsProtocolSpecification ;
rdfs:label "IDS over Multipart" ;
rdfs:comment "The Multipart Messages implementation of the IDS interactions."@en ;
rdfs:seeAlso <https://github.com/International-Data-Spaces-Association/path/to/multipart/spec/> ;
.
We have the use case to directly consume IDS Endpoints based on the Self-Description. While the IM already announces Endpoints (
hasEndpoint
), the endpoint itself does not state which IDS Binding or IDS Protocol specification it supports. Therefore, I propose to add the following property and enum: