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

Re: Service description schema

From: Steve Harris <steve.harris@garlik.com>
Date: Tue, 11 Aug 2009 08:27:59 +0100
Cc: "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Message-Id: <D4917C67-EBA7-4C9F-85A4-438FC5DBBC3D@garlik.com>
To: Alexandre Passant <alexandre.passant@deri.org>
On 11 Aug 2009, at 07:59, Alexandre Passant wrote:

> Hi,
>
> Le 11 août 09 à 07:12, Steve Harris a écrit :
>
>> I'm acutely aware of the dangers of scope creep, but one thing I  
>> think we ought to be able to say is something like:
>>
>> <some-resource> sparql:seeEndpoint <http://sparql.example/endpoint> .
>>
>
> There's a sparqlEndpoint property in voiD, that currently has  
> void:Dataset as a range [1], but I guess they could extend it to  
> make it more generic.

Well, it's reasonable to be able to say that as well, and overloading  
it doesn't seem appropriate.

> Also, SIOC (in the Services module [2]) has a has_service property  
> that links anything to a related service. This service can then be  
> defined as being a SPARQL endpoint using:
>
> <some-resource> siocs:has_service [
>  siocs:service_protocol <http://www.w3.org/TR/rdf-sparql-protocol/> ;
>  siocs:service_endpoint <http://sparql.example.org/endpoint>
> ] .

That looks good though, thanks.

- Steve
Received on Tuesday, 11 August 2009 07:28:38 GMT

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