Re: Abstract syntax for updates

On Oct 15, 2010, at 12:47 PM, Chimezie Ogbuji wrote:

> Hey Pat,
> 
> On 10/15/10 1:37 PM, "Pat Hayes" <phayes@ihmc.us> wrote:
>> Yes, quite, although my point was that we cannot call this thing an RDF graph,
>> because that terminology has been normatively defined to be an immutable set.
>> So we need a new terminology. The more I think about "RDF resource", the
>> better it gets, BTW. It is any information resource which emits RDF
>> representations when poked; and an RDF representation is anything which is an
>> encoding of an RDF graph.
> 
> I'm curious (since you say this is motivated by the REST abstraction and
> there is a similar distinction made in the Uniform HTTP Protocol draft), how
> does this differ from the notion of 'RDF knowledge' [1] which is an
> information resource identified by the graph IRI of a named graph and is
> represented by an RDF document, which serializes that named graph? Can it be
> considered a generalization of this concept (to more than just named graphs)
> or is it something different?

Thanks, I had not seen this document. Yes, I think it can be regarded as a generalization of your notion. The key point however is that in order to allow for 'updates' while still retaining identity, there has to be some way for the same URI to produce different RDF graphs at different times. This goes beyond the named graph model , which assumes that names are rigid designators for graphs, so (even if we think of the named graph as an information-resource) means that it would be an error to speak of updating a named graph.  Maybe we ought to call  them named graph resources or some such. 

Pat

> http://www.w3.org/TR/2010/WD-sparql11-http-rdf-update-20101014/#direct-graph
> -identification
> 
> 
> ===================================
> 
> 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.
> 
> 

------------------------------------------------------------
IHMC                                     (850)434 8903 or (650)494 3973   
40 South Alcaniz St.           (850)202 4416   office
Pensacola                            (850)202 4440   fax
FL 32502                              (850)291 0667   mobile
phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes

Received on Tuesday, 19 October 2010 14:15:00 UTC