Re: A proposed solution

> The proposal says that in order for you to handle relative URIs

Hmm so why the reference to

>  A URI space is typically defined with a set of
> properties concerning uniqueness,

which I read as refering to _absolute_ URI and in particular the uri
schmeme specific notions of equivalence like
http://www.w3.org being equivalent to http://WWW.w3.org.

I am much relieved to hear that you are not proposing that an
application would ever take those two strings to denote the same
namespace. 

On relative URI basically you are just chosing the "undefined" option.
I think? Within a tightly controlled set of applications you may do
whatever you like, but the real question is what infoset properties
does a standalone XML namespace parser return if given

<x xmlns="relative"/>

with no other context as to who created the document and why.

You say

> An application is responsible for knowing the context within which a
> relative link is defined.

But how can a parser (in general) know anything at all about its input
except for information that is actually contained there.

Or is your proposal is that this is an error, to let such a
document out of your control and into the clutches of a "standalone
parser" ?

David

Received on Friday, 9 June 2000 13:30:05 UTC