Re: participating communities (was XML Blueberry)

From: Joel Rees <rees@server.mediafusion.co.jp>

To: "Bullard, Claude L (Len)" <clbullar@ingr.com>

Date: Thu, 12 Jul 2001 15:47:57 +0900

Len,
I'm going to have to ask you to give us some clues on your proposition.
Is this more or less the way to do it?
We develop our own markup language, say, "JEKML" (Japaniizu Enchou Kanou
Maaku-appu Lengeeji, eh, Elliot?). We keep it parallel to XML, to keep
things simple (especially when we need to export documents), we include
charset declarations that allow us to use JIS or whatever encodings, and we
set up our own character classification tables, a table for each encoding,
so we can allow what we want for names. And we write the parsers, etc.,
ourselves, probably borrowing liberally from the existing open sourced
parsers. And, of course, somewhere along the line we write the definition in
SGML, just to check it.
And any document that needs to be published to the rest of the world will
need to include a table of name translations. We still aren't confident of
the UNICODE to JIS translation tables, but that should be a problem we can
live with, since we only have to deal with UNICODE in the international
arena. This kind of thing should even help with debugging UNICODE.
Those character classification tables are rather large. Even generating them
mechanically takes several days (a week maybe?) of hand checks. But that's
not really much to pay, if we can pull the rest of it off.
Joel Rees
programmer -- rees@mediafusion.co.jp
----------------------------------------------------
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. $B3t<02q