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

loosen up xsd:string requirements too allow rdf:langString too #548

Open
marc-portier opened this issue Jul 29, 2021 · 0 comments
Open

loosen up xsd:string requirements too allow rdf:langString too #548

marc-portier opened this issue Jul 29, 2021 · 0 comments

Comments

@marc-portier
Copy link

marc-portier commented Jul 29, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant