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

Re: Service discovery redux - endpoint-based mechanisms

From: Steve Harris <steve.harris@garlik.com>
Date: Thu, 20 Aug 2009 22:21:04 +0100
Message-ID: <4A8DBE40.2040707@garlik.com>
To: Jacek Kopecky <jacek.kopecky@sti2.at>
CC: Lee Feigenbaum <lee@thefigtrees.net>, "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Jacek Kopecky wrote:
> On Fri, 2009-08-14 at 16:57 +0100, Steve Harris wrote:
>   
>> However, if the description of http://localhost:8080/sparql/ lives at http://localhost:8080/sparql/?serviceDescription 
>> , then you can't use <>, so you have to write something like:
>>
>> </sparql> a sparql:Endpoint ;
>>     sparql:has sparql:featureA ;
>>     ...
>>
>> And that will give you an incorrect and unhelpful answer if you  
>> request it as https://machine.example.com/myapp/sparql/?serviceDescription
>>     
>
> In this case, <../sparql/> would apparently work.
>
> Do you know of cases where http://localhost:8080/sparql/ is rev-proxied
> to something like https://machine.example.com/myapp/foo/ ? 
> I.e., something not ending with /sparql/
>   
I couldn't tell you offhand, but obviously nothing prevents it.

- Steve
Received on Thursday, 20 August 2009 21:21:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:39 GMT