Various updates to HTTP Protocol editor's draft

I've updated the editor's draft of the SPARQL 1.1 Uniform HTTP Protocol for
Managing RDF Graphs, addressing the outstanding issues, comments, and
feedback.  At a high-level the changes consist of replacing the term
Networked RDF knowledge with RDF knowledge, replacing the term
Network-manipulable RDF dataset with Network-manipulable Graph Store, and
reconciling definitions from the SPARQL Update document:

- The definition of what a Graph Store is
- Defining a Network-manipulable Graph Store as a subset of a Graph Store
comprised only of named graphs that can be manipulated within the HTTP
- Clarification of language regarding whether or not the Graph Store records
the existence of empty graphs

The terminology has been tightened up.  The sections regarding graph
management operation now have text better clarifying appropriate response
codes (only where clarity is needed) and deferring to the HTTP 1.1
specification for the details of the rest.  Text clarifying the scenario
where a graph IRI is embedded and there is no base URI in the payload has
been added, but examples are still pending.

A new section has been added: Ambiguity Regarding the Range of HTTP GET
(Informative).  It discusses the issue of ambiguity regarding the range
of the dereference function, clarifies how this issue relates to graph IRIs,
RDF knowledge, information resources, and the rules of the httpRange-14
resolution (in particular, the first rule) .  The rule is quoted inline and
the resolution is linked from the text.  Overall, it clarifies why HTTP GET
requests to RDF knowledge should respond with:

- 200 Ok, if it exists
- 404 Not Found, if it doesnt

It also describes why 303 (See Other) is not appropriate as a response to
HTTP GET requests that identify existing RDF knowledge.

-- 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 for
a complete listing of our services, staff and

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, 2 August 2010 20:38:13 UTC