Sorry if this turns out to be a duplicate, I seem to be having an issue with new mailing lists.
-- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://blog.parthcomp.com/xerces
--- Begin Message ---Hi,
The caching feature is an optimization. As such, it should have no real impact on how things are validated. Try your examples with caching turned off. If there is a difference after caching is turned on then mail us.
Jeff Greif wrote:This question might alternately be phrased as 'What determines the set of schemas available for a validation episode?'
The schema that your instance document refers to explicitly or implicitly (via namespace) defines the top level schema. That schema may include and import other schemas and if it does then they will be in the set of schemas.
This parser is used to validate a document d1 with a root element in namespace B. Somewhere in the content there is a reference to element a. When the allowed substitutions are determined for a, are b, c and c' in the set, or just b, or some other combination?
The point to focus on here is that the document d1 is associated with the schema that defines namespace B. Any includes or imports will be resolved and that will be the set of things that are used.
Does the XML Schema spec specify what namespaces are involved in a particular validation episode? If so, a pointer to the relevant section (which I've obviously missed) would be helpful. If not, is this a matter left up to the implementation?
There is a section on importing that may be helpful:
http://www.w3.org/TR/xmlschema-1/#composition-schemaImport
Gareth
-- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://blog.parthcomp.com/xerces
--- End Message ---
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
