Lists Home |
Date Index |
Amy Lewis wrote:
> Which is to say, I don't think it's really an issue of coupling, but
> an issue of ambiguity, as Simon (and Len) originally suggested.
> Using a form (syntax) that carries extremely heavy connotations of an
> associated semantic, and violating that semantic (here I'm not
> speaking of the location algorithm, but of case-sensitivity,
> encoding, and resolution only, mind), is just guaranteed to produce
> confusion. Witness the 3000-message thread that Just Won't Die (and
> TBL reopened it with a suggestion that "relative URIs", an utterly
> *meaningless* concept when namespace names have been divorced from
> URI semantic (say "relative string" and "absolute string" and see
> what meaning you can discover), are not all that bad after all ...
That's an excellent summary of what concerns me in the W3C's use of
I'm well aware of the difference between signified and signifier, and
appreciate that the looseness of the connection between them. At the
same time, however, I recognize that reusing signifiers (or simply the
syntax used by a particular class of signifier) brings with it seemingly
infinite potential for confusion.
There are bigger problems here than the lack of a normative document for
URLs. I like that "relative string" bit, though!
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!