I'm sorry if it's my another stupid thought,


> Curt Arnold expects much more information that that. For schema, he needs:
> - namespace
> - location hints (consider the case of multiple *import* and
> *xsi:schemaLocation* for the same namespace
> - element/attribute/xsi:type name (if the loading is triggered in the
> instance by an element/attribute/xsi:type)
> - other attribute name/value pairs (it's possible that the decision of
> which grammar location to use depends on a *version* attribute)

It occurred to me that these problems may be easily solved if we can
place an XNI component before XML Schema validator XNI component.

The preceding component can read xsi:schemaLocation or any other
attributes, PIs, comments, whatever information available. Then it
can instruct the XML Schema validator component to use more NSSchema
objects for the validation. After that, it pass XNI events forward.


Or am I missing something?

regards,
----------------------
K.Kawaguchi
E-Mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to