[
https://issues.apache.org/jira/browse/JENA-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1317.
---------------------------------
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.3.0
> Property path with wildcard hack fails to consider incoming path
> ----------------------------------------------------------------
>
> Key: JENA-1317
> URL: https://issues.apache.org/jira/browse/JENA-1317
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.2.0
> Reporter: Lorenz Bühmann
> Assignee: Andy Seaborne
> Fix For: Jena 3.3.0
>
>
> It looks like the evaluation of a property path with an alternative of a
> non-existing property and it's negation fails:
> Data (data.ttl):
> {noformat}
> @prefix : <http://example.com/> .
> :a :p :b .
> {noformat}
> Query (query.txt):
> {noformat}
> PREFIX : <http://example.com/>
> SELECT ?u {
> :b ^(:p1|!:p1) ?u .
> }
> {noformat}
> Algebra:
> {noformat}
> (project (?u)
> (path ?u (alt <http://example.com/p1> (notoneof <http://example.com/p1>))
> <http://example.com/b>))
> {noformat}
> Called with
> {{sparql --data data.ttl --query query.txt --explain}}
> Originally reported here:
> (http://stackoverflow.com/questions/43317635/sparql-path-between-two-nodes/43319876#43319876)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
