W3C home > Mailing lists > Public > semantic-web@w3.org > March 2012

Re: Fwd: Call for proposals to amend the "httpRange-14 resolution"

From: David Booth <david@dbooth.org>
Date: Thu, 01 Mar 2012 14:29:25 -0500
To: Jonathan A Rees <rees@mumble.net>
Cc: public-lod@w3.org, semantic-web@w3.org
Message-ID: <1330630165.10438.90085.camel@dbooth-laptop>
I find the document at 
http://www.w3.org/2001/tag/doc/uddp-20120229/ 
to be hard to read, overly broad, unproductively pedantic and
unnecessarily entangling philosophical questions with simple matters of
protocol design.

As an alternate proposal, I have started a significantly simplified
document on the W3C wiki at
http://www.w3.org/wiki/UriDefinitionDiscoveryProtocol 

Others are encouraged to contribute.  The goals are:

- to be simpler, clearer and more direct;

- to limit the scope to http (and https) URIs, because this is where the
LOD community is experiencing the problem that this specification
addresses;

- to specify this as a simple protocol between a URI owner that wishes
to provide a URI definition, and an agent that wishes to discover that
URI definition;

- to avoid placing constraints on the form or meaning of a URI
definition;

- to avoid placing constraints on an application's use of a URI
definition;

- to additionally specify a simple "implicit" URI definition that can be
used in the case where a resource is defined implicitly as being an
"information resource" (as a result of an HTTP 200 "OK" status code
being returned, as per the httpRange-14 resolution[issue-14-resolved]);

- to be consistent with the existing httpRange-14
resolution[issue-14-resolved], the existing Cool URIs for the Semantic
Web[cooluris] document and existing practice. 

Thanks!
David

On Wed, 2012-02-29 at 17:31 -0500, Jonathan A Rees wrote:
> Sorry for the cross-posting.
> 
> ---------- Forwarded message ----------
> From: Jonathan A Rees <rees@mumble.net>
> Date: Wed, Feb 29, 2012 at 10:57 AM
> Subject: Call for proposals to amend the "httpRange-14 resolution"
> To: www-tag@w3.org
> 
> Concerns regarding the efficiency of 303 redirects and the difficulty
> in deploying them on hosting services have been raised numerous times
> since the TAG proposed the 303 redirect as a way to use "hashless"
> URIs for semantic web and linked data purposes (i.e. beyond the
> purposes of the hypertext Web). The TAG now seeks input from the
> community in the form of proposals to amend the resolution in order to
> address these concerns. Proposals may give new discovery techniques,
> or take any other form that might help mitigate these problems.
> 
> Please consult the following document for details of this call:
> 
> http://www.w3.org/2001/tag/doc/uddp/change-proposal-call.html
> 
> Best
> Jonathan Rees
> 
> 
> 

-- 
David Booth, Ph.D.
http://dbooth.org/

Opinions expressed herein are those of the author and do not necessarily
reflect those of his employer.
Received on Thursday, 1 March 2012 19:29:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:32 UTC