Please add your implementation report, or a link to it, to this issue.
This endpoint has a rich example of DCAT embedded in the header.
It includes examples of the following at-risk elements:
:accessService:bbox:hadRoleprov:wasGeneratedBy:spatialResolutionInMeters:endpointDescription:endpointURL:servesDatasetprov:qualifiedAttribution...and that RDF can also be returned as pure RDF, i.e. not embedded in anything, by using Conneg or this URI with query strings:
LinkedPipes DCAT-AP Viewer (currently used as part of Czech National Open Data catalog) is adding support for DCAT2 at the moment. The range of newly supported properties will still grow. So far, it supports:
packageFormat, compressFormat, DataService, endpointURL, servesDataset and endpointDescription.
LinkedPipes DCAT-AP Forms (currently used as part of Czech National Open Data catalog) is adding support for DCAT2 at the moment. The range of newly supported properties will still grow. So far, it supports: packageFormat, compressFormat, DataService, endpointURL, accessService and endpointDescription. This can already be seen deployed in development environment - still under development.
@dr-shorthair , @nicholascar , @jakubklimek , thanks for your feedback!
The implementation you reported are included in the DCAT2 implementation report - see PR https://github.com/w3c/dxwg/pull/1138
The DCAT2 implementation report has been published:
https://w3c.github.io/dxwg/dcat-implementation-report/
I think we can close this issue.
Closing.
Most helpful comment
The DCAT2 implementation report has been published:
https://w3c.github.io/dxwg/dcat-implementation-report/
I think we can close this issue.