Big hierarchy of XML Schema documents ... which XML Schemavalidators bri

["Costello, Roger L." <costello@mitre.org>]

Hi Folks,

Suppose that my XML Schema imports/includes some XML Schemas and they import/include some XML Schemas and so on. That is, there is a big hierarchy of XML Schema documents.

I envision two ways that XML Schema validators could be implemented:

1. On-demand: the validator brings in an XML Schema document only when it's needed. (On-demand/Just-in-time/Dynamic-Loading)

2. Not on-demand: when the validator brings in an XML Schema document it also brings in the XML Schema documents it imports/includes and the documents they import/include and so on. (What is the right term for this?)

I am interested to know how these XML Schema validators operate with regard to being on-demand or not. Can you help to fill in this table please:

                 On-demand      Not on-demand
SAXON (Java)

SAXON (.NET)

XERCES (Java)

XERCES (C++)

XERCES (Perl)

LIBXML

MSXML

XSV


/Roger