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

I guess I'm not sure what still needs to be nailed down or what is gained
from answering the question of whether a graph is an information resource or
not.  It seems orthogonal to the HTTP update protocol definition since the
protocol only defines how to interact with RDF graphs over HTTP.

On 4/18/10 2:55 PM, "Gregory Williams" <greg@evilfunhouse.com> wrote:
>> Concretely, this seems to imply that if you have a document
>> http://example.org/foo.rdf you cannot import this into a quad store with
>> http://example.org/foo.rdf as the graph name, since it is an information
>> resource. Moreover, if you did, you cannot return a 200 if has been imported,
>> it would have to return a 303.

This seems to suggest that some interpretation of http-range-14 is a
necessary part of the HTTP update protocol and I think this is more trouble
than it is worth and beyond the scope of the document (which is about
interaction and not interpretation).

The use of the term 'information resource' was only meant to align with the
terminology used in the AWWW rather than to ascribe any formal definition
beyond what is implied in the current SPARQL specification: that graph IRIs
identify graphs that are represented by RDF graph syntaxes (and thus can be
manipulated over HTTP).
 
-- Chime


===================================

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 Monday, 19 April 2010 21:11:12 UTC