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

Re: Service or graph store naming.

From: Chimezie Ogbuji <chimezie@gmail.com>
Date: Tue, 8 Feb 2011 16:58:53 -0500
Message-ID: <AANLkTikfABW9_nKRDfPDznanm5MZiLU3emd6NVarp51t@mail.gmail.com>
To: Andy Seaborne <andy.seaborne@epimorphics.com>
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
On Tue, Feb 8, 2011 at 9:06 AM, Andy Seaborne
<andy.seaborne@epimorphics.com> wrote:
>> sd:defaultDatasetDescription a owl:FunctionalProperty

> ?? It can't be functional in all cases - suppose the dataset description is
> rather minimal.

I'm not sure what you mean.  I guess the question I was posing with
that axiom is if it is the case that every service (SPARQL RDF
protocol service or Dataset HTTP Protocol service) 'manages' one and
only one graph store or RDF dataset.

> And the domain of sd:defaultDatasetDescription is sd:Service and we might
> have several services.

Ok, but can any of them be associated with more than one dataset or graph store?

> Can we have multiple service descriptions (query, update,
> RESTDatasetService) in one description? If so, which URL gets that
> description?

I wouldn't think so.  I've assumed that each service description
document has only one sd:Service instance and (incorporating what
Gregg said about the way the sd:url property is used), the service URL

  { ?SERVICE a sd:Service FILTER(isUri(?URL)) } UNION { ?ALIAS sd:url ?SERVICE }

-- Chime
Received on Tuesday, 8 February 2011 21:59:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:03 UTC