- From: Chimezie Ogbuji <ogbujic@ccf.org>
- Date: Fri, 15 Oct 2010 13:47:13 -0400
- To: "Pat Hayes" <phayes@ihmc.us>, "Richard Newman" <rnewman@twinql.com>
- cc: "Eric Prud'hommeaux" <eric@w3.org>, "public-rdf-dawg-comments@w3.org Group Comments" <public-rdf-dawg-comments@w3.org>, rjh06r <rjh06r@ecs.soton.ac.uk>, "Axel Polleres" <axel.polleres@deri.org>
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? [1] 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.
Received on Friday, 15 October 2010 17:48:20 UTC