W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2009

Uniform, Core RDF Update Protocol for HTTP (FPWD)

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Mon, 28 Sep 2009 18:43:43 -0400
To: "SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-ID: <C6E6B45F.CB66%ogbujic@ccf.org>
I've committed an initial draft for the "RESTful RDF update" document.  I
tried to be as faithful to the intent and language of the AWWW, HTTP/URI
RFCs, REST literature as possible.

http://www.w3.org/2009/sparql/docs/http-rdf-update/

In order to ensure a meaningful mapping to HTTP, I had to describe a
protocol model and introduce some terminology to clarify the model and the
roles of the actors to (hopefully) help with the discussion at least with
respect to the open issue of using ?graph=.. to (indirectly) route HTTP
operations to a network-manipulable RDF graph.

The outstanding questions that need to be answered to reconcile the protocol
model to this use case are:

- What do those 'proxy' URIs identify?
- If they identify an addressable data-processing service, does that break
cacheability, and URI best practices around consistent identification of
resources? 

My current intuition is that if we consider:

http://example.com/graph1?graph=http://inaccessible.domain.org/graph1

to be a separate URI that identifies the same networked RDF knowledge as
does

http://inaccessible.domain.org/graph1

Then this works with the protocol model described so far.

There seems to be some similarity between the behavior we want from routing
HTTP operations to the proxy URI and the semantics of the use of 303 for
indirection, but I didn't pursue that thought any further.

Currently, the protocol model assumes the methods are only directed at
'information resources' that are identified by the (resolvable) IRIs of
named graphs in a dataset managed by an implementation of this protocol (I
use the term networked RDF knowledge as a special kind of 'information
resource' in this model).

I'm hoping the terminology helps to keep the dialog out of the philosophical
quick sand often associated with the URI resolution / denotation redux
thread.  

Comments are welcome

----------------------
Chime (chee-meh) Ogbuji (oh-bu-gee)
Heart and Vascular Institute (Clinical Investigations)
Architect / Informatician
Cleveland Clinic (ogbujic@ccf.org)
Ph.D. Student Case Western Reserve University
(chimezie.thomas-ogbuji@case.edu)


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

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 (2008).  
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, 28 September 2009 22:45:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:08:28 GMT