Re: On the inevitability of SPARQL/SPIN for SHAQL

On 3/1/15 5:24 PM, Jose Emilio Labra Gayo wrote:
> 2.- To allow the core language to have XPATH like functionality and 
> variables. It can be something similar to the expressions that appear 
> in the FILTER clauses in SPARQL. As an example using the compact 
> syntax we could say:
>
> <RectangleShape> { :weidth ?w, :height ?h, :area ?a, FILTER (?w * ?h = 
> ?a) }

This looks like it would simply reinvent a new SPARQL, only that no 
existing tool would support it yet.

>
>
>
> But generating human-readable error messages can be a post-process 
> operation. Embedding that functionality in SPARQL you are preventing 
> any implementation that is not based in SPARQL.

Why not? If someone wants to use another language, then this would also 
have a mechanism to create strings. JavaScript certainly has. And even 
if not, the human-readable messages are purely optional anyway, but 
preventing something that is already solved by SPARQL doesn't sound like 
a good idea.

Holger

Received on Sunday, 1 March 2015 08:57:15 UTC