[capidl] Re: [EROS-Arch] capidl alive again

[Jonathan S. Shapiro]

> I also recommend that we define the subset of
> XML and DTDs that we'll use for this project.  I could stand Minimal-XMLs
+
> attributes.  I could stand...

We had previously agreed that the user could specify the DTD for the
documentation input, which means that (a) we must support full XML, at least
to the extent of being able to pass it through, and (b) we must support the
namespaces proposal so as to keep the capidl namespace cleanly separated
from the user-supplied documentation namespace.

Neither of these, in practice, seems burdensome.

Different projects will, of course, define documentation DTDs appropriate to
their needs. If the right one for E is to use a MinXML type of DTD, then
please by all means do so. The only real requirement on CapIDL here is that
the XML parser support full XML. Given the level of wide acceptance, it's
pretty clear that CapIDL should be build on Xalan, which already provides
full XML. Xerces (the XSLT processor) provides full Xpath compatibility, so
I assume that they got the semantics right to the extent that it is possible
to do so.

shap