SAX Topic 2004-0003: Unicode normalization

[David Megginson <dmeggin@attglobal.net>]

* Topic 2004-0003: Unicode normalization

- add a feature to request Unicode normalization checking (John Cowan,
   2004-02-18)

- add a read-only feature to indicate that the current document is
   normalized (John Cowan, 2004-02-18); not needed, because if no
   error() is reported after normalization is requested, document is
   normalized (Norm Walsh, 2004-02-20)

- add a feature to XMLReaderFactory, such as
   http://xml.org/sax/features/unicode-normalization-checking; most
   appropriate at the factory level (Norm Walsh, 2004-02-19); Jeff
   Rafter (2004-02-19) and Elliotte Rusty Harold (2004-02-19) disagree;
   Norm wants feature in factory so that factory can return different
   parsers (2004-02-20)

- unicode-normalization-checking should be false by default (Elliotte
   Rusty Harold, 2004-02-19)

- errors should be reported through the error() callback (Elliotte
   Rusty Harold, 2004-02-19); Norm Walsh agrees (2004-02-20); using
   error() instead of warning() may cause too much noise (Jeff Rafter,
   2004-02-20); should error() or warning() be called only on the first
   problem? (Jeff Rafter, 2004-02-20)

- may want to standardize an exception subtype for normalization
   errors (Elliotte Rusty Harold, 2004-02-19); Norm Walsh agrees
   (2004-02-20)

- feature should be in XMLReader, not in the factory (Jeff Rafter,
   2004-02-19); Elliotte Rusy Harold agrees (2004-02-19);

- normalization transcoding may be a useful feature (Jeff Rafter,
   2004-02-19); that's application-level functionality that belongs in
   a layer above SAX (Norm Walsh, 2004-02-20); could also argue that
   validation is application-level functionality (Karl Waclawek,
   2004-02-20); Jeff Rafter agrees, pointing to separate validating and
   non-validating AElfred parsers (2004-02-20)


All the best,


David