[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX Topic 2004-0003: Unicode normalization


unicode normalization checking
----- Original Message ----- 
From: "David Megginson" <dmeggin@a...>
To: "XML Developers List" <xml-dev@l...>
Sent: Sunday, February 22, 2004 9:28 AM
Subject:  SAX Topic 2004-0003: Unicode normalization


> * Topic 2004-0003: Unicode normalization
> 
> - add a feature to request Unicode normalization checking (John Cowan,
>    2004-02-18)

This should not be a "must recognize" feature, as the XML 1.1 spec
does not require it as a "MUST".

> - 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)

Ideally the factory is the better place for it, as it would
be for requesting a validating parser. But what about
backwards compatibility?

> - 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)

Should be called on every problem. If the app decides that
parsing should continue despite an error, that does not mean
that further errors should be kept hidden from it automatically.

It is conceivable to have user options for ignoring certain
kinds of errors. In the case of Unicode normalization:
What about the ability to turn normalization checking
off in the middle of parsing? 
 
> - may want to standardize an exception subtype for normalization
>    errors (Elliotte Rusty Harold, 2004-02-19); Norm Walsh agrees
>    (2004-02-20)

What about a special exceptionId instead?
(I know exception ids are not well standardized yet).
 
Karl

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.