construct starting to feel like a separate interface

I'm working on sparcli.py , playing with various
services out there; one of the options is...

    elif '--sparqlette' in sys.argv:
        BG='data'
        svcAddr =
'http://www.wasab.dk/morten/2005/04/sparqlette/?format=xml&'

i.e. I'm trying to look at the SPARQL interface as something
that doesn't have a format= param, but sparqlette has
a format param, so I'm trying to "hide" it in the service
address.

That works for SELECT and ASK, but not for CONSTRUCT.

I'm starting to wonder if ?query=... should be
separated into ?select=... and ?construct=... or
something.

And the special-case for ASK in the results format
feels wierd. I'd rather use the degenerate form of
the general case: zero results for false, and
one result with zero bindings for true. But I guess
we're decided on that (indeed...
http://www.w3.org/2001/sw/DataAccess/ftf4.html#item11 )
and I don't have much in the way of new information.

Just thinking out loud.

for ref...
http://www.w3.org/2001/sw/DataAccess/proto-wd/sparcli.py
1.5 now

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

Received on Friday, 6 May 2005 18:05:57 UTC