loosen up xsd:string requirements too allow rdf:langString too
marc-portier opened this issue · 0 comments
marc-portier commented
The current shapes.ttl is often strictly requiring a datatype of xsd:string in places where rdf:langstring feels equally ok.
For instances the many occurrences of dct:description properties fit this observation for sure.
As a consequence validation fails for a perfectly acceptable (and arguably even more open-accessible, globally inviting, and thus recommended?) case like this:
dct:description "Your description here, please."@en ;
dct:description "Votre description ici, svp"@fr ;
dct:description "Uw beschriJving hier, aub"@nl ;
If you all agree I would like us to
- list other candidates for thoughtful consideration
- discuss and agree on those
- provide a pull request to loosen up the constraints about these through replacing several:
sh:datatype xsd:string ;
with:
sh:or ( [ sh:datatype xsd:string ; ]
[ sh:dataype rdf:langString ; ] ) ;
thx for considering.