Re: Divide the problem

> a similar result, that is. using schemaLocation involves cluttering
> instances with xml-schema-specific markup; it's not compatible with
> the usage I expect to be typical:

> xhtml + mathml example.

That is exactly the case where you'll need  schemaLocation

"http://www.w3.org/1999/xhtml

doesn't identify which schema for XHTML  against which you want to validate

xmlns="http://www.w3.org/1998/Math/MathML">
and that doesn't say whether its mathml 1 or 2

and neither of them specify the wrapper schema that'll be needed to
say whereabouts in html you want to allow mathml.

The document is a well formed document conforming to the namespace
spec, and that's what this list is talking about. Schema validation is
something else and will almost always require an explicit schema
location (perhaps as with sgml open catalogs, simple cases may be able
to default the schema location based on the top level element
name/namespace) 

David

Received on Thursday, 8 June 2000 12:26:10 UTC