[
https://issues.apache.org/jira/browse/JENA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626655#comment-14626655
]
Andy Seaborne commented on JENA-989:
------------------------------------
Thanks for the confirmation. While in the area, I cleaned up query production
for various unnecessary nesting cases as well and expanded the test coverage.
Nesting multiple OPTIONALs is a remaining area of different syntax which shows
up in your test corpus. Output is correct (equivalent query; same algebra) from
OpAsQuery, just looks different.
> Round tripping property paths from SPARQL into Sexpressions and back yields a
> syntax error
> ------------------------------------------------------------------------------------------
>
> Key: JENA-989
> URL: https://issues.apache.org/jira/browse/JENA-989
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.0.0
> Reporter: Rick Moynihan
> Assignee: Andy Seaborne
> Fix For: Jena 3.0.0
>
>
> The following SPARQL query:
> {noformat}
> SELECT ?uri WHERE {
> ?uri <http://www.w3.org/2000/01/rdf-schema#subPropertyOf>+
> <http://purl.org/linked-data/sdmx/2009/dimension#refArea>
> }
> {noformat}
> When converted into an sse:
> {noformat}
> (path
> ?uri
> (path+ <http://www.w3.org/2000/01/rdf-schema#subPropertyOf>)
> <http://purl.org/linked-data/sdmx/2009/dimension#refArea>)
> {noformat}
> and converted back into a SPARQL query via OpAsQuery is syntactically
> invalid. Note the misplaced `.`:
> {noformat}
> SELECT *
> WHERE
> { .
> ?uri (<http://www.w3.org/2000/01/rdf-schema#subPropertyOf>)+
> <http://purl.org/linked-data/sdmx/2009/dimension#refArea>
> }
> {noformat}
> The same seems to occur for all other property paths (e.g. those that use +,
> *, /, ^ etc...)
> This seems related to issues resolved in JENA-963.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
