Proposed Namespace URI Versioning Policy v2

["Scott Cantor" <cantor.2@osu.edu>]

My mistake, I reread their original text and definitions aside I see now
that their criteria was for listing changes that result in old documents
remaining valid, but new documents not necessarily being valid, which I
would call backward compatible (as they did).

Revised the last bullet back, so the text is as follows.

-- Scott

It is the intent of the OASIS XRI Technical Committee that the Extensible
Resource Descriptor namespace URI will not change arbitrarily with each
subsequent revision of the corresponding XML Schema document but rather
change only when a subsequent revision, published in conjunction with a
Committee Specification, results in backwardly-incompatible changes from a
previously published Committee Specification.

While it is also the intent that backwardly-incompatible changes will not
occur between Committee Drafts, the Technical Committee reserves the right
to make such changes without changing the namespace URI. In such cases,
consultation with the implementation community will be sought before doing
so, but the final decision rests with the TC's voting members.

Under this policy, the following are examples of backwards-compatible
changes that would not result in assignment of a new namespace URI:

    * addition of new global element, attribute, complexType and simpleType
definitions
    * addition of new elements or attributes in locations covered by a
previously specified wildcard
    * modifications to the pattern facet of a type definition for which the
value-space of the previous definition remains valid or for which the
value-space of the preponderance of instances would remain valid
    * modifications to the cardinality of attributes or elements for which
the value-space of possible instance documents conformant to the previous
revision of the schema would still be valid with regards to the revised
cardinality rule


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php