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

Re: [public-webapps] Comment on Widget URI (1)

From: Robin Berjon <robin@berjon.com>
Date: Thu, 19 Nov 2009 15:13:26 +0100
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
Message-Id: <09B4C0A6-0DAC-4A3C-B402-1BB1CCE385CF@berjon.com>
To: Larry Masinter <masinter@adobe.com>
Dear Larry,

thank you for your comments.

On Oct 10, 2009, at 19:44 , Larry Masinter wrote:
> 1) ** WELL DEFINED QUERY AND AUTHORITY **
> http://www.w3.org/TR/webarch/#URI-scheme points to RFC 2617, which has been
> replaced by RFC 4395. I think WebArch should be updated to recommend that
> W3C recommendations must use "permanent" schemes and not "provisional" ones.

Does this apply in any way to us?

> RFC 4395 requires that permanent scheme definitions be "Well-defined". Leaving in syntactic components and declaring them "out of scope"  is leaving them undefined.

The only parts the semantics of which were flagged as "outside the scope" were fragment and query  this section has been removed.

> Suggestion: Remove 'authority' from the syntax, and any sections that
>  refer to them; disallow query components
> Alternate Suggestion: define the meaning of "authority" and query components.

Neither the authority nor the query components are undefined or out of scope. Authority is syntactically defined, and is clearly specified as being devoid of semantics (opaque). Stating that this makes the scheme not "well-defined" is untrue  it is like saying that XML Namespaces aren't well-defined because they are equally opaque.

The query component is equally defined as to its syntax, and its meaning is left to the processor (typically, a script inside an HTML page, but for other resources it could be different). I can't see how this differs from the http scheme.

-- 
Robin Berjon - http://berjon.com/
Received on Thursday, 19 November 2009 14:14:04 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT