8000 IRIs for dct:Standards ? · Issue #417 · SEMICeu/DCAT-AP · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Open
barthanssens opened this issue Feb 28, 2025 · 2 comments
Open

IRIs for dct:Standards ? #417

barthanssens opened this issue Feb 28, 2025 · 2 comments

Comments

@barthanssens
Copy link

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/>

@bertvannuffelen
Copy link
Contributor

@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.

@EmidioStani
Copy link
Member
EmidioStani commented Mar 4, 2025

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.
Personally I would expect the one with a version to be more precise on the structure expected by the distribution, definitely not the URL from which download the file extension.

I see the Profile vocabulary a potential candidate where the main class is dct:Standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
0