Since Chris has raised this formally I
will ask that the proposal be modified to change the following text:
“It is the intent of the WS-RX TC
members that the namespace URI will not
change arbitrarily with each subsequent revision
of the corresponding WSDL
or XML Schema document, but rather change
only when a subsequent revision,
published in conjunction with a
Committee Specification results in
non-backwardly compatible changes from a
previously published
Committee Specification.”
to refer to “Committee
Drafts/Specification” instead of “Committee Specification”.
This was discussed at the Dec F2F and the minutes
indicate that we agreed to this direction:
> Gil: For subsequent CDs the editors change the namespace.
This is in Namespace evolution policy for TC. The namespace will not change on
subsequent WDs.
/paulc
From: Christopher B
Ferris [mailto:chrisfer@us.ibm.com]
Sent: January 19, 2006 9:07 AM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] [New Issue[
versioning policy
A little birdy told me that we addressed the versioning
policy AI#25 [2] at the Sept f2f [1], but that there
was
no formal motion to accept the proposal (sigh). So, I'd like to formally open
an issue to adopt the
language
that PaulC and I worked up [3] tweaked to accomodate the namespace URI scheme
that
we modified to include the TC name path component preceding the [product] path
component.
Title:
Versioning policy
Description/Justification: Our specs need a
formally adopted namespace versioning policy.
Target: specs
Type: design
Proposal: Add a new subsection following section
1.3 Namespace of both the wsrm and wsrmp
specifications
as follows:
Namespace
Versioning Policy
The following is the declared policy of this
specification with regards to
the namespace URI assignment for both the related
XML Schema and WSDL definitions.
The pattern of the namespace URI shall be:
http://docs.oasis-open.org/ws-rx/[product]/yyyymm/
Where [product] is the short name of the
specification as prescribed by
OASIS followed by the century, year and month
chosen by the TC.
It is the intent of the WS-RX TC members that the
namespace URI will not
change arbitrarily with each subsequent revision
of the corresponding WSDL or XML Schema
document, but rather change only when a subsequent
revision, published in conjunction with a Committee Specification results
in non-backwardly compatible changes from a previously published Committee
Specification.
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 operations within a WSDL
portType or binding (along with
the corresponding
schema, message and part 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 instance would
remain valid
* modifications to the cardinality of 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
The policy for namesapce URI assignment between
subsequent revisions of TC
editors drafts shall be to retain the same namespace
URI regardless of the nature of the
changes. Prior to adoption of a new Committee
Specification, the TC will assess the
backwards-compatibility of the schema and WSDL
documents with the prior Committee Specification (if any) and either retain the
namespace URI or assign a new one in accordance with this policy.
An RDDL document shall be made available at the
namespace URI location
that will provide a link to the actual location of
the relevant XML Schema or WSDL
definitions documents. When appropriate, the RDDL
will provide links to the deprecated revisions of the XML Schema and WSDL
definitions documents that carry the same namespace URI.
[1]
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14693/MinutesWSRXF2f-0905.htm#_Toc115510906
[2]
http://www.oasis-open.org/apps/org/workgroup/ws-rx/members/action_item.php?action_item_id=1004
[3]
http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/archives/200509/msg00189.html
Cheers,
Christopher
Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295