- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 07 Feb 2007 22:34:15 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv7968
Modified Files:
ws-policy-framework.xml ws-policy-framework.html
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Implemented the resolution for issue 4306. Editors' action 158.
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -d -r1.118 -r1.119
--- ws-policy-framework.xml 7 Feb 2007 21:19:41 -0000 1.118
+++ ws-policy-framework.xml 7 Feb 2007 22:34:12 -0000 1.119
@@ -290,12 +290,16 @@
ref="XMLSchemaPart2"/>] document can be obtained by
dereferencing the namespace document at the WS-Policy 1.5 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>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 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.</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>
@@ -2663,6 +2667,14 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4307">4307</loc>.
Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/156">156</loc>.
</td>
+ </tr>
+ <tr>
+ <td>20070207</td>
+ <td>ASV</td>
+ <td>Implemented the resolution for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4306">4306</loc>.
+ Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/158">158</loc>.
+ </td>
</tr>
</tbody>
</table>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -d -r1.96 -r1.97
--- ws-policy-framework.html 25 Jan 2007 19:46:58 -0000 1.96
+++ ws-policy-framework.html 7 Feb 2007 22:34:13 -0000 1.97
@@ -156,12 +156,15 @@
listed in <a href="#nsprefix">Table 2-1</a>. Note that the choice of any namespace
prefix is arbitrary and not semantically significant (see [<cite><a href="#XML-NS">XML Namespaces</a></cite>]).</p><a name="nsprefix"></a><table summary="Namespace prefixes usage in this specification" border="1" cellspacing="0" cellpadding="5"><caption>Table 2-1. Prefixes and Namespaces used in this specification</caption><thead><tr><th rowspan="1" colspan="1">Prefix</th><th rowspan="1" colspan="1">Namespace</th><th rowspan="1" colspan="1">Specification</th></tr></thead><tbody><tr><td rowspan="1" colspan="1"><code>sp</code></td><td rowspan="1" colspan="1"><code>http://schemas.xmlsoap.org/ws/2005/07/securitypolicy</code></td><td rowspan="1" colspan="1">[<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>]</td></tr><tr><td rowspan="1" colspan="1"><code>wsp</code></td><td rowspan="1" colspan="1"><code>http://www.w3.org/ns/ws-policy</code></td><td rowspan="1" colspan="1">This specification</td></tr><tr><td rowspan="1" colspan="1"><code>wsu</code></td><td rowspan="1" colspan="1"<code>http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd</code></td><td rowspan="1" colspan="1">[<cite><a href="#WS-Security">WS-Security 2004</a></cite>]</td></tr><tr><td rowspan="1" colspan="1"><code>xs</code></td><td rowspan="1" colspan="1"><code>http://www.w3.org/2001/XMLSchema</code></td><td rowspan="1" colspan="1">[<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>]</td></tr></tbody></table><br><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/ns/ws-policy</code>. A <a href="http://www.w3.org/ns/ws-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 namespace document at the WS-Policy 1.5 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
+ dereferencing the namespace document at the WS-Policy 1.5 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 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.</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
@@ -659,7 +662,7 @@
of the <strong>[parent element]</strong>.</p></dd></dl><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code class="elt">wsp:All</code> and
<code class="elt">wsp:ExactlyOne</code> elements do not allow attribute extensibility
because such attributes cannot be preserved through normalization.</p></div><p>The following rules are used to transform a compact policy expression into a normal form policy expression:</p><dl><dt class="label">Equivalence</dt><dd><p>Use of <code class="elt">wsp:Policy</code> as an operator within a policy expression is
- equivalent to <code class="elt">wsp:All</code> .</p></dd><dd><p>
+ equivalent to <code class="elt">wsp:All</code> .</p><p>
A collection of assertions in an <code class="elt">wsp:All</code> operator is equivalent
to a <a title="policy alternative" href="#policy_alternative">policy alternative</a>. For instance,
</p><div class="exampleInner"><pre>(01) <wsp:All>
@@ -1032,7 +1035,10 @@
</p></div></div><div class="back"><div class="div1">
<h2><a name="media-type"></a>A. The application/wspolicy+xml Media Type</h2><p>This appendix defines the "application/wspolicy+xml"
media type which can be used to describe Web Services Policy documents
- serialized as XML. Either <code class="attr">wsp:Policy</code> or <code class="attr">wsp:PolicyAttachment</code> could be the root element of such a document.</p><div class="div2">
+ serialized as XML. Either <code class="attr">wsp:Policy</code> or <code class="attr">wsp:PolicyAttachment</code> could be the root element of such a document.
+ The "application/wspolicy+xml" media type is being submitted to the
+ IESG for review, approval, and registration with IANA.
+ </p><div class="div2">
<h3><a name="ietf-reg"></a>A.1 Registration</h3><dl><dt class="label">MIME media type name:</dt><dd><p>application</p></dd><dt class="label">MIME subtype name:</dt><dd><p>wspolicy+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>none</p></dd><dt class="label">Optional parameters:</dt><dd><dl><dt class="label">charset</dt><dd><p>This parameter has identical semantics to the charset parameter
of the "application/xml" media type as specified in
<cite><a href="#RFC3023">IETF RFC 3023</a></cite>.</p></dd></dl></dd><dt class="label">Encoding considerations:</dt><dd><p>Identical to those of "application/xml"
@@ -1491,4 +1497,10 @@
to section <a href="#Extensibility"><b>2.2 Extensibility</b></a>: Umit's amendment - "such as in Section
4.3.4 Policy References" and other changes.
</td></tr><tr><td rowspan="1" colspan="1">20070124</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated Section <a href="#change-description"><b>D. Changes in this Version of the Document</b></a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070207</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Implemented the resolution for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4307">4307</a>.
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/156">156</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070207</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the resolution for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4306">4306</a>.
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/158">158</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- ws-policy-attachment.xml 25 Jan 2007 19:46:58 -0000 1.87
+++ ws-policy-attachment.xml 7 Feb 2007 22:34:13 -0000 1.88
@@ -302,12 +302,17 @@
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>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 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.</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>
@@ -3260,7 +3265,15 @@
<td>ASV</td>
<td>Updated Section <specref ref="change-description"/>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070207</td>
+ <td>ASV</td>
+ <td>Implemented the resolution for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4306">4306</loc>.
+ Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/158">158</loc>.
+ </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.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- ws-policy-attachment.html 25 Jan 2007 19:46:58 -0000 1.86
+++ ws-policy-attachment.html 7 Feb 2007 22:34:13 -0000 1.87
@@ -160,12 +160,15 @@
<code class="attr">wsu:Id</code> attribute was added to the utility schema
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
+ </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 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.</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
@@ -1852,6 +1855,7 @@
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/116">116</a> and
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/124">124</a>
Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211">4211</a></td></tr><tr><td rowspan="1" colspan="1">20070117</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Applied the resolution for issues 4045 and 4127 using <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c2">first</a>
+
and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4045#c3">second</a> parts as outlined in working group
<a href="http://www.w3.org/2007/01/17-ws-policy-irc#T22-50-02">resolution</a>. This closes editors actions
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/139">139</a> and
@@ -1875,4 +1879,7 @@
and all occurrences of <code class="elt">Policy</code> and <code class="elt">PolicyReference</code> .
</td></tr><tr><td rowspan="1" colspan="1">20070123</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Fixed a typo in <a href="#Informative-References"><b>A.2 Other References</b></a>: "[IETF RFC 3023]IETF "RFC 2246:".
</td></tr><tr><td rowspan="1" colspan="1">20070124</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated Section <a href="#change-description"><b>D. Changes in this Version of the Document</b></a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070207</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Implemented the resolution for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4306">4306</a>.
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/158">158</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 7 February 2007 22:34:21 UTC