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

Meaning of recommended properties on Standards #101

Open
jakubklimek opened this issue Mar 3, 2024 · 2 comments
Open

Meaning of recommended properties on Standards #101

jakubklimek opened this issue Mar 3, 2024 · 2 comments
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft webinar:2024-03-12 To be discussed in the 2024-03-12 webinar

Comments

@jakubklimek
Copy link
Contributor

Motivation
GeoDCAT-AP 2.0.0 specifies recommended properties for Standards:

However, even in GeoDCAT-AP examples, the recommended properties are not used, e.g. Example 25:

<http://www.opengis.net/def/crs/OGC/1.3/CRS84> a dct:Standard ;
  dct:identifier "urn:ogc:def:crs:OGC:1.3:CRS84"^^xsd:anyURI ;
  dct:title "CRS84"@en ;
  dct:type <http://inspire.ec.europa.eu/glossary/SpatialReferenceSystem> ;
  skos:inScheme <http://www.opengis.net/def/crs/OGC> ;
  skos:prefLabel "CRS84"@en .

Questions

  1. What is the meaning of recommended here? Should the properties be used with all standards mentioned in GeoDCAT-AP? e.g. with http://www.opengeospatial.org/standards/wms in the following example?
[] a dcat:DataService;
    dct:conformsTo <http://www.opengeospatial.org/standards/wms> .
  1. Should they be used only for standards for which there are no URIs?
  2. Is there a registry of standards in which the standards are documented using the recommended properties?

Possible proposals

  1. Move recommended properties to optional properties for Standards
@jakubklimek jakubklimek added feedback-requested Community feedback requested release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 webinar:2024-03-12 To be discussed in the 2024-03-12 webinar next-webinar To be discussed in the next webinar labels Mar 3, 2024
@jakubklimek jakubklimek added status:postponed Decision postponed and removed next-webinar To be discussed in the next webinar labels Mar 21, 2024
@jakubklimek
Copy link
Contributor Author

Voting on this issue postponed to give the community more time to discuss it here in GitHub.

@jakubklimek jakubklimek removed the feedback-requested Community feedback requested label Apr 25, 2024
@jakubklimek
Copy link
Contributor Author

Since no additional feedback was received, this is resolved in sync with #109 - all properties for supporting entities, including Standards, will be optional.

@jakubklimek jakubklimek added status:fixed Resolution applied in draft and removed status:postponed Decision postponed labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft webinar:2024-03-12 To be discussed in the 2024-03-12 webinar
Projects
None yet
Development

No branches or pull requests

1 participant