You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/06/06 09:49:00 UTC
[jira] [Commented] (JENA-1907) Nested targets can lead to different
numbers of constraint executions.
[ https://issues.apache.org/jira/browse/JENA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127296#comment-17127296 ]
ASF subversion and git services commented on JENA-1907:
-------------------------------------------------------
Commit 27f74df759e7a609d688f04f8dfce70e9d378d8d in jena's branch refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=27f74df ]
JENA-1907: SHACL - Deal with nested targets
> Nested targets can lead to different numbers of constraint executions.
> ----------------------------------------------------------------------
>
> Key: JENA-1907
> URL: https://issues.apache.org/jira/browse/JENA-1907
> Project: Apache Jena
> Issue Type: Bug
> Components: SHACL
> Affects Versions: Jena 3.15.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.16.0
>
>
> If one target "A" refers to another target "B" then the encounter order affects the validation because the code track all shapes processed.
> If B is processed first as a target then A, B is executed twice - once as a top level target and once as part of A.
> If A is processed first as a target then the parser shapes now includes B so processing B is skipped.
> Note - the effect is only in the number of times constriants are executed , once or twice, not whether they are omitted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)