Overloaded URIs (was Re: XLink: behavior must go!)

[James Tauber]

>It strikes me as clearly poor design to use an HTTP url for something not
>retrievable by the HTTP protocol. I am distressed that this is becoming
>"standard practice." How the heck are we supposed to know, on seeing a URI
>whether it is supposed to be retrievable or not?


That's my point. I was proposing an HTTP-like URI scheme that *isn't*
intended to be retrievable, but TimBL didn't see the need.

James


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)