Hi Kohsuke, Many thanks for the response. Any no apologies required for missing the point - my original posting was not sufficiently clear. I will try again.
I have an XML document with an xinclude/xpointer element in it. The included document may itself have an xinclude element, and so on. XInclude documents cannot be validated until after the aggregate document is assembled, i.e. after the xinclude elements are evaluated and the relevant substitution performed. One feature of xpointer is for it to select the element from the included document based on its schema-determined ID. To find the schema-determined ID, I think I need access to the schema before the document is validated. Hence, I need to load the schema myself. I'm not sure how to load the scheme. I would prefer to load it in a way that the subsequent validation can use the pre-load scheme rather than having to load it all over again. Hope this makes my problem clearer. Thanks and regards Dean Chalker > -----Original Message----- > From: Kohsuke Kawaguchi [mailto:[EMAIL PROTECTED] > Sent: Thursday, 4 December 2003 5:15 AM > To: [EMAIL PROTECTED] > Subject: Re: XMLSchema assistance requested > > > > > XPointer has a shorthand syntax which locates and includes > an element by its > > id. So I need to be able to determine the attribute that is a > > schema-determined ID, or a DTD-determined ID. > > > > This is confused that XML containing XIncludes can't be > validated until > > *after* the XInclude has assembled the aggregate document. > Sadly,I need the > > schema to be able to evaluate the XPointer shorthand to be > able to assemble > > the aggregate document. > > I'm not familiar with XInclude, but you can use ID to identify the > fragment to be included, right? > > So isn't it just a matter of setting up another parser with whatever > validator you care, then run that pipeline until you find > the right ID? > > Then you can forward the sub-tree into the main pipeline? > > Sorry if I'm missing the point. > > regards, > -- > Kohsuke Kawaguchi > Sun Microsystems [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
