- From: Joel Sahleen via GitHub <noreply@w3.org>
- Date: Tue, 23 Dec 2025 21:05:16 +0000
- To: public-i18n-archive@w3.org
jsahleen has just created a new issue for https://github.com/w3c/i18n-activity: == Base direction and lang tag requirement in SHACL shape and constraint messages == This is in reference to the following section of the SHACL 1.2 Core specification. 3.1.5 Declaring Messages for a Shape or Constraint https://w3c.github.io/data-shapes/shacl12-core/#message The SHACL 1.2 Core specification recommends the use of language tags in the declaration SHACL messages for shapes or constraints but does not require them. It does not add anything about identifying the base direction of the message literal. > Shapes can have values for the property sh:message. The values of sh:message are either xsd:string literals or literals with a language tag. A subject should not have more than one value for sh:message with the same language tag. There is no official RDF recommendation on base direction for literals, but I have found the following internal document. RDF Literals and Base Directions https://w3c.github.io/rdf-dir-literal/ It might be worth adding some language to the specification about base directionality in literals which explains the lack of official guidance and recommends a strategy based on the discussion above. It should also be considered whether a language tag should be required in all cases, even if the message is not intended to be multilingual, or if there is some way to set the language tag for all such messages at a higher level. Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/2062 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 December 2025 21:05:17 UTC