- From: Lee Feigenbaum <lee@thefigtrees.net>
- Date: Fri, 14 Aug 2009 09:34:26 -0400
- 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. Steve, I'm feeling a bit dense today, but don't totally understand what you're saying here. Mind giving an example? Lee > - Steve >
Received on Friday, 14 August 2009 13:35:17 UTC