W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2007

Re: proposal for namespace versioning policy for mtom assertion

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Wed, 04 Apr 2007 10:03:51 -0700
Message-ID: <4613DA77.9070908@oracle.com>
To: Christopher B Ferris <chrisfer@us.ibm.com>
CC: xml-dist-app@w3.org

 >       Addition of new elements or attributes in locations covered by a
 >       previously specified wildcard

I assume that if the wildcard said namespace="##other", an addition 
would be considered a non-backward compatible change.

-Anish
--

Christopher B Ferris wrote:
> 
> Proposed namespace document for the mtom policy assertion namespace 
> attached.
> 
>  
> 
> Cheers,
> 
> Christopher Ferris
> STSM, Software Group Standards Strategy
> email: chrisfer@us.ibm.com
> blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
> phone: +1 508 377 9295
> ------------------------------------------------------------------------
> 
> W3C <http://www.w3.org/>
> 
> 
>   MTOM Policy Assertion 1.0 Namespace:
>   |http://www.w3.org/@@@/soap12-mtom-policy|
> 
> This (|http://www.w3.org/@@@/soap12-mtom-policy|) is a URI defined in 
> the MTOM Policy Assertion 1.0 
> <http://www.w3.org/@@@/soap12-mtom-policy/> @@@(dated) specifications.
> 
> This document describes the MTOM Policy Assertion 1.0 namespace. A RDDL 
> version <soap12-mtom-policy.xhtml> of this document is available.
> 
> 
>     Latest XML Schema:
> 
> The following URI always points to the latest schema (including errata) 
> for the MTOM Policy Assertion 1.0 namespace. The resource at this 
> location may change as new errata are incorporated.
> 
> http://www.w3.org/@@@/soap12-mtom-policy.xsd
> 
> 
>     This dated version of the XML Schema:
> 
> The following URI points to the schema for the MTOM Policy Assertion 1.0 
> namespace corresponding to the @@@(dated) specifications.
> 
> http://www.w3.org/@@@/soap12-mtom-policy.xsd
> 
> 
>     Stability of this namespace URI:
> 
> It is the intent of the W3C XML Protocols Working Group that the MTOM 
> Policy Assertion 1.0 XML namespace URI will not change arbitrarily with 
> each subsequent revision of the corresponding XML Schema documents as 
> the specifications transition through Candidate Recommendation, Proposed 
> Recommendation and Recommendation status. However, should the 
> specifications revert to Working Draft status, and a subsequent 
> revision, published as a WD, CR or PR draft, results in non-backwardly 
> compatible changes from a previously published WD, CR or PR draft of the 
> specification, the namespace URI will be changed accordingly.
> 
> Under this policy, the following are examples of backwards compatible 
> changes that would not result in assignment of a new XML 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 vast majority of instances would
>       remain valid.
> 
>     *
> 
>       Modifications to the cardinality of elements (i.e. modifications
>       to minOccurs or maxOccurs attribute value of an element
>       declaration) 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.
> 
> ------------------------------------------------------------------------
> 
> Comments on this document may be sent to the public xmlp-comments@w3.org 
> <mailto:xmlp-comments@w3.org> mailing list (public archive 
> <http://lists.w3.org/Archives/Public/xmlp-comments//>).
> 
> =
Received on Wednesday, 4 April 2007 17:06:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:24 GMT