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

Re: REST and HTTP Update

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Thu, 08 Oct 2009 09:29:27 -0400
To: "Steve Harris" <steve.harris@garlik.com>, "public-rdf-dawg@w3.org Group" <public-rdf-dawg@w3.org>
Message-ID: <C6F36177.CEB9%ogbujic@ccf.org>
On 10/7/09 3:26 PM, "Steve Harris" <steve.harris@garlik.com> wrote:
> However, among the other people using our store, I don't know of
> anyone using the obvious REST approach. For whatever reason* people
> seem to prefer the urlencode form. The half dozen or so 3rd party
> libraries all seem to use the urlencode form.

Just my take, but I would imagine that not having control over the address
space of a named graph is the most common reason.

For example, we store patient records as RDF graphs (one graph per patient
record) and allocate non-resolvable tag: URIs as their names.  So, already,
this rules out the 'direct' approach for managing these graphs in the
proposed protocol.
- 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 (2008).  
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 Thursday, 8 October 2009 13:31:03 UTC

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