W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > August 2006

Re: c14n note status

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 30 Aug 2006 15:56:48 +0200
To: Konrad Lanz <Konrad.Lanz@iaik.tugraz.at>
Cc: Jose Kahan <jose.kahan@w3.org>, public-xml-core-wg@w3.org
Message-ID: <20060830135648.GC14696@raktajino.does-not-exist.org>

I'm committing a modified version of the draft note; comments below.

On 2006-08-23 12:03:27 +0200, Konrad Lanz wrote:
> From: Konrad Lanz <Konrad.Lanz@iaik.tugraz.at>
> To: Thomas Roessler <tlr@w3.org>
> Cc: Jose Kahan <jose.kahan@w3.org>
> Date: Wed, 23 Aug 2006 12:03:27 +0200
> Subject: Re: c14n note status
> X-Spam-Level: 
> 
> Hi Jose and Thomas,
> 
> may I suggest the following changes to the c14n Note 
> (http://www.w3.org/2006/04/c14n-note/c14n-note.html),
> 
> Section 2:
> 
>    *
> 
>      |xml:base| values may include fragments (= noop)

Changed to "consist of only a fragment identifier (this is a no-op)"

>    *
> 
>      |xml:base| values may be empty (= noop)
> 
>    *
> 
>      |xml:base| values may be absolute or relative URI references
> 
> @@@Comment: To make clear up front what is a no-p.

ok

> Section 5.1:
> 
>    Some special considerations are needed. When normalizing a relative
>    URI reference, it is crucial to keep the leading "../" segments of
>    relative-path references. Otherwise path-segments of ancestor's
>    xml:base URI references that are to be removed will not be removed.
>    Another issue is that one could create erroneous output that looks
>    similiar to that of a network-path reference when normalizing an
>    absolute-path reference. For instance, an incorrect normalization of
>    |"seg/.././/pseudo-networkpath/seg/file.ext"| would be
>    |//pseudo-netpath/seg/file.ext|.
>    Note: [RFC 3986, Section 4.2
>    <http://www.w3.org/2006/04/c14n-note/c14n-note.html#RFC3986>]
>    defines the terms relative-path, network-path and absolute-path
>    reference.
> 
> 
> @@@Comment: This change is needed to emphasize that there are two issues 
> (leading ../ segments and pseudo-netpath) to be tackled.

ok.  It would make things smoother if you could just send XML
snippets that can be copied and pasted into the note.

> Section 5.3: 
> @@@Comment: requireing --> requiring

ok

-- 
Thomas Roessler, W3C   <tlr@w3.org>
Received on Wednesday, 30 August 2006 13:57:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:34 GMT