Hi Ishara, Your proposal should have a high level design of the XNI component which would support xml:id and cover the functional requirements we've been discussing. It should also contain some detail about how the component would be integrated into the parser's pipeline as well as how the user would enable this feature (probably just need a new feature string; some examples here [1]) through the SAX and DOM parser APIs.
If you're looking for examples of existing components there are several in the org.apache.xerces.impl package. org.apache.xerces.parsers.XML11Configuration would be a good class to look at to get a feel for how XNI components are integrated together to form a pipeline. Thanks. [1] http://xerces.apache.org/xerces2-j/features.html Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org ishara karunarathna <isharaar...@gmail.com> wrote on 03/28/2011 06:55:21 AM: > Hi Michael, > > At the moment I am Xerces source code and studying how should it be > implemented. but still I haven't clear idea how to start > and I don't have idea what implementation detail should be included > to the proposal. > > so could you please let me know how to start this > what kind of implementation detail should be added to the proposal. > what are the things I should further study. > > > Thank you, > Ishara Karunarathna.
