Re: The "deprecate/fixed-base" option

-----Original Message-----
From: David Carlisle <david@dcarlisle.demon.co.uk>
To: cce@clarkevans.com <cce@clarkevans.com>
Cc: xml-uri@w3.org <xml-uri@w3.org>
Date: Thursday, June 08, 2000 1:48 PM
Subject: Re: The "deprecate/fixed-base" option


>
>> Given "http://www.w3c.org/2000/Namespaces/base", what would
>> happen if my relative namespace is..."../../../../pop_empty_stack"


You get    http://www.w3c.org/pop_empty_stack


>you get whatever John answers in response to
>
>me> Probably you'd need to say (for the record) whether relative paths
>me> with too many ../ were an error or whether any of the fallback options
>me> which I think are mentioned in the RFC are taken. (having a fixed
>me> base with a relatively deep path section would avoid this problem in
>me> practice)



The URI specification handles that.  You can not pop off a part between //
and the next /


Tim BL