W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2011

Re: Dataset HTTP Protocol and Service Descriptions

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Thu, 03 Mar 2011 10:57:46 +0000
Message-ID: <4D6F742A.7040006@epimorphics.com>
To: Chimezie Ogbuji <chimezie@gmail.com>
CC: Gregory Williams <greg@evilfunhouse.com>, SPARQL Working Group <public-rdf-dawg@w3.org>


On 02/03/11 02:22, Chimezie Ogbuji wrote:
> On Tue, Mar 1, 2011 at 1:33 PM, Andy Seaborne
> <andy.seaborne@epimorphics.com>  wrote:
>> ..snip..
>> Something that might need describing is whether the service providing the
>> RDF Dataset HTTP Protocol supports direct or indirect, or both, naming.
>
> Perhaps, the following specific sd:Features?:
> - sd:DirectGraphIdentification
> - sd:IndirectGraphIdentification
>
> i.e.:
>
> <>  a sd:Service;
>       sd:defaultDatasetDescription</dataset>  .
>       sd:feature sd:DirectGraphIdentification, sd:IndirectGraphIdentification .
>
> </dataset>  a sd:RESTDataset
>
> -- Chime
>

+1

I've realised that in Fuseki, it going to be hard to provide direct 
naming and a service model without some degree of name clashing.  A 
common usage model however, is likely to be an aggregating store, where 
there is no need for direct naming.

	Andy
Received on Thursday, 3 March 2011 10:58:36 GMT

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