[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Joel Rees <email@example.com>
- To: "Jeremy H. Griffith" <firstname.lastname@example.org>
- Date: Tue, 10 Jul 2001 19:46:39 +0900
Jeremy H. Griffith enthused:
> On Tue, 10 Jul 2001 12:18:09 +0700, James Clark <email@example.com> wrote:
> >At least I think one should consider easing draconian error handling
> >for bad name characters to reduce deployment problems with option 2.
> I think you've got it. As usual. <g> What if *all* characters were
> acceptable as name characters, excluding only the very short list of
> those that collide with XML syntax itself? For starters, that could
> be only < > / " ' [ ] ? ! = and the sequence "--". And also cease
> making a distinction between the first and subsequent name characters.
> This would preserve total backward data compatibility, simplify parsers,
> and would never need to be revisited later. Some new documents might be
> rejected by old parsers, but old documents would be fine. Inclusive in
> every sense of the word.
> -- Jeremy H. Griffith, at Omni Systems Inc.
> (firstname.lastname@example.org) http://www.omsys.com/
In addition to the problem code points Christopher Maden refers to, Japanese
character codes include those lousy double-width characters, and UNICODE had
to include them for round-tripping, and they happen to duplicate all the
characters on the explicitly reserved list. This could be confusing to human
parsers seeing double width angle brackets in an identifier.
Easing the rules is one thing, but opening them too wide is another. At any
rate, round-trip punctuation characters should probably not be accepted.
programmer -- email@example.com
To be a tree supporting all information,
giving root to the chaos
and branches to the trivia,
information breathing anew --
This is the aim of Yggdrasill.
============================XML as Best Solution===
Media Fusion Co. ,Ltd. 株式会社メディアフュージョン
Amagasaki TEL 81-6-6415-2560 FAX 81-6-6415-2556
Tokyo TEL 81-3-3516-2566 FAX 81-3-3516-2567