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

RE: participating communities (was XML Blueberry)

• From: "Bullard, Claude L (Len)" <clbullar@i...>
• To: Joel Rees <rees@m...>
• Date: Thu, 12 Jul 2001 08:40:55 -0500

If the XML Core WG cannot be convinced to 
accept the consequences of cultural eugenics, 
then yes, that is precisely what should be 
done.  I support interoperability but not 
at the cost of cultural diversity.

Business decisions do not free us from 
responsibility to the world community. 
We must never go down that path.  The 
lessons of the 20th century were not 
that government or business were bad, 
but that we must not tolerate bad government 
or bad business.  It's a "world" wide web; 
not a web of programmer-elites.

Len
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Joel Rees [mailto:rees@s...]

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@m...
----------------------------------------------------
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
                       http://www.mediafusion.co.jp
===================================================


Bullard, Claude L (Len) ??:

> Thanks.  If I reload SoftQuad Author/Editor and load
> the right declaration, I should be able to use the
> XML software too.  Nice how that works.
>
> SGML is still there in case given decisions such as "we don't
> want these characters in XML because given the business
> case, we don't need them", those who do need them can.
>
[snipped]

• Prev by Date: RE: xslt
• Next by Date: RE: building an object model of a XML schema
• Previous by thread: Re: participating communities (was XML Blueberry)
• Next by thread: Conformance testing info
• Index(es):
  • Date
  • Thread