W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2010

Re: short before the call... remaining issues on LET/BIND/ASSIGN

From: Axel Polleres <axel.polleres@deri.org>
Date: Tue, 12 Oct 2010 10:50:40 -0300
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-Id: <E15CEE8C-2663-4A3D-A086-83F9E8EAAC11@deri.org>
To: Axel Polleres <axel.polleres@deri.org>
p.s.: 

I forgot... 

5) "simple semantics" needs a syntactic restriction, yes? I.e.
   Var is not potentially bound in P1
 yes? Is that ok/enough/

6) I used "SELECT * (Expr AS Var)" in my example ... is that allowed at the moment, i.e. can I combined * with Project expressions?

Axel
  
On 12 Oct 2010, at 10:47, Axel Polleres wrote:

> remaining issues on LET/BIND/ASSIGN
> 
> 1) we seemed to have a preference for simple semantics, i.e. based on Extend() operator which we already have. my understanding of that is that assignment is then just syntactic sugar for subselect + project expression, yes?
> 
> 2) order dependence yes/no?
>   currently order-dependent in ARQ... others?
>   order-dependence conforms with understanding in 1), i.e. 
> 
>      { P1 KW(Expr AS ?Var)  P2}
>    =:=
>      { { SELECT * Expr AS ?Var { P1} } P2 }
> 
> 3) syntax?  
>   * keywords (in aphabetic order): 
>       ASSIGN
>       BIND
>       LET
> 
>    * assignment operator
>       Var := Expr
>        vs.
>       Expr AS Var
> 
> 4) other open questions?
Received on Tuesday, 12 October 2010 13:51:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:44 GMT