Processing schema - sharing between Xalan and Xerces

[Jon Smirl <jo...@mediaone.net>]

Oracle is splitting their schema processor into a separate project. I think
Xerces/Xalan should also do this.

One of the proposed optimizations for Xalan is to load the schemas of the
input and output documents at XSLT sheet compile time. Xalan would then
build an internal mapping from it's stylesheet rules to the schema. As an
input document was being accepted it would be matched to the nodes in the
compiled schema and Xalan would know immediately the work to perform for
that node.

Currently Xerces reports docElements with an XMLElementDecl that refers to
the schema associated with the document.

If Xerces and Xalan were sharing a common schema object things could be very
high performance. Xalan could leave pointers to it's compiled rules inside
each of the schema nodes.  When Xerces parses the document and matches a tag
to the schema it would just call the method Xalan set up for it.

Jon Smirl
jonsmirl@mediaone.net