XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Question on XML Schema 1.1 [vc:maxVersion]

On 10/01/2011 22:29, Ramkumar Menon wrote:

Sorry for the delay in responding to this. If you are interested in such 
questions, asking on the W3C schema-dev list would be a better way of 
getting information and feedback.
> Gurus,
> Two questions on the version control namespace in XML Schema 1.1.
>  a) Why did we chose to have maxVersion be exclusive of the value?
>      i.e.
> <element name="Price" vc:minVersion="1.1" vc:maxVersion="2.4"/>
>    Its tricky for a person to read this as
>    "Price" element will be removed on pre-processing if we are using 
> XSD version 2.4.

The rule was adopted so that you can say that you want your schema to 
work with all the 1.x releases but not with 2.0, without knowing how 
many 1.x releases there will be. (In practice, I'd be inclined to write 
vc:maxVersion="1.99999" as it seems clearer to the reader.)
> b) Are we assuming that version numbers for XML Schema MUST be 
> decimals, now and later? Exposing terms such as minVersion and 
> maxVersion indicate so.
>
Yes. We thought it unlikely that W3C would depart from the practice of 
using decimal numbers as version numbers for the specification. If there 
were a primitive type for "Dewey-decimal" type numbering (1.5.7.2) then 
we might well have chosen it; but there isn't, and defining such a type 
for this specific purpose would be overkill.

Michael Kay
Saxonica


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS