You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2021/04/01 09:20:00 UTC

[jira] [Updated] (JENA-2008) SHACL alternative paths get turned into nested structures unnecessarily

     [ https://issues.apache.org/jira/browse/JENA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne updated JENA-2008:
--------------------------------
    Fix Version/s:     (was: Jena 4.0.0)

> SHACL alternative paths get turned into nested structures unnecessarily
> -----------------------------------------------------------------------
>
>                 Key: JENA-2008
>                 URL: https://issues.apache.org/jira/browse/JENA-2008
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: SHACL
>    Affects Versions: Jena 3.17.0
>            Reporter: Andy Seaborne
>            Priority: Minor
>
> SHACLC parsing
> {noformat}
> shape ex:shape2 {
>  targetNode = :WhatEver .
>  ex:A|ex:B|ex:C datatype=xsd:integer .
> }
> {noformat}
> produces
> {noformat}
> sh:path [ sh:alternativePath ( [ sh:alternativePath ( ex:A ex:B ) ] ex:C  )
> {noformat}
> which evaluates correctly but it could be {{sh:alternativePath ( ex:A ex:B ex:C  )}}.
> Printing SHACLC (and SPARQL) paths ({{PathWriter}}) puts in {{()}} over-cautiously to get {{(ex:A|ex:B)|ex:C}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)