-
Notifications
You must be signed in to change notification settings - Fork 24
IRIs for dct:Standards ? #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@barthanssens harmonisation of this is a very complex topic. Some of the standards are only accessible via a paywall. Most of them are not machine readable described. And sometimes users reference copies instead of the original source url. E.g. I found W3C standards on Zenodo and those DOIs were used in the references. Sometimes even more detailed identifiers are needed than the standardisation documents require. In here https://github.com/Informatievlaanderen/OSLOthema-metadataVoorServices/blob/master/codelijsten/protocol.ttl you find a list of "protocols" (technical data standards, documented with extra metadata derived from the INSPIRE context) used in Flanders to denote INSPIRE and other services their technical conformance. This can be an inspiration for a common protocol list with the minimal metadata descriptions. |
Hello @barthanssens , that is an interesting point, especially in the context of the Semantic Registry. Indeed by looking at data.europa.eu, at the dct:conformsTo relation in a dcat:Distribution, it is possible to note examples like:
Sometimes it is indicating the version, sometimes not and in some case there is a file associated. In other cases I have seen links to files such as json, .xsd, .xml, .trig, .zip. Therefore it would be nice to agree on the expected value for dct:conformsTo. I see the Profile vocabulary a potential candidate where the main class is dct:Standard. |
Is there a common way to generate IRIs for Idcterms:conformsTo / dct:Standard, or an EU Publication Office Authority table (much like media types etc) ?
Many (often INSPIRE-related) datasets and services adhere to the same small set of ISO standards (and maybe others), so instead of having blank nodes with a dcterms:description for each and every dataset, it would be nicer (and easier to query) to use an IRI.
I assume one can just (ab)use
<http://www.isotc211.org/2005/gmd>
or<https://standards.iso.org/iso/19115/-3/>
The text was updated successfully, but these errors were encountered: