[Bug 4774] definitional schema documents should be preferentially used over all other sources when validating instances


------- Comment #6 from sandygao@ca.ibm.com  2007-11-29 15:12 -------
Revised proposal:

Summary of key points in the proposal:
1 Add a new element <schemaBindings> (parallel to <ruleBindings> we already
2 <schemaBindings> can have any number of <schemaBinding> children, each
specifies a schema that's used to validate instance documents listed inside
this <schemaBinding>. We can use the same "prefix matching" mechanism as
3 <schemaBindings> can have an optional <defaultSchema> child, to specify the
schema used to validate all instance documents not covered any <schemaBinding>.
4 If a <defaultSchema> is not present, then a schema is composed from *all*
schema documents and used to validate instances not covered by any
5 Processors are not required to support <schemaBindings> (that is, they are
allowed to always compose a schema from all schema documents and use it to
validate all instance documents)
6 schemaLocation on <include> and <redefined> are resolved using aliases
7 xsi:schemaLocation attributes and schemaLocation on <import> elements are

Received on Thursday, 29 November 2007 15:12:24 UTC