[Bug 5380] Clarify XSD vs. xsi:schemaLocation attribute


------- Comment #1 from sandygao@ca.ibm.com  2008-01-16 20:07 -------
> Section 4: there is reference to xsi:schemaLocation occurring in Schema
> documents. 

I agree this sentence (in 4.0) is not optimal. Suggest to remove "xsi:". (Just
went back and checked my proposal for this section, and it didn't have "xsi:".
Some kind of copy/paste error must have happened when the proposal was

> Section 4 should more explicitly recognize the distinction between the
> xsi:schemaLocation attributes that typically occurs in model instance
> documents (but must be address wherever it occurs)

They are not required to be addressed. See the first bullet 3 in section 4.3.2
of http://www.w3.org/TR/xmlschema-1/

> vs. the schemaLocation attribute in the XSDL <import> (which also has to be
> addressed).

These are not required to be addressed either. See "Schema Document Location
Strategy" in section 4.3.2 of http://www.w3.org/TR/xmlschema-1/.

I agree that different schema location cases need to be distinguished. This is
implicitly covered in section 5.3.3 and 5.5, where xsi:schemaLocation and
schemaLocation on <xs:import> are ignored (only schemaLocation on <xs:include>
and <xs:redefine> are used).

Don't feel strongly about whether section 4 should give an informal statement
about this situation.

> In particular, section 5.3.3 should address ... the second parameter of the
> xsi:schemaLocation attribute.

I think the decision we made was to ignore xsi:schemaLocation attributes (and
schemaLocation on <xs:import> elements), and use "namespace matching" to locate
relevant schema documents. One reason we chose to do this is to improve
inter-op, because how these attributes are handled almost completely depends on
the schema processor.

Are you suggesting that we should reopen that topic?

Received on Wednesday, 16 January 2008 20:07:06 UTC