RE: proposal for namespace versioning policy for mtom assertion
"David Orchard" <[email protected]> Wed, 4 Apr 2007 17:10:45 -0700
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C77716.E37C17D7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I suggest revisions to simplify the wording: =20 >>> =20 It is the intent of the W3C XML Protocols Working Group that the MTOM Policy Assertion 1.0 XML namespace URI will not change 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 contain any non-backwards compatible changes from a previously published WD, CR or PR draft of the specification, the namespace URI will be changed. =20 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 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. =20 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Christopher B Ferris Sent: Wednesday, April 04, 2007 8:26 AM To: [email protected] Subject: proposal for namespace versioning policy for mtom assertion =09 =09 Proposed namespace document for the mtom policy assertion namespace attached.=20 =09 =20 =09 Cheers,=20 =09 Christopher Ferris STSM, Software Group Standards Strategy email: [email protected] blog: http://www.ibm.com/developerworks/blogs/page/chrisferris phone: +1 508 377 9295 ------_=_NextPart_001_01C77716.E37C17D7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007><FONT = face=3DArial=20 color=3D#0000ff size=3D2>I suggest revisions to simplify the=20 wording:</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007><FONT = face=3DArial=20 color=3D#0000ff size=3D2>>>></FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007>It is the = intent of the=20 W3C XML Protocols Working Group that the MTOM Policy Assertion 1.0 XML = namespace=20 URI will not change with each subsequent revision of the = corresponding=20 XML Schema documents as the specifications transition through Candidate=20 Recommendation, Proposed Recommendation and Recommendation status. = However, should the specifications contain any non-backwards = compatible=20 changes from a previously published WD, CR or PR draft of the = specification, the=20 namespace URI will be changed.</SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN = class=3D671430500-05042007></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D671430500-05042007>Under this = policy, the=20 following are examples of backwards compatible changes that would not = result in=20 assignment of a new namespace URI:</DIV> <DIV dir=3Dltr align=3Dleft> <UL> <LI> <P>Addition of new global element, attribute, complexType and = simpleType=20 definitions.</P> <LI> <P>Addition of new elements or attributes in locations covered by a = previously=20 specified wildcard.</P> <LI> <P>Modifications to the pattern facet of a type definition for which = the=20 value-space of the previous definition remains valid or for which the=20 value-space of the vast majority of instances would remain valid.</P> <LI> <P>Modifications to the cardinality of elements (i.e. modifications to = minOccurs or maxOccurs attribute value of an element declaration) for = which=20 the value-space of possible instance documents conformant to the = previous=20 revision of the schema would still be valid with regards to the = revised=20 cardinality rule.</P></LI></UL><!-- <p>This namespace URI = (<code>http://www.w3.org/ns/oap12-mtom-policy</code>) is defined in a <a href=3D"http://www.w3.org/Consortium/Process/tr.html#RecsW3C">W3C Recommendation</a> and is stable.</p> --></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN = class=3D671430500-05042007></SPAN> </DIV><BR> <BLOCKQUOTE=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> [email protected]=20 [mailto:[email protected]] <B>On Behalf Of </B>Christopher B = Ferris<BR><B>Sent:</B> Wednesday, April 04, 2007 8:26 AM<BR><B>To:</B> = [email protected]<BR><B>Subject:</B> proposal for namespace = versioning=20 policy for mtom assertion<BR></FONT><BR></DIV> <DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Proposed namespace = document for=20 the mtom policy assertion namespace attached.</FONT> <BR><BR><FONT=20 face=3Dsans-serif size=3D2> </FONT> <BR><BR><FONT = face=3Dsans-serif=20 size=3D2>Cheers,</FONT> <BR><BR><FONT face=3Dsans-serif = size=3D2>Christopher=20 Ferris<BR>STSM, Software Group Standards Strategy<BR>email:=20 [email protected]<BR>blog:=20 http://www.ibm.com/developerworks/blogs/page/chrisferris<BR>phone: +1 = 508 377=20 9295</FONT></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C77716.E37C17D7--