On 09/08/11 17:24, Svatopluk Šperka wrote:
I've expected that the framework does not allow constructing invalid
queries - sorry for bug suspicion then ;)
The query may be legal and executable ... but not creatable from SPARQL
syntax. That said, onyl legal SPARQl+extensions is tested.
I've debugged my script in Eclipse and inspected the structure of the
correct query in order to rewrite my code. There were two problems -
I had an ElementNamedGraph as a top element of a query but there has
to be an ElementGroup around it (this resolved differences in dots
after triple patterns.); and mainly I've used NodeValueNode instead
of ExprVar by mistake in one place.
Yes - you have to have an ElementGroup ({}) at the top.
BTW what is the difference between ElementPathBlock and
ElementTriplesBlock ? Is it that in the former it is possible to use
property paths when using SPARQL 1.1 ?
Yes.
ElementPathBlock get processed into triple patterns during conversion to
the algebra, only leaving path expression like :p*, :p+ and :p{0} that
do not have a SPARQL triples equivalent.
Thanks for pointing me towards the problem.
Regards,
Svatopluk Šperka
Andy
