scope - Should variable bound in SELECT clause be accessible in ORDER BY? -
should valid sparql?
select ("text" ?astring) {} order ?astring
i have tried 2 different engines. 1 returns "text" ?astring, other errors, saying ?astring not defined in order by. sparql spec cover case? or implementation detail, happens work in engines, not strictly portable?
sparql.org's query validator says it's legal. pretty important case, since want able things like:
select ?min ?max ((?max - ?min) ?range) { #-- ... } order ?range
Comments
Post a Comment