W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2009

Re: Service discovery redux - endpoint-based mechanisms

From: Lee Feigenbaum <lee@thefigtrees.net>
Date: Fri, 14 Aug 2009 09:34:26 -0400
Message-ID: <4A8567E2.5090608@thefigtrees.net>
To: Steve Harris <steve.harris@garlik.com>
CC: "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Steve Harris wrote:

>> Option 8 - New protocol operation (?serviceDescription)
>> A request to a URI such as /endpoint/sparql?serviceDescription returns 
>> the service description. Argument for: Simple extension of SPARQL 
>> protocol that maps nicely to non-HTTP instantiations of the protocol. 
>> Easy to implement and invoke. A well-known pattern from Web Services 
>> stacks. Argument against: ?? Not sure, other than Steve is ok with it 
>> but not thrilled. :-)
> There is an annoyance with it, which only just occurred to me. There's 
> no really easy way to reference the actual endpoint with a relative URI, 
> which is sadly necessary in many situations.
> You can use </endpoint/sparql>, in the example above, but that won't 
> work in the general case if the endpoint is being reverse proxied.


I'm feeling a bit dense today, but don't totally understand what you're 
saying here. Mind giving an example?


> - Steve
Received on Friday, 14 August 2009 13:35:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:56 UTC