W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2010

Re: ISSUE-49 (are graphs information resources?)

From: Alexandre Passant <alexandre.passant@deri.org>
Date: Thu, 22 Apr 2010 15:37:42 +0100
Cc: "Gregory Williams" <greg@evilfunhouse.com>, "SPARQL Working Group WG" <public-rdf-dawg@w3.org>
Message-Id: <26D6C745-0E68-4268-8C26-C9C347DD63C8@deri.org>
To: Chimezie Ogbuji <ogbujic@ccf.org>

On 20 Apr 2010, at 18:29, Chimezie Ogbuji wrote:

[...]

> 
> New entries:
> 
> * Graph IRI - The IRIs involved in this protocol that are specified as a
> request URI or embedded as a query component *and* correspond to the IRIs in
> the underlying Network-manipulable RDF.   
> * RDF document   - A serialization of an RDF Graph into a concrete syntax
> [RDF-XML].

Could we avoid explicit reference to RDF-XML here ?
(I know that's the only rec. but we may abstain mentioning it in that case)

Alex.

> 
> [[[
> Networked RDF knowledge - ... snip ... An information resource, identified
> by the IRI of a graph in a network-manipulable RDF dataset ...
> ]]]
> ==>
> [[[
> Networked RDF knowledge - ... snip ... An information resource, identified
> by a graph IRI ...
> ]]]
> 
> In every other similar case where there is a reference to dataset, replace
> with graph store.
> 
> Add a new sentence to the last paragraph in 2:
> 
> [[[
> Following the terminology in [AWWW], the intuition here is that messages in
> this HTTP protocol use graph IRIs to access the underlying graph store.  The
> graph IRIs identify networked RDF knowledge.  Networked RDF knowledge is
> distinguished from other kinds of (information) resources by the fact that
> they are primarily represented by an RDF document and these RDF documents
> are serializations of RDF graphs in the underlying graph store.
> ]]]
> 
> In 4.1:
> 
> [[[
> We recall from [SPARQL] that IRIs for RDF graphs in SPARQL queries identify
> a resource, and the resource is represented by a graph (or, more precisely:
> by a document that serializes a graph)
> ]]]
> 
> ==>
> 
> [[[
> We recall from [SPARQL] that IRIs for RDF graphs in SPARQL queries identify
> a resource, and the resource is represented by a graph.
> ]]]
> 
> In the third paragraph of this section:
> 
> [[[
> In our example, the corresponding request URI
> (http://example.com/rdf-graphs/employees) is meant to identify RDF triples
> on the example.com server that describe employees ..
> ]]]
> ==>
> [[[
> In our example, the corresponding request URI
> (http://example.com/rdf-graphs/employees) is a graph IRI that identifies RDF
> knowledge about employees ..
> ]]]
> 
> In section 5
> [[[
> .. snip ... performed on Networked RDF knowledge. Where an equivalent SPARQL
> Update operation is given, <graph_uri> is understood to be either the
> request URI or the URI indirectly specified via the query component as
> described above. 
> ]]]
> ===>
> [[[
> ... snip .. performed on Networked RDF knowledge. Occasionally, an analogous
> SPARQL Update operation is given to demonstrate how the operations are
> interpreted.  This is meant to be informative and does not dictate a formal
> binding between the two protocols.  Within the given analogous SPARQL Update
> operations, <graph_uri> is understood to be a graph IRI.  As mentioned
> previously, these do not directly identify the RDF graphs. 
> ]]]
> 
> And wherever the document says 'is equivalent to' (in reference to the
> analogous SPARQL Update operations) this should be changed to 'is analogous
> to'
> 
> -- Chime
> 
> [1] http://www.w3.org/2009/sparql/track/actions/116
> 
> 
> ===================================
> 
> P Please consider the environment before printing this e-mail
> 
> Cleveland Clinic is ranked one of the top hospitals
> in America by U.S.News & World Report (2009).  
> Visit us online at http://www.clevelandclinic.org for
> a complete listing of our services, staff and
> locations.
> 
> 
> Confidentiality Note:  This message is intended for use
> only by the individual or entity to which it is addressed
> and may contain information that is privileged,
> confidential, and exempt from disclosure under applicable
> law.  If the reader of this message is not the intended
> recipient or the employee or agent responsible for
> delivering the message to the intended recipient, you are
> hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited.  If
> you have received this communication in error,  please
> contact the sender immediately and destroy the material in
> its entirety, whether electronic or hard copy.  Thank you.
> 
> 

--
Dr. Alexandre Passant
Digital Enterprise Research Institute
National University of Ireland, Galway
:me owl:sameAs <http://apassant.net/alex> .
Received on Thursday, 22 April 2010 14:38:23 GMT

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