W3C home > Mailing lists > Public > public-iri@w3.org > March 2009

Re: Path Normalization Causing Issues

From: Martin Duerst <duerst@it.aoyama.ac.jp>
Date: Mon, 09 Mar 2009 15:11:23 +0900
Message-Id: <6.0.0.20.2.20090309150735.07b6e798@localhost>
To: Geoffrey Sneddon <foolistbar@googlemail.com>, public-iri@w3.org
Hello Geoffrey,

I think your question is not specific to IRIs, it is exactly the
same for URIs. I suggest you send your question to uri@w3.org,
the URI mailing list. If a relative ".." will end up as ""
for URIs, it has to be the same for IRIs.

Regards,   Martin.

At 02:03 08/09/10, Geoffrey Sneddon wrote:
>
>If you try and normalize the following two IRIs:
>
>".."
>"http://example.com/foobar/"
>
>You end up with:
>
>""
>"http://example.com/foobar/"
>
>Then resolve the former as relative to the latter:
>
>"http://example.com/foobar/"
>
>This this is per section 5.3.2.4. of RFC3987:
>> The complete path segments "." and ".." are intended only for use  
>> within relative references (section 4.1 of [RFC3986]) and are  
>> removed as part of the reference resolution process (section 5.2 of  
>> [RFC3986]). However, some implementations may incorrectly assume  
>> that reference resolution is not necessary when the reference is  
>> already an IRI, and thus fail to remove dot-segments when they occur  
>> in non-relative paths. IRI normalizers should remove dot-segments by  
>> applying the remove_dot_segments algorithm to the path, as described  
>> in section 5.2.4 of [RFC3986].
>
>As ".." is an IRI, it can be normalized, which results in "". This is  
>obviously problematic. Should path segment normalization only be done  
>when there is a scheme and/or authority?
>
>
>--
>Geoffrey Sneddon
><http://gsnedders.com/>
>
>


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     
Received on Monday, 9 March 2009 08:03:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:51:54 GMT