You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the geodcat-ap-SHACL.ttl file the following is declared: @prefix dc: <http://purl.org/dc/terms/> .
typically de dc: prefix is reserved for http://purl.org/dc/elements/1.1/
while dcterms: is the most commonly used prefix for 'http://purl.org/dc/terms/`
The use of a conflicting prefix causes issues with the use of python rdflib and pyshacl for validation.
While I would prefer dcterms as prefix, I see the xslt is declaring dct: which is used inside the uri's of the nodeShapes as well.
Using dct would solve the conflict with rdflib/pyshacl as well.
The text was updated successfully, but these errors were encountered:
This is an issue from the GeoDCAT-AP 3.0.0 pilot.
In the geodcat-ap-SHACL.ttl file the following is declared:
@prefix dc: <http://purl.org/dc/terms/> .
typically de
dc:
prefix is reserved forhttp://purl.org/dc/elements/1.1/
while
dcterms:
is the most commonly used prefix for 'http://purl.org/dc/terms/`The use of a conflicting prefix causes issues with the use of python rdflib and pyshacl for validation.
While I would prefer dcterms as prefix, I see the xslt is declaring dct: which is used inside the uri's of the nodeShapes as well.
Using dct would solve the conflict with rdflib/pyshacl as well.
The text was updated successfully, but these errors were encountered: