I agree with, Michael. DOM was an intermediate store for Schema information (in the XSSerializer), and it's probably not right to take it as input for SCD processing. But this could be explored later, as needed by the community.
It seems that, SCD spec only defines the addressing mechanism for schema components. It doesn't specify an evaluation semantics of the SCD path expressions. The SCD spec, seems to leave open the usage of SCD path language, in different imaginable environments. So for example, there could be systems which could function in following ways: 1. Given a schema XSModel as input, a SCD path evaluation on XSModel could return a list of XSModel objects (for example a XSObjectList. ref, http://xerces.apache.org/xerces2-j/javadocs/xs/org/apache/xerces/xs/XSObjectList.html). 2. Or say, given a lexical XSD syntax and a SCD path applied to the lexical schema, one could retrieve schema components as some sort of list (say a list of tuples of some sort) for example. But I guess, the option 1 above is a good starting point of Xerces SCD implementation. On Tue, Feb 23, 2010 at 7:00 PM, Michael Glavassevich <[email protected]> wrote: > 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] -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
