Re: "absolute URI reference" considered awkward (and in one case, overly constraining)

> Trouble is the RFC process (as I understand it) is pretty 
> nondeterministic, and it's gonna REALLY SUCK if the W3C and the IETF mean 
> different things when they say "URI".  It would be so much nicer if we 
> could have some comfort that there will be consistency.

The RFC process is a lot more deterministic than the W3C process.
Those who show up with an opinion AND an implementation determine
what goes in the standard.  People who do not show up, or who just
have an opinion, have to depend on others.

The issue is well-known.  The problem has been that some folks don't
consider the fragment to be part of the URI, and for good reason:
outside of the href element, it has no relationship with the URI.
They aren't processed together, they aren't dependent on one another,
and they don't communicate the same concepts.  The only way to
justify them being joined together is to first define what a
resource is and then define a fragment as an identifier of a
resource, which is not a technical argument.  So, the majority of
opinions will carry the issue and people who do not express their
opinions on uri@w3.org will not be heard.

....Roy

Received on Saturday, 7 September 2002 06:10:45 UTC