- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 26 Jul 2006 18:38:13 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv21166
Modified Files:
ws-policy-framework.xml ws-policy-framework.html
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Incorporated the XML namespace URI versioning policy adopted by the WG.
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- ws-policy-framework.xml 22 Jul 2006 01:15:08 -0000 1.12
+++ ws-policy-framework.xml 26 Jul 2006 18:38:04 -0000 1.13
@@ -279,6 +279,34 @@
ref="XMLSchemaPart1"/>, <bibref
ref="XMLSchemaPart2"/>] document can be obtained by
dereferencing the XML namespace URI.</p>
+
+ <p>It is the intent of the W3C Web Services Policy Working Group that
+ the &framework.title; and &attachment.title; XML namespace URI will not change
+ arbitrarily with each subsequent revision of the corresponding
+ XML Schema documents but rather change only when 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.</p>
+ <p>Under this policy, the following are examples of backwards compatible
+ changes that would not result in assignment of a new XML namespace URI:</p>
+
+ <ulist>
+ <item>
+ <p>Addition of new global element, attribute, complexType
+ and simpleType definitions.</p></item>
+ <item>
+ <p>Addition of new elements or attributes in locations
+ covered by a previously specified wildcard.</p></item>
+ <item>
+ <p>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.</p></item>
+ <item>
+ <p>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.</p></item>
+ </ulist>
</div2>
<div2 id="Terminology">
@@ -1444,6 +1472,14 @@
(note: PLH had already done but it didn't show up in the change log)
</td>
</tr>
+ <tr>
+ <td>20060726</td>
+ <td>ASV</td>
+ <td>Incorporated the
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
+ namespace URI versioning policy</loc> adopted by the WG.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- ws-policy-framework.html 22 Jul 2006 01:15:08 -0000 1.11
+++ ws-policy-framework.html 26 Jul 2006 18:38:10 -0000 1.12
@@ -270,6 +270,34 @@
<p>All information items defined by this specification
are identified by the XML namespace URI [<cite><a href="#XML-NS">XML Namespaces</a></cite>] <code>http://www.w3.org/@@@@/@@/policy</code>. A <a href="http://www.w3.org/@@@@/@@/policy">normative XML Schema</a> [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaPart2">XML Schema Datatypes</a></cite>] document can be obtained by
dereferencing the XML namespace URI.</p>
+
+ <p>It is the intent of the W3C Web Services Policy Working Group that
+ the Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment XML namespace URI will not change
+ arbitrarily with each subsequent revision of the corresponding
+ XML Schema documents but rather change only when 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.</p>
+ <p>Under this policy, the following are examples of backwards compatible
+ changes that would not result in assignment of a new XML namespace URI:</p>
+
+ <ul>
+ <li>
+ <p>Addition of new global element, attribute, complexType
+ and simpleType definitions.</p></li>
+ <li>
+ <p>Addition of new elements or attributes in locations
+ covered by a previously specified wildcard.</p></li>
+ <li>
+ <p>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.</p></li>
+ <li>
+ <p>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.</p></li>
+ </ul>
</div>
<div class="div2">
@@ -1427,6 +1455,14 @@
(note: PLH had already done but it didn't show up in the change log)
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060726</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Incorporated the
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
+ namespace URI versioning policy</a> adopted by the WG.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- ws-policy-attachment.xml 22 Jul 2006 01:10:04 -0000 1.13
+++ ws-policy-attachment.xml 26 Jul 2006 18:38:11 -0000 1.14
@@ -230,6 +230,35 @@
with the intent that other specifications requiring such an
Id could reference it (as is done here).
</p>
+
+ <p>It is the intent of the W3C Web Services Policy Working Group that
+ the &framework.title; and &attachment.title; XML namespace URI will not change
+ arbitrarily with each subsequent revision of the corresponding
+ XML Schema documents but rather change only when 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.</p>
+ <p>Under this policy, the following are examples of backwards compatible
+ changes that would not result in assignment of a new XML namespace URI:</p>
+
+ <ulist>
+ <item>
+ <p>Addition of new global element, attribute, complexType
+ and simpleType definitions.</p></item>
+ <item>
+ <p>Addition of new elements or attributes in locations
+ covered by a previously specified wildcard.</p></item>
+ <item>
+ <p>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.</p></item>
+ <item>
+ <p>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.</p></item>
+ </ulist>
+
</div2>
<div2 id='Glossary'>
<head>Terminology</head>
@@ -1833,6 +1862,14 @@
<loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action29">29</loc>
from the Austin F2F.</td>
</tr>
+ <tr>
+ <td>20060726</td>
+ <td>ASV</td>
+ <td>Incorporated the
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
+ namespace URI versioning policy</loc> adopted by the WG.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- ws-policy-attachment.html 22 Jul 2006 01:10:03 -0000 1.17
+++ ws-policy-attachment.html 26 Jul 2006 18:38:11 -0000 1.18
@@ -225,6 +225,35 @@
with the intent that other specifications requiring such an
Id could reference it (as is done here).
</p>
+
+ <p>It is the intent of the W3C Web Services Policy Working Group that
+ the Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment XML namespace URI will not change
+ arbitrarily with each subsequent revision of the corresponding
+ XML Schema documents but rather change only when 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.</p>
+ <p>Under this policy, the following are examples of backwards compatible
+ changes that would not result in assignment of a new XML namespace URI:</p>
+
+ <ul>
+ <li>
+ <p>Addition of new global element, attribute, complexType
+ and simpleType definitions.</p></li>
+ <li>
+ <p>Addition of new elements or attributes in locations
+ covered by a previously specified wildcard.</p></li>
+ <li>
+ <p>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.</p></li>
+ <li>
+ <p>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.</p></li>
+ </ul>
+
</div>
<div class="div2">
@@ -1816,6 +1845,14 @@
<a href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action29">29</a>
from the Austin F2F.</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060726</td>
+ <td rowspan="1" colspan="1">ASV</td>
+ <td rowspan="1" colspan="1">Incorporated the
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
+ namespace URI versioning policy</a> adopted by the WG.
+ </td>
+ </tr>
</tbody>
</table><br>
</div>
Received on Wednesday, 26 July 2006 18:38:21 UTC