- From: Polleres, Axel <axel.polleres@siemens.com>
- Date: Wed, 25 Apr 2012 13:24:43 +0200
- To: Steve Harris <steve.harris@garlik.com>, Andy Seaborne <andy.seaborne@epimorphics.com>
- CC: "public-rdf-dawg@w3.org" <public-rdf-dawg@w3.org>
> On 25 Apr 2012, at 09:38, Andy Seaborne wrote: > ... > > > > Better: add BindingsClause to > > > > [58] GraphPatternNotTriples > > ::= GroupOrUnionGraphPattern | OptionalGraphPattern | > > MinusGraphPattern | GraphGraphPattern | ServiceGraphPattern > | Filter | > > Bind | BindingsClause Alright, convinced, thanks ;-) Axel > -----Original Message----- > From: Steve Harris [mailto:steve.harris@garlik.com] > Sent: Wednesday, 25 April 2012 10:59 AM > To: Andy Seaborne > Cc: public-rdf-dawg@w3.org > Subject: Re: Today's Minutes / Publication Plan > > On 25 Apr 2012, at 09:38, Andy Seaborne wrote: > ... > > > > Better: add BindingsClause to > > > > [58] GraphPatternNotTriples > > ::= GroupOrUnionGraphPattern | OptionalGraphPattern | > > MinusGraphPattern | GraphGraphPattern | ServiceGraphPattern > | Filter | > > Bind | BindingsClause > > > > > > { ?s ?p ?o BINDINGS ?p ?o { (:p 157) (:q 34.7) } > > > > execution wise - happens after 'extend' (BIND) and before 'filter' > > (FILTER) > > > > then its in subqueries and everywhere else. > > This also neatly solves the surprise FILTER interaction, as > BINDINGS get joined before FILTER is run, when inline. > > - Steve > > -- > Steve Harris, CTO > Garlik, a part of Experian > 1-3 Halford Road, Richmond, TW10 6AW, UK > +44 20 8439 8203 http://www.garlik.com/ > Registered in England and Wales 653331 VAT # 887 1335 93 > Registered office: Landmark House, Experian Way, NG2 Business > Park, Nottingham, Nottinghamshire, England NG80 1ZZ > > >
Received on Wednesday, 25 April 2012 11:30:15 UTC