Re: normalization-form serialization option

On 11/29/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Norman Walsh writes:
>
> > The serialization section includes a normalization-form parameter but
> > none of the steps that have the serialization options include a
> > normalization-form option. This is just an oversight, right?
>
> Most (serialize, store, http-request) do, only escape-markup doesn't.
> I guess we need to ask Alex if there's a reason. . .
>
> ht
> - --
>  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
>                      Half-time member of W3C Team
>     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
>             Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
>                    URL: http://www.ltg.ed.ac.uk/~ht/
> [mail really from me _always_ has this .sig -- mail without it is forged spam]
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFHTt4okjnJixAXWBoRAsjMAJ9T5GRgDfSt6JNiJIl0XPR/RMEx2wCeIzHD
> sSYq2q+iN0rn4NCSOxcHXBo=
> =zNTP
> -----END PGP SIGNATURE-----
>
>

You can't normalize because that's an encoding issue and
the content isn't encoded to a byte stream.

I've added a note that clarifies this.



-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics

Received on Wednesday, 16 January 2008 22:46:16 UTC