Re: XML Schema language version
"C. M. Sperberg-McQueen" <[email protected]> Wed, 2 Oct 2013 14:38:09 -0600
| Newsgroups | gmane.text.xml.schema.devel |
|---|---|
| Message-ID | <[email protected]> |
On Oct 2, 2013, at 2:12 PM, Michael Kay wrote: > I think it would be a creative but perfectly reasonable interpretation = of the XSD 1.1 specification to advise users to set vc:minVersion=3D"1.0" = or vc:minVersion=3D"1.1" or vc:maxVersion=3D"1.0" on the xs:schema = element to indicate whether they expect to use a 1.0 processor or a 1.1 = processor for the schema, and for an IDE such as oXygen to use this = attribute when selecting a processor to run. >=20 > See http://www.w3.org/TR/xmlschema11-1/#cip That's an elegant idea, much better than the vague notions that were floating around in my mind's eye of using the xml-model PI with a new pseudo-attribute like=20 version=3D"http://www.w3.org/XML/XMLSchema/v1.0" or version=3D"http://www.w3.org/XML/XMLSchema/v1.1" I think vc:minVersion and vc:maxVersion are nicer. To be specific, I think=20 vc:minVersion=3D"1.0" should be taken to mean a 1.0 or a 1.1 processor is fine for validations using this schema, but an editor like Oxygen should check that the schema document uses only 1.0 features, or that any 1.1 features are protected=20 by an appropriate version-control attribute, like=20 vc:minVersion=3D"1.1". vc:maxVersion=3D"1.0" should mean that ONLY a 1.0=20 validator should be used for validation, and that no 1.1 features should be included at all (even with a version-control attribute). vc:minVersion=3D"1.1" should mean that a 1.1 (or higher, if that day were ever to come) processor should be used for validation, and that an editor should check that only 1.1 features are used. Michael --=20 **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com=20 * http://cmsmcq.com/mib =20 * http://balisage.net ****************************************************************