Skip to content
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

Controlled vocabularie to be used for adms:representationTechnique #137

Open
idevisser opened this issue Sep 26, 2024 · 2 comments
Open

Comments

@idevisser
Copy link

Why is in this profile an INSPIRE codelist http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType required instead of the widely used ISO19139 codelist MD_SpatialRepresentationTypeCode?
This INSPIRE codelist is not mandated by INSPIRE so if it must be used in geoDCAT explanation is required or allow to use the ISO19139 codelist.

@idevisser
Copy link
Author

same issue for the property:
dcat:hadRole with codelist http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole,
geodcatap:resourceType with codelist http://inspire.ec.europa.eu/metadata-codelist/ResourceType
geodcatap:topicCategory with codelist http://inspire.ec.europa.eu/metadata-codelist/TopicCategory

@jakubklimek
Copy link
Contributor

This is because GeoDCAT-AP is an RDF (Linked Data) representation of the metadata, where controlled vocabularies and their items are identified by their IRIs, which is not the case for ISO codelists. That is why there are RDF (Linked Data) based codelist counterparts published in the INSPIRE registry, which use IRIs for identification.

Content-wise, the http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType seems the same as the MD_SpatialRepresentationTypeCode, and the other corresponding codelists, should be identical, so there should be no issue in the mapping.

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

2 participants