- From: Graham Klyne <GK@ninebynine.org>
- Date: Fri, 19 Nov 2004 10:52:25 +0000
- To: "Roy T. Fielding" <fielding@gbiv.com>, "Martin Balaz" <balaz@ii.fmph.uniba.sk>
- Cc: <uri@w3.org>
At 23:57 18/11/04 -0800, Roy T. Fielding wrote:
>On Nov 18, 2004, at 9:17 AM, Martin Balaz wrote:
>>I would like to discuss one old problem of the remove_dot_segments function,
>>which is not yet solved as I know.
>>
>>Following URIs are valid with the respect to the latest rfc2396bis:
>
>No, they are allowed by the syntax. They are not valid.
>
> The path segments "." and "..", also known as dot-segments, are
> defined for relative reference within the path name hierarchy. They
> are intended for use at the beginning of a relative-path reference
> (Section 4.2) for indicating relative position within the
> hierarchical tree of names. This is similar to their role within
> some operating systems' file directory structure to indicate the
> current directory and parent directory, respectively. However,
> unlike a file system, these dot-segments are only interpreted within
> the URI path hierarchy and are removed as part of the resolution
> process (Section 5.2).
>
>It doesn't matter what is the result of processing
>
>>file:/x/..//y
>>file:x/..//y/
>
>because those are not valid file URIs.
Roy, I'm not sure that helps with these test cases:
testRelative84 = testRelJoin "testRelative84"
"f:/a" ".//g"
"f://g"
testRelative89 = testRelJoin "testRelative89"
"f:/a/" "..//g"
"f://g"
or did I miss something else?
#g
------------
Graham Klyne
For email:
http://www.ninebynine.org/#Contact
Received on Friday, 19 November 2004 11:20:01 UTC