-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi David,
David Lichteblau wrote:
Quoting Sunil Mishra (smishra@sfmishras.com):
I had another thought concerning the DOM API in cxml. Have you considered creating an independent out of the DOM API, just as there is a separate package in Java that does nothing but create the interface
IMO that would be worth it if and only if there is at least one other DOM implementation willing to use it.
Agreed. But there is a chicken-and-egg situation here: without a re-usable DOM API, there will never be another piece of software that re-uses the DOM API.
classes for the DOM API? Having such a standard API to program against does make it possible to develop other CL packages (such as an XPath parser) without having to commit to a specific XML parser.
Hopefully XPath can be implemented based on a simpler interface, something more general than DOM. ISTR that CL-XML uses infoset-like function names.
Well, given that:
1. I can't find the XPath implementation of CL-XML; and 2. My XPath implementation is less than a toy at present
I am not going to pursue this matter any further, other than state an opinion that having a standard API available for multiple pieces of software to use can at least theoretically lead to the development of independent inter-operable modules. There has been *some* success due to this approach in the Java world.
Sunil