Re: SHACL-C [was: misleading parse exception message in Shacl.]

On 19/07/2020 23:21, Holger Knublauch wrote: On 19/07/2020 19:53, Andy Seaborne wrote: Hi Chris, Oddly, sh:group/sh:order aren't in SHACLC - they look like they got overlooked as they fit is quite naturally into the grammar. Maybe the WG focus was validation and these aren't "validation".

Re: SHACL-C [was: misleading parse exception message in Shacl.]

On 19/07/2020 19:53, Andy Seaborne wrote: Hi Chris, Oddly, sh:group/sh:order aren't in SHACLC - they look like they got overlooked as they fit is quite naturally into the grammar. Maybe the WG focus was validation and these aren't "validation". All terms from the sh: namespace are supported

SHACL-C [was: misleading parse exception message in Shacl.]

Hi Chris, Oddly, sh:group/sh:order aren't in SHACLC - they look like they got overlooked as they fit is quite naturally into the grammar. Maybe the WG focus was validation and these aren't "validation". dash:editor, and your own annotations: There was a brief discussion on the SHACL CG list

Re: misleading parse exception message in Shacl.

Hi Andy, I haven’t looked into SHACLC. We do use features such as sh:group, sh:order, dash:editor and so on; as well as a few annotations of our own that are relevant to editing and some validation controls. Off-hand it isn’t clear how to use SHACLC and weave these other features in. The notat

Re: misleading parse exception message in Shacl.

Be interested to hear experiences using SHACL Compact Syntax. It's Lang.SHACLC SHACL-CS doesn't cover all SHACL but what it does cover is easier to read and write. 1/ What is missing from SHACL-CS from your perspective? 2/ Is it, in fact, actually helpful for managing SHACL at scale or not?

Re: misleading parse exception message in Shacl.

Andy, That's great news! Updating to 3.16.0 is on the ToDo list. I'm moving it to the top. Thanks very much, Chris > On Jul 16, 2020, at 16:20, Andy Seaborne wrote: > > Fixed in 3.16.0: > > "shacl parse" gives: > > No sh:path on a property shape: node=

Re: misleading parse exception message in Shacl.

Fixed in 3.16.0: "shacl parse" gives: No sh:path on a property shape: node= sh:property when there exists at least one triple with bds:ContentLocationShape-contentLocationStatement as su

misleading parse exception message in Shacl.

Hi, I’ve gotten a parse exception: org.apache.jena.shacl.parser.ShaclParseException: No sh:path on a property shape: at org.apache.jena.shacl.parser.ShapesParser.findPropertyShapes(ShapesParser.java:285) at org.apa