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


From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Mon, 14 Dec 2009 15:31:14 -0500
To: "SPARQL Working Group" <public-rdf-dawg@w3.org>
Message-ID: <C74C0AC2.EA35%ogbujic@ccf.org>
Per my ACTION (152) [1] to provide a high-level changelog summarising what
has happened since FPWD in RDF Update:

I have a draft response for Leigh Dodds comments can be found here:

- http://www.w3.org/2009/sparql/wiki/CommentResponse:ldodds-http-update

The following modifications were made with these comments in mind:

At the end of 4.1 HTTP PUT, I added a paragraph (and example) documenting
the semantics of A PUT request with an empty payload.

Leigh Dodds suggested a built-in mechanism for POSTing RDF graphs to a
container resource which then responds with a 201 such that the server can
determine the URI used to store the payload as a new, named RDF graph and
indicate this to the client.  The changes were made to 4.3 HTTP POST

Note the similarity between this mechanism and that of AtomPub [2]

A new Conditional Request section was added as a generalization of the
conditions described for GET requests to all other methods in the protocol.

A general Security Considerations was added to discuss how implementations
might choose to not respond to a request if it violates a local security

[1] http://www.w3.org/2009/sparql/track/actions/152
[2] http://tools.ietf.org/html/rfc5023#section-5.3

-- 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

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, 14 December 2009 20:32:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:58 UTC