Keep in mind that SCD is an addressing mechanism for schema components and that the DOM is a schema document representation. You can't evaluate a SCD directly against it. Needs to be processed first into schema components which in Xerces ends up producing an XSModel. Like Hiranya said, I believe the focus should be on getting something working with the XSModel first. Other inputs could be added as convenience methods in the future.
Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected] Hiranya Jayathilaka <[email protected]> wrote on 02/23/2010 08:19:31 AM: > Hi Ishan, > > On Tue, Feb 23, 2010 at 6:21 PM, Ishan Jayawardena <[email protected]> wrote: > Thanks Mukul. So, as you have told me about the two possible > implementations of the SCD, those two give out two different object > types as the out put. Am I correct? > So what do you think should be the implementation based on? On the > Xerces based XSModel Schema objects, or standard DOM nodes? Or else > should it be implemented for both types? Since the implementation is > intended for Xerces, is the first type more suitable? > > IMO as far as Xerces is concerned implementing SCD support for > Xerces XSModel is good enough (at least for now). And I would > suggest you do your first cut implementation based on XSModel. But > having SCD support for DOM would be a great feature addition too. > Since DOM is very popular in industrial applications this will have > some value. > > However I believe you are planning to do this for your GSoC project, > isn't it? In that case please take the time constraints into account > when planning your project and preparing the proposals. > > Thanks, > Hiranya > > thank you. > > On Tue, Feb 23, 2010 at 6:03 PM, Mukul Gandhi <[email protected]> wrote:> > Hi Ishan, > > On Tue, Feb 23, 2010 at 5:40 PM, Ishan Jayawardena <[email protected]> wrote: > > For an example can't we build a Schema DOM with the DOM implementation > > available for XML? > By Schema DOM, I meant the DOM object constructed from the XSD schema > grammar as input. > > > Can you please tell me the exact usage of XSModel? The > > only thing I know is that it's an object model for schema. But what really > > makes it different from DOM? > DOM is a vendor neutral generic XML object model, with an API that is > defined by W3C. Whereas, XSModel is a Schema object model which is > specific to Xerces. But Xerces XSModel, also implements the following > XML Schema API (ref, > http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309/). > > > you've said that it's possible to create a Schema DOM with > > XSSerializer utility. Is that the only way that one can build a DOM for a > > schema? > The XSSerializer utility, builds a DOM representation of the schema, > taking XSModel as an input. > > Ofcourse, one could build a DOM object directly from a Schema file (or > a schema URI), using say: > DocumentBuilder.parse .... > > > Are there any serious implementation differences of the DOM for a > > schema from that of an XML? > DOM for a XML could be for any XML vocabulary. Whereas, DOM for a > schema is for a specific XML Schema document. > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com
