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: Mon, 7 Feb 2011 09:58:31 -0500
Message-ID: <AANLkTi=p3gpeqdQXQGcae8FDoo6OdW=Aks_BwpW7ZcGw@mail.gmail.com>
To: Gregory Williams <greg@evilfunhouse.com>
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
On Sun, Feb 6, 2011 at 12:32 PM, Gregory Williams <greg@evilfunhouse.com> wrote:
> .. snip ..
> I don't agree that this is entirely the second case. Protocol implementations that return a service description but don't implement the
> dataset protocol may still have URIs for the dataset. Just the use of sd:defaultDatasetDescription (or typing as sd:Dataset) isn't
> enough to imply that the URI acts as part of the dataset protocol. The only way as described to find out is to dereference the URI
> and see if you get anything back.
> .. snip ..
> I don't think it's improper, no. But sd:Dataset is a fundamental part of the service description vocabulary that doesn't necessarily
> imply availability of a dataset protocol resource.

Ok, so the SD vocabulary would need some extension to specify this.
Do you have any suggestions?  I was browsing through the SD vocabulary
to find an appropriate extension point, but didn't find any
immediately obvious ones.  One thing I noticed is that sd:Service
instances are instances of SPARQL Protocol implementations.  The
current SPARQL protocol includes operations (and bindings to HTTP) for
the Update language but not for the RDF Dataset HTTP Protocol.  So, it
doesn't appear that instances of sd:Service can be implementations of
the RDF Dataset HTTP Protocol since the SPARQL Protocol doesn't
specify HTTP bindings for it.

I.e., assuming (just for the sake of conversation) there is an
sd:RESTDatasetService class, following the dependent specifications
seem to  suggest:

sd:RESTDatasetService owl:disjointWith sd:Service

Otherwise, I would have suggested adding something like

sd:RESTDatasetService rdfs:subClassOf sd:Service

But, once that conceptual link is made between both classes then this
could serve as the extension point that ensures this entirely in the
second case.  In particular:

sd:RESTDatasetService rdfs:subClassOf
  [ a owl:Restriction owl:onProperty sd:defaultDatasetDescription
    owl:allValuesFrom
      [ a owl:Class;
        owl:intersectionOf ( sd:DataSet ..mutable web resource.. ) ] ]
Received on Monday, 7 February 2011 14:59:26 GMT

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