|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 11/Apr/12 09:26 AM
Updated: 21/May/12 06:46 AM
|
|
| Component/s: |
SPARQL
|
| Affects Version/s: |
2.6.5
|
| Fix Version/s: |
2.6.6
|
|
We have discovered three bugs in the property path parsing:
* It seems that property path {x,} and {,x} is not parsed correctly.
Sesame parses the following three queries all to the same TupleExpr, and
seems to ignore the upper/lower bound in the first/second form:
SELECT ?result WHERE {?start (<u:1>|<u:2>){2,} ?result}
SELECT ?result WHERE {?start (<u:1>|<u:2>){,2} ?result}
SELECT ?result WHERE {?start (<u:1>|<u:2>){2} ?result}
* Likewise the ^ operator is not always taken into account. In the
following query the ^operator is ignored
SELECT ?result WHERE {<u:start> ^(<u:1>|<u:2>)+ ?result}
* ClassCastException when parsing the following query:
SELECT ?result WHERE {?start !<u:1>? ?result}
|
|
Regarding the first issue it should be noted that the SPARQL WG is planning to remove {x,y} property path form from the spec altogether. So we have a choice to either fix the parser or perhaps completely remove the functionality.
fixed problem in SVN. Treating possible removal after SPARQL spec update as separate issue.
|
|
Bug
Resolved
Major
Sesame property path bugs