[data-shapes] How to handle and/or report IRI values of `sh:annotationProperty` that would lead to invalid SPARQL variable? (#378)

ajnelson-nist has just created a new issue for https://github.com/w3c/data-shapes:

== How to handle and/or report IRI values of `sh:annotationProperty` that would lead to invalid SPARQL variable? ==
One of those niche corner cases: `http://example.org/☃` ([snowman, code point U+2603](https://www.compart.com/en/unicode/U+2603)) is a valid IRI ([RFC 3987, Section 2.2](https://datatracker.ietf.org/doc/html/rfc3987#section-2.2), grammar rule `ucschar`).  `☃` cannot be a SPARQL variable name (SPARQL grammar rule [`VARNAME`](https://www.w3.org/TR/sparql11-query/#rVARNAME)).  Do we need to leave a reminder here of SPARQL's `VARNAME` grammar rule?  If someone does try some unicode IRI---probably not an emoji , but perhaps there would be non-Latin use cases---and it wouldn't work in SPARQL, should we specify that it's the SHACL processor's responsibility to catch this at shapes graph load-time; or, instead warn the shapes graph authors that incompatible IRIs would likely be reported by the SPARQL engine (i.e., SHACL delegating to SPARQL)?  Note the latter case leaves the shapes graph _users_ scratching their heads if the shapes graph _authors_ don't see the warning.

_Originally posted by @ajnelson-nist in https://github.com/w3c/data-shapes/pull/330#discussion_r2084311095_
            

Please view or discuss this issue at https://github.com/w3c/data-shapes/issues/378 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 May 2025 10:56:04 UTC