Definition: A description of the services available via the end-points, including their operations, parameters etc.
Range: rdfs:Resource
Usage note: The endpoint description gives specific details of the actual endpoint instances, while dcterms:conformsTo is used to indicate the general standard or specification that the endpoints implement.
And while the second usage note does allow for a text representation, it is only as a last resort if other formal representations are not available. I'd argue for it to be compliant to the DCAT-AP spec to allow for interoperability with other EU portals.
Usage note: An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description [OpenAPI], an OGC GetCapabilities response [WFS], [ISO-19142], [WMS], [ISO-19128], a SPARQL Service Description [SPARQL11-SERVICE-DESCRIPTION], an [OpenSearch] or [WSDL20] document, a Hydra API description [HYDRA], else in text or some other informal mode if a formal representation is not possible.
kburger
commented
3 months ago
As discussed in https://github.com/Health-RI/health-ri-metadata/pull/112, the
dcat:endpointDescriptionshould point to anrdfs:Resource, where the current model has it as ardfs:Literal. According to the spec [0][1]:And while the second usage note does allow for a text representation, it is only as a last resort if other formal representations are not available. I'd argue for it to be compliant to the DCAT-AP spec to allow for interoperability with other EU portals.
[0] https://www.w3.org/TR/vocab-dcat-3/#Property:data_service_endpoint_description [1] https://semiceu.github.io/DCAT-AP/releases/3.0.0/#DataService.endpointdescription