- From: Steve Harris <steve.harris@garlik.com>
- Date: Wed, 20 Jul 2011 15:14:01 +0100
- To: Lee Feigenbaum <lee@thefigtrees.net>
- Cc: Carlos Buil Aranda <cbuil@fi.upm.es>, Gregory Williams <greg@evilfunhouse.com>, SPARQL Working Group <public-rdf-dawg@w3.org>
On 2011-07-20, at 03:57, Lee Feigenbaum wrote: >> So, the possible solutions are: >> - For the SERVICE VAR semantics >> - add a new operation that could allow the evaluation (operation >> which wouldn't be bottom-up) >> - define its whole semantics in a new way >> - For the boundedness restriction >> - specify all cases: it may take a bit long >> - remove it? I do not think this is a good idea, how do we specify >> then that a variable is bound (which is needed for the evaluation >> semantics of SERVICE VAR)? >> >> something missing? any other option? > > As someone who was a bit uncomfortable including it in the first place, I'll add another, dramatic option: remove SERVICE VAR from the specification altogether. That sounds like a good, pragmatic solution, but it would require a second Last Call, no? - Steve -- Steve Harris, CTO, Garlik Limited 1-3 Halford Road, Richmond, TW10 6AW, UK +44 20 8439 8203 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Wednesday, 20 July 2011 14:14:42 UTC