OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Blueberry/Unicode/XML

Don Park wrote:

> No, I did not mean that </> could be a start tag for an element named "/".
> Marcus, don't you think you are nitpicking over details which are best
> worked out after some consensus gathers behind James' proposal?

Sorry Don, please advise me when the appropriate moment arises for further

In the mean time, another concern is the fact that by allowing all characters
to be name characters, we forgo the possibility of sequestering a currenly
illegal character for a purpose similar to the way that the colon has been
used to represent a namespace. Are we now certain that we don't need to keep
any characters in reserve for the future? (We only got away with redefining
the colon because it happened early enough in the in the piece.) Would those
who use non-ASCII character sets feel obliged to reserve their own set of
characters for the same purpose? If so, the proposal would not eliminate the
problem, only make it very, very much smaller. Parsers would still have to
keep pace with languages... I suspect this is why Len feels that this is an
SGML problem - the easiest way for the parser to keep pace is to be provided
with a map of characters at processing time.


Marcus Carr                      email:  mrc@allette.com.au
Allette Systems (Australia)      www:    http://www.allette.com.au
"Everything should be made as simple as possible, but not simpler."
       - Einstein