W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2005

Re: CR10 : Refined proposal.

From: Hugo Haas <hugo@w3.org>
Date: Mon, 5 Dec 2005 22:36:26 +0100
To: Jonathan Marsh <jmarsh@microsoft.com>
Cc: public-ws-addressing@w3.org
Message-ID: <20051205213626.GN3451@w3.org>
* Jonathan Marsh <jmarsh@microsoft.com> [2005-12-05 12:34-0800]
> You seem to think the term "Best Practice" as used in AoWWW is a weak
> term.  Perhaps it's not what they really meant when writing that
> document?  That's strange, but if you don't think that term correctly
> conveys the intent, I'm willing to abstract it out as well.
> 
> It also seems the more we can encourage people to actually read AoWWW
> the better, so they understand those benefits and can actually make use
> of them.  Further encouragement to read section 2 might help here.

This proposal looks much better than proposal 5 to me.

One minor nit:

> Proposal 5a:  The W3C Architecture of the World Wide Web [AoWWW]
> recommends [Section 2.1] the use of URIs to identify resources.  Using
> abstract properties of an EPR other than [destination] to identify
> resources is contrary to this recommendation.  In certain circumstances,
> such a use of additional properties may be convenient or beneficial;
> however, when building systems, the benefits or convenience of
> identifying a resource using reference parameters should be carefully
> weighed against the benefits of identifying a resource solely by URI as
> explained in [Section 2. Identification] of the Web Architecture.
> 
> One more option shouldn't make the chadding any more difficult...

I'd like to replace "W3C Architecture of the World Wide Web" by
"Architecture of the World Wide Web, Volume One", as this is the
document we are talking about. Also, the whole section about
identification is section 2, and the one about benefits of URIs is
section 2.1, so I think that the references are backwards.

Let me crystallize this as proposal 5b, which hopefully is a friendly
amendment to 5a:

  Proposal 5b:  The Architecture of the World Wide Web, Volume One
  [AoWWW] recommends [Section 2 of AoWWW] the use of URIs to identify
  resources.  Using abstract properties of an EPR other than
  [destination] to identify resources is contrary to this
  recommendation.  In certain circumstances, such a use of additional
  properties may be convenient or beneficial; however, when building
  systems, the benefits or convenience of identifying a resource using
  reference parameters should be carefully weighed against the
  benefits of identifying a resource solely by URI as explained in
  [Section 2.1] of the Web Architecture.

Cheers,

Hugo

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Monday, 5 December 2005 21:39:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:10 GMT