[E-Lang] Draft Kernel-E DTD & Sketch of translation to debuggable Java

[Tyler Close]

> Tyler, I recall you were doing some XML stuff, but I could
> find it among the
> code I downloaded from you?

The XML stuff was implementing SOAP v1.1 for Droplets. Currently, SOAP
is the main format for two Droplets servers talking to each other.
This code is in the Droplets library, which is Open Source. It's not
on the waterken.com site yet, but I can post a Beta if you want to use
it.

Before you put too much effort into developing E's DOM subset, or
deciding on the use of Minimal-XML, I think we should identify some
target tasks for the use of XML in E. For example, if one of the goals
is to enable E programs to access web resources using SOAP, then
supporting only Minimal-XML would not be a good idea.

I think just accepting XML, in all of its gory detail, is the only
meaningful course of action. Doing anything less just brings all the
disadvantages of XML without providing its main advantage, a common
transport format.

I've posted a new Beta for Acid on the waterken.com site at:
http://www.waterken.com/Acid/2.0/

The new Beta includes the hooks that Droplets uses to support SOAP
messaging. E does not have these hooks (nor any of this richness of
reference types), so I think you should take a look. The design is
different from your "negotiate everything at connect time" approach.

Tyler