Hi Ishara, That's about right.
To be more precise the module (XNI component) needs to: 1) Normalize the value of each xml:id attribute. 2) Perform ID type assignment with the normalized value (in other words give it an ID type if it doesn't already have one). 3) Report an error if the constraints on the xml:id are violated (in other words validate the xml:id). 4) Pass the processed xml:id attribute (and other XNI events) to the next component in the pipeline. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected] ishara karunarathna <[email protected]> wrote on 02/20/2011 11:12:48 AM: > Hi Michael, > > I went through these [1] [2] articles and some other documents. > > And I think xml:id provides a unique element identification > mechanism. And it use to over come some pitfalls in > DTD and XML schema based identifiers. > > And adding support for xml:id to Xerces we have to come up with a > module that can. > > 1.Access to the xml:id and identify it. > 2.validate the xml:id. > 3.Parse it to the other processing part. > > This is how I understand the problem and could you please tell me > weather I am on the correct path and how should I improve the background. > > Thank you. > Regards, > Ishara Karunarathna. > > [1] http://www.w3.org/TR/2005/CR-xml-id-20050208/ > [2] http://www.xml.com/pub/a/ws/2005/02/23/salz.html
