-
Notifications
You must be signed in to change notification settings - Fork 6
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
Reference system mapped to dct:conformsTo
#94
Labels
alignment:style-guide
SEMIC Style Guide alignment related
release:3.0.0
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
Posponed until the next webinar |
Related issue / information: #115 |
As an applicable example, in Flanders we refer to the standard accompanied by a unique identifier. An example <dct:conformsTo>
<dct:Standard rdf:about="https://www.opengis.net/def/crs/EjjPSG/0/5710">
<dct:title>Ostend height</dct:title>
<dct:identifier>https://www.opengis.net/def/crs/EPSG/0/5710</dct:identifier>
<dct:type rdf:resource="http://inspire.ec.europa.eu/glossary/SpatialReferenceSystem"/>
</dct:Standard>
</dct:conformsTo> |
A subproperty will be created. |
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
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
Problem statement
In GeoDCAT-AP 2.0.0, the Reference system property on
is mapped to the generic
dct:conformsTo
, which is also present on the same classes, both havingdct:Standard
as range.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.
The reference system usage note says e.g.
This property SHOULD be used to specify the reference system used in the Catalogue. Spatial reference systems SHOULD be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by OGC [OGC-EPSG].
The
dct:conformsTo
usage note says e.g.This property refers to an implementing rule or other specification.
Proposal
Either
dct:conformsTo
to make it clear that reference systems are one kind of the Standards expected as values here, ordct:conformsTo
geodcatap:referenceSystem
and attach the separate usage notes there.The text was updated successfully, but these errors were encountered: