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

Revise ambiguous dct:type mapping on Data Service #77

Closed
jakubklimek opened this issue Feb 9, 2024 · 3 comments
Closed

Revise ambiguous dct:type mapping on Data Service #77

jakubklimek opened this issue Feb 9, 2024 · 3 comments
Labels
alignment:style-guide SEMIC Style Guide alignment related release:3.0.0-oct2024 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-03-12 To be discussed in the 2024-03-12 webinar webinar:2024-04-23 To be discussed in the 2024-04-23 webinar

Comments

@jakubklimek
Copy link
Contributor

jakubklimek commented Feb 9, 2024

Problem statement

In GeoDCAT-AP 2.0.0 dct:type on Data Service is used in three different contexts.

  1. service category with "Classification of spatial data services" code list
  2. service type with "Spatial data service types" code list
  3. type with "Resource types" code list. (this one also appears in Dataset)

This makes correct assignment of usage notes, labels and the required code lists rather difficult, as well as consequent validation e.g. via SHACL.
The current approach is not in line with the profiling guidelines established in the context of the SEMIC Style Guide property reuse guideline Reuse of a property with terminological adaptations and Reuse of a property with semantic adaptations.
Also, the approach becomes even more problematic in a cross-profile environment where incompatible requirements can be easily made.

Proposal

Introduce subproperties of dct:type

  1. geodcatap:serviceCategory for "Classification of spatial data services" code list
  2. geodcatap:serviceType for "Spatial data service types" code list
  3. geodcatap:resourceType for "Resource types" code list with the domain of dcat:Resource to accomodate both for Datasets and Data Services

This approach is in line with the profiling guidelines established in the context of the SEMIC Style Guide property reuse guideline Reuse of a property with terminological adaptations and Reuse of a property with semantic adaptations.
If interoperability is a concern, a data publisher can always easily materialize the subPropertyOf inference and replace the subproperties with dct:type.

@jakubklimek jakubklimek added release:3.0.0-oct2024 Actively being worked on for GeoDCAT-AP 3.0.0 alignment:style-guide SEMIC Style Guide alignment related labels Feb 9, 2024
@jakubklimek jakubklimek added type:improvement Improvement of current handling of a problem webinar:2024-03-12 To be discussed in the 2024-03-12 webinar next-webinar To be discussed in the next webinar labels Mar 8, 2024
@jakubklimek jakubklimek added the webinar:2024-04-23 To be discussed in the 2024-04-23 webinar label Mar 21, 2024
@jakubklimek
Copy link
Contributor Author

Posponed until the next webinar

@jakubklimek jakubklimek added status:postponed Decision postponed feedback-requested Community feedback requested labels Mar 21, 2024
@joachimnielandt
Copy link

For info, in Flanders we are mapping to a subproperty of dct:type (related to #78 ):

Eigenschap URI GeoDCAT-AP GeoDCAT-AP Vlaanderen
servicetype http://data.vlaanderen.be/ns/metadata-dcat#servicetype dct:type subproperty van dct:type
servicecategorie http://data.vlaanderen.be/ns/metadata-dcat#servicecategorie dct:type subproperty van dct:type

@VeronikaKusova
Copy link

We had a discussion about this issue (Czech Office for Surveying, Mapping and Cadastre and Czech Environmental Information Agency) and we support the proposal - to create new subproperties of dct:type.

@jakubklimek jakubklimek added status:resolution-provided Resolution statement present, not yet applied in draft and removed next-webinar To be discussed in the next webinar status:postponed Decision postponed labels Apr 25, 2024
@jakubklimek jakubklimek added status:fixed Resolution applied in draft and removed feedback-requested Community feedback requested status:resolution-provided Resolution statement present, not yet applied in draft labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alignment:style-guide SEMIC Style Guide alignment related release:3.0.0-oct2024 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-03-12 To be discussed in the 2024-03-12 webinar webinar:2024-04-23 To be discussed in the 2024-04-23 webinar
Projects
None yet
Development

No branches or pull requests

3 participants