ws-tx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ws-tx] Issue 015: Replace namespace and action URIs [RDDL documents]
- From: Ian Robinson <ian_robinson@uk.ibm.com>
- To: "Ram Jeyaraman" <Ram.Jeyaraman@microsoft.com>
- Date: Mon, 13 Mar 2006 18:03:46 +0000
Ram, one comment.
In the RDDLS the various "specification" links should point to
http://docs.oasis-open.org/ws-tx/{spec}/2006/03/wstx-{spec}-1.1-spec-cd-01
.pdf
rather than
http://docs.oasis-open.org/ws-tx/{spec}/2006/03/wstx-{spec}-1.1-spec-wd-03
.pdf
(i.e. cd-01 rather than wd-03).
Regards,
Ian Robinson
STSM, WebSphere Messaging and Transactions Architect
IBM Hursley Lab, UK
ian_robinson@uk.ibm.com
"Ram Jeyaraman"
<Ram.Jeyaraman@mi
crosoft.com> To
<ws-tx@lists.oasis-open.org>
09/03/2006 02:05 cc
Subject
[ws-tx] Issue 015: Replace
namespace and action URIs [RDDL
documents]
As part of the resolution to issue i015, we agreed to provide RDDL
documents for the resources (specification, XSD and WSDL documents).
Please find attached the RDDL documents for WS-Coordination, WS-AT and
WS-BA.
These documents should be published at the time of our first Committee
Draft publication. At the time of publication, the resource URI’s contained
in these documents must be updated to point to the correct resources
(specification, XSD and WSDL document locations). Thanks.(See attached
file: wstx-wsat-1.1-rddl.htm)(See attached file: wstx-wsba-1.1-rddl.htm)
(See attached file: wstx-wscoor-1.1-rddl.htm)
Title: Web Services Atomic Transaction
Web Services Atomic Transaction (WS-AtomicTransaction)
March 2006
Introduction
This document describes version 1.1 of the
WS-AtomicTransaction namespace. It also contains a directory of links to
related resources using
Resource Directory Description Language (RDDL) 2.0.
Namespace URI Versioning Policy
The pattern of the WS-AtomicTransaction v1.1 namespace URI shall be:
http://docs.oasis-open.org/ws-tx/wsat/yyyy/mm
Where yyyymm is the century, year and month chosen by the TC for
that version of the namespace URI.
It is the intent of the OASIS WS-TX Technical Committee that the
WS-AtomicTransaction v1.1 namespace URI will not change arbitrarily with each
subsequent revision of the corresponding WSDL or XML Schema documents but
rather change only when a subsequent revision, published in conjunction with
a Committee Draft or Committee Specification results in non-backwardly
compatible changes from a previously published Committee Draft or
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.
Related Resources for WS-AtomicTransaction
Specification:
XML Schema:
WSDL:
Title: Web Services Atomic Transaction
Web Services Business Activity (WS-BusinessActivity)
March 2006
Introduction
This document describes version 1.1 of the
WS-BusinessActivity namespace. It also contains a directory of links to
related resources using
Resource Directory Description Language (RDDL) 2.0.
Namespace URI Versioning Policy
The pattern of the WS-BusinessActivity v1.1 namespace URI shall be:
http://docs.oasis-open.org/ws-tx/wsat/yyyy/mm
Where yyyymm is the century, year and month chosen by the TC for
that version of the namespace URI.
It is the intent of the OASIS WS-TX Technical Committee that the
WS-BusinessActivity v1.1 namespace URI will not change arbitrarily with each
subsequent revision of the corresponding WSDL or XML Schema documents but
rather change only when a subsequent revision, published in conjunction with
a Committee Draft or Committee Specification results in non-backwardly
compatible changes from a previously published Committee Draft or
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.
Related Resources for WS-BusinessActivity
Specification:
XML Schema:
WSDL:
Title: Web Services Coordination
Web Services Coordination (WS-Coordination)
March 2006
Introduction
This document describes version 1.1 of the
WS-Coordination namespace. It also contains a directory of links to
related resources using
Resource Directory Description Language (RDDL) 2.0.
Namespace URI Versioning Policy
The pattern of the WS-Coordination v1.1 namespace URI shall be:
http://docs.oasis-open.org/ws-tx/wscoor/yyyy/mm
Where yyyymm is the century, year and month chosen by the TC for
that version of the namespace URI.
It is the intent of the OASIS WS-TX Technical Committee that the
WS-Coordination v1.1 namespace URI will not change arbitrarily with each
subsequent revision of the corresponding WSDL or XML Schema documents but
rather change only when a subsequent revision, published in conjunction with
a Committee Draft or Committee Specification results in non-backwardly
compatible changes from a previously published Committee Draft or
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.
Related Resources for WS-Coordination
Specification:
XML Schema:
WSDL:
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]