W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2000

I18N Last Call comments on Canonical XML

From: Martin J. Duerst <duerst@w3.org>
Date: Tue, 01 Aug 2000 18:22:59 +0900
Message-Id: <4.2.0.58.J.20000801172126.02687d30@sh.w3.mag.keio.ac.jp>
To: w3c-ietf-xmldsig@w3.org
Cc: www-international@w3.org
Hello John, dear XMLDSig WG,

Here are some i18n last call comments on Canonical XML.
Sorry for the delay.

- Canonical XML should include and xml declaration with
   the version information. This is important because
   there is some chance that a future version of XML
   will be defined to allow newly encoded characters
   in Unicode to be used in element/attribute names
   (e.g. Mongolian, Khmer,...).

- Various things that were added to XML Signature
   have to be added here, too:

   - UTF-8 doesn't have a BOM
   - For conversion, please be careful (see Japanese
     XML profile, http://www.w3.org/TR/japanese-xml/).

   For details and text, please see some recent mail
   and the XML Signature spec.

- 'a UTF-8 encoding': There is only one UTF-8. Change
   e.g. to 'encoded as UTF-8'.

- Appendix A.1 should not use the word 'recommended'
   for the [CharModel] document, as that document is
   not (yet, I hope) a recommendation.

- Appendix A.1 should specifically say that security
   concerns were responsible for removing character
   normalization.

- The special provisions for xml:lang (and xml:space)
   on document subsets are appreciated.


Regards,    Martin.
Received on Tuesday, 1 August 2000 05:24:20 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:10 GMT