[Bug 5168] vc:maxVersion versioning

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5168

           Summary: vc:maxVersion versioning
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: johnarwe@us.ibm.com
         QAContact: www-xml-schema-comments@w3.org


4.2.1 The support as described includes the schema components if the
vc:minVersion <= actual version <= vc:maxVersion.  That means I have to know
the full range of version numbers, including point releases, a priori in order
to construct a continuous range of schema components.  Using the example in
4.2.1, if someone later does a point release of 3.1, e.g. 3.15, I have to
update my schemas.

It seems perfectly valid to want to express the maxVersion semantic as "my
schema component does NOT apply (should not be included) starting with version
x.y".  In 4.2.1's example, x.y=3.2.  That way if someone creates a point
release 3.15 after my 3.1 schema is out, I do not need to deploy any updates to
that schema.  Given the usual rules around breaking changes and versioning, my
case would seem the more common one.

Proposal: include the schema components if vc:minVersion <= version <
vc:maxVersion (change maxVersion comparison from <= to strictly <).

Received on Tuesday, 9 October 2007 14:32:27 UTC