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:
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:
If you all agree I would like us to
with:
thx for considering.