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

Re: ACTION-115: Note on proxy graph URI

From: Chimezie Ogbuji <ogbujic@ccf.org>
Date: Mon, 12 Oct 2009 12:23:11 -0400
To: "Steve Harris" <steve.harris@garlik.com>, "Kjetil Kjernsmo" <kjetil@kjernsmo.net>
cc: public-rdf-dawg@w3.org
Message-ID: <C6F8D02F.CFB7%ogbujic@ccf.org>
Response to both message below

On 10/11/09 2:50 PM, "Steve Harris" <steve.harris@garlik.com> wrote:
>> If we do have enough time for a straw poll, I suggest voting over the
>> following questions, separately:
>> 1) The HTTP Update protocol is required to be RESTful. (+1, yes; 0,
>> preferred, but not required; -1, it could be anything)

I'm very concerned about explicitly making an ambiguous requirement.  This
is why I tried to avoid using the term RESTful, because beyond the AWWW best
practices, the RFC specification related to the semantics of HTTP, and the
fuzzy notion of 'using HTTP appropriately for the purpose of inducing
harmonious behavior in large-scale, hypermedia applications' it seems IMHO
ambiguous as to what it means to be 'RESTful'.

I think it is much more useful for the WG to focus on how HTTP can be used
as a 'native' protocol for RDF graph management in a way that meets
well-established usecases and tries to faithfully follow AWWW best practices
and the semantics of the HTTP specifications (both of which are much more
concrete and thus better suited as the basis for a 'requirement').
> I have a strong concern around deciding that "it must be RESTful", as
> no-one in this group really seems to know the exact criteria for some
> API to be RESTful.

I agree

-- Chimezie


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 Monday, 12 October 2009 16:24:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:57 UTC