Re: [SHACL] sh:prefixes

2023-03-01 Thread Andy Seaborne
Could you add it to the formal errata list? It does not appear to be listed at https://github.com/w3c/data-shapes/issues?q=is%3Aissue+is%3Aopen+label%3AErrata It helps make the case for work to be done. > go into that document and fix it The SHACL CG can publish a revised document as a CG

Re: [SHACL] sh:prefixes

2023-02-28 Thread Holger Knublauch
I know, almost everybody stumbles there. It was bad editing by the editor :) Unfortunately I cannot just go into that document and fix it. That's the bane of these formal specs, and why many people get work done quicker outside of such formal processes. Holger > On 28 Feb 2023, at 1:24 pm,

Re: [SHACL] sh:prefixes

2023-02-28 Thread Martynas Jusevičius
Thanks Holger, that is the case :) The "sh:prefixes ex:" in the SHACL spec was somewhat confusing without context, because it looks like a Turtle prefix declaration. This works: :prefixes sh:declare [ sh:prefix "skos" ; sh:namespace "http://www.w3.org/2004/02/skos/core#"^^xsd:anyURI ; ]

Re: [SHACL] sh:prefixes

2023-02-28 Thread Holger Knublauch
I suspect this is another instance of the common misunderstanding: the @prefix declarations are not mapped to any triples and are only a concept of the serialization. To make them visible to SHACL, you need to declare triples such as in https://www.w3.org/TR/shacl/#sparql-prefixes in your

Re: [SHACL] sh:prefixes

2023-02-28 Thread Andy Seaborne
Is there something in the WG test suite for this? Andy On 28/02/2023 12:56, Martynas Jusevičius wrote: Hi, Does Jena's SHACL engine support sh:prefixes? Or am I using them wrong? The following test shape @prefix skos: . @prefix sh: