2006/ws/policy ws-policy-framework.html,1.101,1.102 ws-policy-attachment.html,1.91,1.92

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv12113

Modified Files:
	ws-policy-framework.html ws-policy-attachment.html 
Log Message:
Editors' copies versions

Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -d -r1.101 -r1.102
--- ws-policy-framework.html	22 Feb 2007 21:39:02 -0000	1.101
+++ ws-policy-framework.html	22 Feb 2007 21:50:02 -0000	1.102
@@ -54,62 +54,20 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-CR.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"></head><body><div class="head">
 <h1><a name="title" id="title"></a>Web Services Policy 1.5 - Framework</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Candidate Recommendation 28 February 2007</h2><dl><dt>This version:</dt><dd>
-            <a href="http://www.w3.org/TR/2007/CR-ws-policy-20070228">http://www.w3.org/TR/2007/CR-ws-policy-20070228</a>
-        </dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-policy">http://www.w3.org/TR/ws-policy</a></dd><dt>Previous version:</dt><dd>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+            <a href="ws-policy-framework.html">ws-policy-framework.html</a>
+        </dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
             <a href="http://www.w3.org/TR/2006/WD-ws-policy-20061117">http://www.w3.org/TR/2006/WD-ws-policy-20061117</a>
-        </dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</dd></dl><p>This document is also available in these non-normative formats: <a href="ws-policy-framework.pdf">PDF</a>, <a href="ws-policy-framework.ps">PostScript</a>, <a href="ws-policy-framework.xml">XML</a>, and&nbsp;<a href="ws-policy-framework.txt">plain text</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;2007&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathemaics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
+        </dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark/a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
 <h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding 
 	    syntax to describe the policies of entities in a Web services-based system.</p><p>Web Services Policy Framework defines a base set of
 	  constructs that can be used and extended by other Web
 	  services specifications to describe a broad range of service
 	  requirements and capabilities.</p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the
-  time of its publication. Other documents may supersede this
-  document. A list of current W3C publications and the latest revision
-  of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
-  http://www.w3.org/TR/.</em></p><p>W3C publishes a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#maturity-levels">Candidate
-  Recommendation</a> to indicate that the document is believed to be
-  stable and to encourage implementation by the developer
-  community. The <a href="http://www.w3.org/2002/ws/policy/">Web
-  Services Policy Working Group</a> expects to request that the
-  Director advance this document to Proposed Recommendation once the
-  Working Group has demonstrated 4 or more interoperable
-  implementations with the exception of <a href="#ignorable-policy-assertions">ignorable policy
-  assertions</a>, which shall require 2 or more implementations. The
-  Working Group does not plan to request to advance to Proposed
-  Recommendation prior to 30 June 2007.</p><p>No features have been identified as <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#cfi">"features
-  at risk"</a> by the Web Services Policy Working Group</p><p>This Working Draft was produced by the members of the <a href="http://www.w3.org/2002/ws/policy/">Web Services Policy Working
-  Group</a>, which is part of the <a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
-  Activity</a>. The Working Group expects to advance this Working
-  Draft to Recommendation Status.</p><p>A list of <a href="#change-description">changes in this version
-  of the document</a> and a <a href="ws-policy-framework-diff20061117.html">diff-marked version
-  against the previous version of this document</a> are
-  available. Major changes in this version of the document encompass
-  the reorganization of the content in section <a href="#Compact_Policy_Expression"><b>4.3 Compact Policy Expression</b></a> and the documentation of the schema
-  outline and description of policy operators in section <a href="#Policy_Operators"><b>4.3.3 Policy Operators</b></a>.</p><p>The Working Group is tracking all comments via <a href="http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=WS-Policy&amp;component=Framework&amp;component=Framework%2BAttachment&amp;component=Framework%2BAttachment%2BGuidelines&amp;component=Framework%2BAttachment%2BPrimer">Bugzilla</a>
-  and highly prefers to receive comments via this system. If access to
-  Bugzilla is not feasible, you may send your comments to the mailing
-  list <a href="mailto:public-ws-policy-comments@w3.org">public-ws-policy-comments@w3.org</a>
-  mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-policy-comments/">public
-  archive</a>). Each Bugzilla entry and email message should contain
-  only one comment. All comments on this specification should be made
-  following the <a href="http://www.w3.org/2002/ws/policy/#issues">Description for
-  Issues</a> of the Working Group.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
-  February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/39293/status">public list of
-  any patent disclosures</a> made in connection with the
-  deliverables of the group; that page also includes instructions for
-  disclosing a patent. An individual who has actual knowledge of a
-  patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
-  Essential Claim(s)</a> must disclose the information in accordance
-  with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
-  section 6 of the W3C Patent Policy</a>.</p><p>Publication as a Candidate Recommendation does not imply
-  endorsement by the W3C Membership. This is a draft document and may
-  be updated, replaced or obsoleted by other documents at any time. It
-  is inappropriate to cite this document as other than work in
-  progress.</p></div><div class="toc">
+<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+        no official standing.</strong></p><p></p></div><div class="toc">
 <h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1. <a href="#tocRange">Introduction</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#Example">Example</a><br>
 2. <a href="#Notation_Terminlogy">Notations and Terminology</a><br>
@@ -337,7 +295,7 @@
 	    [<a name="ignorable_policy_assertion" id="ignorable_policy_assertion" title="ignorable policy assertion">Definition</a>: An 
 	    <b>ignorable policy assertion</b> is 
 	    an assertion that may be ignored for policy intersection (as defined in 
-	        <a href="http://www.w3.org/TR/ws-policy#Policy_Intersection">4.5 Policy Intersection</a>).] By default, an assertion is not 
+	        <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#Policy_Intersection">4.5 Policy Intersection</a>).] By default, an assertion is not 
 	    ignorable for policy intersection.	          
 	    </p><p>Assertions are typed by the authors
 	    that define them.  [<a name="policy_assertion_type" id="policy_assertion_type" title="policy assertion type">Definition</a>: A <b>policy assertion type</b> 
@@ -1140,21 +1098,21 @@
                             "application/xml" as described in <cite><a href="#RFC3023">IETF RFC 3023</a></cite>.</p></dd><dt class="label">Base URI:</dt><dd><p>As specified in <cite><a href="#RFC3023">IETF RFC 3023</a></cite>, section 6.
                             Also see section <a href="#IRI_Policy_Expressions"><b>4.6 Use of IRIs in Policy Expressions</b></a> 
                             in this document and 
-                            <a href="http://www.w3.org/TR/ws-policy-attach#IRI_Policy_Attachment">section 3.5  
+                            <a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8#IRI_Policy_Attachment">section 3.5  
                                 Use of IRIs in Policy Attachment</a> in  <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>.</p></dd><dt class="label">Macintosh File Type code:</dt><dd><p>TEXT</p></dd><dt class="label">Person and email address to contact for further information:</dt><dd><p>World Wide Web Consortium &lt;web-human@w3.org&gt;</p></dd><dt class="label">Intended usage:</dt><dd><p>COMMON</p></dd><dt class="label">Author/Change controller:</dt><dd><p>The Web Services Policy 1.5 specification set is a work product of the World Wide
                     Web Consortium's 
                     <a href="http://www.w3.org/2002/ws/desc/">Web Service Policy Working Group</a>.
                     The W3C has change control over these specifications.</p></dd></dl></dd></dl></div></div><div class="div1">
 <h2><a name="References" id="References"></a>B. References</h2><div class="div2">
 <h3><a name="Normative-References" id="Normative-References"></a>B.1 Normative References</h3><dl><dt class="label"><a name="WS-PolicyAttachment"></a>[Web Services Policy Attachment] </dt><dd>
-	        <cite><a href="http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228">Web Services Policy 1.5 - Attachment</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,  
+	        <cite><a href="ws-policy-attachment.html">Web Services Policy 1.5 - Attachment</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,  
 	        P. Yendluri, T. Boubez and Ü. Yalçinalp,
-	        Editors. World Wide Web Consortium, 28,
-	        February 2007.  This version of the
+	        Editors. World Wide Web Consortium, @@,
+	        @@@@ @@@@.  This version of the
 	        specification of the Web Services Policy 1.5 - Attachment specification is
-	        http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228. The <a href="http://www.w3.org/TR/ws-policy-attach">latest
+	        ws-policy-attachment.html. The <a href="http://www.w3.org/TR/ws-policy-attachment">latest
 	            version of Web Services Policy 1.5 - Attachment</a> is available at
-	        http://www.w3.org/TR/ws-policy-attach.
+	        http://www.w3.org/TR/ws-policy-attachment.
 	    </dd><dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
 	    <cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate
 	    Requirement Levels</a></cite>, S. Bradner, Author. Internet
@@ -1331,7 +1289,7 @@
       Dimitar Angelov (SAP AG), Abbie Barbir (Nortel Networks), Charlton Barreto (Adobe Systems Inc.), Sergey Beryozkin (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Toufic Boubez (Layer 7 Technologies), Symon Chang (BEA Systems, Inc.), Paul Cotton (Microsoft Corporation), Jeffrey Crump (Sonic Software), Glen Daniels (Sonic Software), Jacques Durand (Fujitsu Limited), Ruchith Fernando (WSO2), Christopher Ferris (IBM Corporation), William Henry (IONA Technologies, Inc.), Frederick Hirsch (Nokia), Maryann Hondo (IBM Corporation), Tom Jordahl (Adobe Systems Inc.), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Mark Little (JBoss Inc.), Ashok Malhotra (Oracle Corporation), Monica Martin (Sun Microsystems, Inc.), Arnaud Meyniel (Axway Software), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Axway Software), Anthony Nadalin (IBM Corporation), Bob Natale (MITRE Corporation), David Orchard (BEA Systems, Inc.), Fabian Ritzmann (Sun Microsystems, Inc.), Daniel Roth (Microsoft Corporaton), Tom Rutt (Fujitsu Limited), Sanka Samaranayake (WSO2), Felix Sasaki (W3C/Keio), Skip Snow (Citigroup), Yakov Sverdlov (CA Inc.), Mark Temple-Raston (Citigroup), Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
   </p><p>
     Previous members of the Working Group were:
-      Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.)
+      Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.).
   </p><p>
     The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-policy/">discussions
     on public-ws-policy@w3.org</a> are also gratefully

Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- ws-policy-attachment.html	22 Feb 2007 21:39:03 -0000	1.91
+++ ws-policy-attachment.html	22 Feb 2007 21:50:02 -0000	1.92
@@ -54,13 +54,13 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-CR.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"></head><body><div class="head">
 <h1><a name="title" id="title"></a>Web Services Policy 1.5 - Attachment</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Candidate Recommendation 28 February 2007</h2><dl><dt>This version:</dt><dd>
-<a href="http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228">http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228</a>
-</dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a></dd><dt>Previous version:</dt><dd>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<a href="ws-policy-attachment.html">ws-policy-attachment.html</a>
+</dd><dt>Latest version:</dt><dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
             <a href="http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117">http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117</a>
-        </dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</dd></dl><p>This document is also available in these non-normative formats: <a href="ws-policy-attachment.pdf">PDF</a>, <a href="ws-policy-attachment.ps">PostScript</a>, <a href="ws-policy-attachment.xml">XML</a>, and&nbsp;<a href="ws-policy-attachment.txt">plain text</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;2007&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Matematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
+        </dd><dt>Editors:</dt><dd>Asir S Vedamuthu, Microsoft Corporation</dd><dd>David Orchard, BEA Systems, Inc.</dd><dd>Frederick Hirsch, Nokia</dd><dd>Maryann Hondo, IBM Corporation</dd><dd>Prasad Yendluri, webMethods, Inc.</dd><dd>Toufic Boubez, Layer 7 Technologies</dd><dd>Ümit Yalçinalp, SAP AG.</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark/a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
 <h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
 	This specification, Web Services Policy 1.5 - Attachment, defines two
 	general-purpose mechanisms for associating policies, as
@@ -69,50 +69,8 @@
 	general-purpose mechanisms may be used to associate policies
 	with WSDL and UDDI descriptions.
       </p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the
-  time of its publication. Other documents may supersede this
-  document. A list of current W3C publications and the latest revision
-  of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
-  http://www.w3.org/TR/.</em></p><p>W3C publishes a <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#maturity-levels">Candidate
-Recommendation</a> to indicate that the document is believed to be
-stable and to encourage implementation by the developer community. The
-<a href="http://www.w3.org/2002/ws/policy/">Web Services Policy
-Working Group</a> expects to request that the Director advance this
-document to Proposed Recommendation once the Working Group has
-demonstrated 4 or more interoperable implementations with the
-exception of the following: <a href="#ws-policy-attachment-for-wsdl20">WSDL2.0 attachment</a>, <a href="#ExternalPolicyAttachment">external policy attachment</a> and <a href="#AttachingPoliciesUsingUDDI">UDDI attachment</a>, which shall
-require 2 or more implementations. The Working Group does not plan to
-request to advance to Proposed Recommendation prior to 30 June
-2007.</p><p>No features have been identified as <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#cfi">"features
-at risk"</a> by the Web Services Policy Working Group</p><p>This Working Draft was produced by the members of the <a href="http://www.w3.org/2002/ws/policy/">Web Services Policy Working
-Group</a>, which is part of the <a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
-Activity</a>. The Working Group expects to advance this Working Draft
-to Recommendation Status.</p><p>A list of <a href="#change-description">changes in this version of
-the document</a> and a <a href="ws-policy-attachment-diff20061117.html">diff-marked version
-against the previous version of this document</a> are available. Major
-changes in this version of the document encompass the clarification of
-the relationship between URI domain expression and WSDL 1.1 Element
-Identifiers in Section <a href="#uri-domain-expression"><b>3.4.1 URI Domain Expression</b></a>.</p><p>The Working Group is tracking all comments via <a href="http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=WS-Policy&amp;component=Attachment&amp;component=Framework%2BAttachment&amp;component=Framework%2BAttachment%2BGuidelines&amp;component=Framework%2BAttachment%2BPrimer">Bugzilla</a>
-and highly prefers to receive comments via this system. If access to
-Bugzilla is not feasible, you may send your comments to the mailing
-list <a href="mailto:public-ws-policy-comments@w3.org">public-ws-policy-comments@w3.org</a>
-mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-policy-comments/">public
-archive</a>). Each Bugzilla entry and email message should contain
-only one comment. All comments on this specification should be made
-following the <a href="http://www.w3.org/2002/ws/policy/#issues">Description for
-Issues</a> of the Working Group.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
-2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/39293/status">public list of
-any patent disclosures</a> made in connection with the deliverables of
-the group; that page also includes instructions for disclosing a
-patent. An individual who has actual knowledge of a patent which the
-individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
-Essential Claim(s)</a> must disclose the information in accordance
-with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">
-section 6 of the W3C Patent Policy</a>.</p><p>Publication as a Candidate Recommendation does not imply
-endorsement by the W3C Membership. This is a draft document and may be
-updated, replaced or obsoleted by other documents at any time. It is
-inappropriate to cite this document as other than work in
-progress.</p></div><div class="toc">
+<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+        no official standing.</strong></p><p></p></div><div class="toc">
 <h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1. <a href="#tocRange">Introduction</a><br>
 2. <a href="#NotationsTerminology">Notations and Terminology</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#NotationalConventions">Notational Conventions</a><br>
@@ -155,9 +113,9 @@
 &nbsp;&nbsp;&nbsp;&nbsp;6.4 <a href="#RegisteringPoliciesUDDIVersion3">Registering Policies in UDDI Version 3</a><br>
 7. <a href="#SecurityConsiderations">Security Considerations</a><br>
 8. <a href="#Conformance">Conformance</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#d3e4075">External Policy Attachment Conformance</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#d3e4087">WSDL 1.1 Attachment Conformance</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;8.3 <a href="#d3e4096">WSDL 2.0 Attachment Conformance</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;8.1 <a href="#d3e3991">External Policy Attachment Conformance</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;8.2 <a href="#d3e4003">WSDL 1.1 Attachment Conformance</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;8.3 <a href="#d3e4012">WSDL 2.0 Attachment Conformance</a><br>
 </p>
 <h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A. <a href="#References">References</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;A.1 <a href="#Normative-References">Normative References</a><br>
@@ -410,7 +368,7 @@
 (36) &lt;/wsp:Policy&gt;</pre></div></div><p>The document containing both of these policy expressions is
 	assumed to be located at
 	<code>http://www.example.com/policies</code>. &nbsp;Per Section
-	<a href="http://www.w3.org/TR/2007/CR-ws-policy-20070228/#Policy_Identification">3.2
+	<a href="ws-policy-framework.html/#Policy_Identification">3.2
 	Policy Identification</a> of Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>], the IRIs used for these <a title="" href="#policy_expression">policy expressions</a>
 	in the remainder of this document are
 	<code>http://www.example.com/policies#RmPolicy</code> and
@@ -514,7 +472,7 @@
 associating <a title="" href="#policy_expression">policy expressions</a> with XML-based constructs.</p><p>Alternatively, rather than using the global attribute, XML elements
   <span class="rfc2119">MAY</span> use the <code>wsp:Policy</code> or <code>wsp:PolicyReference</code> elements directly as
 children, in order to support <a title="element policy" href="#element_policy">element policy</a> (Per Section
-	<a href="http://www.w3.org/TR/2007/CR-ws-policy-20070228/#Policy_References">4.3.4
+	<a href="ws-policy-framework.html/#Policy_References">4.3.4
 	Policy References</a> of Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]), and the semantics for
 this are the same as for the use of the global attribute. For example,
 an alternative way of attaching the policies in the above example,
@@ -725,7 +683,7 @@
 <a title="merge" href="#merge">merged</a> into the <a title="effective policy" href="#effective_policy">effective policy</a> of every implementation
 of that abstract WSDL definition.</p><p>Policies that are attached to a deployed resource (e.g., services
 or ports) are only considered in the <a title="effective policy" href="#effective_policy">effective policy</a> of that deployed
-resource itself.</p><div class="figure" style="text-align: center"><a name="Figure1" id="Figure1"></a><br><img src="effective-policy-scope.jpg" alt="Effective Policy and Policy Scopes in WSDL"><p style="text-align:left"><i><span>Figure 4-1. </span>Effective Policy and Policy Scopes in WSDL</i></p><br></div><p>(This graphic is also available in SVG format <a href="http://www.w3.org/TR/2007/CR-ws-policy-attach-20070228/effective-policy-scope.svg">here</a>.)</p><p>When attaching policies at different levels of the WSDL hierarchy, care must be taken. 
+resource itself.</p><div class="figure" style="text-align: center"><a name="Figure1" id="Figure1"></a><br><img src="effective-policy-scope.jpg" alt="Effective Policy and Policy Scopes in WSDL"><p style="text-align:left"><i><span>Figure 4-1. </span>Effective Policy and Policy Scopes in WSDL</i></p><br></div><p>(This graphic is also available in SVG format <a href="ws-policy-attachment.html/effective-policy-scope.svg">here</a>.)</p><p>When attaching policies at different levels of the WSDL hierarchy, care must be taken. 
 A message exchange with an endpoint <span class="rfc2119">MAY</span> be described by the 
 <a title="effective policy" href="#effective_policy">effective policies</a> 
 in all four subject types simultaneously.</p><p>For example, in <a href="#Figure1">Figure 4-1</a>, for a particular input message to a deployed
@@ -1524,11 +1482,11 @@
     Security Considerations section of the Web Services Policy 1.5 - Framework document [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>].
   </p></div><div class="div1">
 <h2><a name="Conformance" id="Conformance"></a>8. Conformance</h2><div class="div2">
-<h3><a name="d3e4075" id="d3e4075"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/ns/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>] for that element as defined by this specification (<a href="http://www.w3.org/2007/02/ws-policy.xsd">http://www.w3.org/2007/02/ws-policy.xsd</a>) and additionally adheres to all the constraints contained in Section <a href="#ExternalPolicyAttachment"><b>3.4 External Policy Attachment</b></a> of this specification. Such a conformant element information item constitutes an external policy attachment. </p></div><div class="div2">
-<h3><a name="d3e4087" id="d3e4087"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
+<h3><a name="d3e3991" id="d3e3991"></a>8.1 External Policy Attachment Conformance</h3><p>An element information item whose namespace name is "http://www.w3.org/ns/ws-policy" and whose local part is PolicyAttachment conforms to this specification if it is valid according to the XML Schema [<cite><a href="#XMLSchemaPart1">XML Schema Structures</a></cite>] for that element as defined by this specification (<a href="http://www.w3.org/2007/02/ws-policy.xsd">http://www.w3.org/2007/02/ws-policy.xsd</a>) and additionally adheres to all the constraints contained in Section <a href="#ExternalPolicyAttachment"><b>3.4 External Policy Attachment</b></a> of this specification. Such a conformant element information item constitutes an external policy attachment. </p></div><div class="div2">
+<h3><a name="d3e4003" id="d3e4003"></a>8.2 WSDL 1.1 Attachment Conformance</h3><p>
  A WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] description conforms to this specification when it incorporates one or more element policies and additionally adheres to all the constraints contained in section <a href="#AttachingPolicyUsingWSDL1.1"><b>4. Attaching Policies Using WSDL 1.1</b></a>
 </p></div><div class="div2">
-<h3><a name="d3e4096" id="d3e4096"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
+<h3><a name="d3e4012" id="d3e4012"></a>8.3 WSDL 2.0 Attachment Conformance</h3><p>
  A WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] description conforms to this specification when it incorporates one or more element policies and additionally adheres to all the constraints contained in section <a href="#ws-policy-attachment-for-wsdl20"><b>5. WS-Policy Attachment for WSDL 2.0</b></a>
 </p></div></div></div><div class="back"><div class="div1">
 <h2><a name="References" id="References"></a>A. References</h2><div class="div2">
@@ -1586,14 +1544,14 @@
 	UDDI 3.0</a> specification is available at
 	http://uddi.org/pubs/uddi_v3.htm.
       </dd><dt class="label"><a name="WS-Policy"></a>[Web Services Policy Framework] </dt><dd>
-  <cite><a href="http://www.w3.org/TR/2007/CR-ws-policy-20070228">Web Services Policy 1.5 - Framework</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,  
+  <cite><a href="ws-policy-framework.html">Web Services Policy 1.5 - Framework</a></cite>, A. S. Vedamuthu, D. Orchard, F. Hirsch, M. Hondo,  
   P. Yendluri, T. Boubez and Ü. Yalçinalp,
-	Editors. World Wide Web Consortium, 28, February
-	2007.  This version of the specification of the
+	Editors. World Wide Web Consortium, @@, @@@@
+	@@@@.  This version of the specification of the
 	Web Services Policy 1.5 - Framework specification is
-	http://www.w3.org/TR/2007/CR-ws-policy-20070228. The <a href="http://www.w3.org/TR/ws-policy">latest version
+	ws-policy-framework.html. The <a href="http://www.w3.org/TR/ws-policy-framework">latest version
 	of Web Services Policy 1.5 - Framework</a> is available at
-	http://www.w3.org/TR/ws-policy.
+	http://www.w3.org/TR/ws-policy-framework.
       </dd><dt class="label"><a name="WS-Addressing"></a>[WS-Addressing Core] </dt><dd>
 <cite><a href="http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/">Web Services Addressing 1.0 - Core</a></cite>,
 	M. Gudgin, M. Hadley, and T. Rogers, Editors. World Wide Web
@@ -1839,7 +1797,7 @@
       Dimitar Angelov (SAP AG), Abbie Barbir (Nortel Networks), Charlton Barreto (Adobe Systems Inc.), Sergey Beryozkin (IONA Technologies, Inc.), Vladislav Bezrukov (SAP AG), Toufic Boubez (Layer 7 Technologies), Symon Chang (BEA Systems, Inc.), Paul Cotton (Microsoft Corporation), Jeffrey Crump (Sonic Software), Glen Daniels (Sonic Software), Jacques Durand (Fujitsu Limited), Ruchith Fernando (WSO2), Christopher Ferris (IBM Corporation), William Henry (IONA Technologies, Inc.), Frederick Hirsch (Nokia), Maryann Hondo (IBM Corporation), Tom Jordahl (Adobe Systems Inc.), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Mark Little (JBoss Inc.), Ashok Malhotra (Oracle Corporation), Monica Martin (Sun Microsystems, Inc.), Arnaud Meyniel (Axway Software), Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Axway Software), Anthony Nadalin (IBM Corporation), Bob Natale (MITRE Corporation), David Orchard (BEA Systems, Inc.), Fabian Ritzmann (Sun Microsystems, Inc.), Daniel Roth (Microsoft Corporaton), Tom Rutt (Fujitsu Limited), Sanka Samaranayake (WSO2), Felix Sasaki (W3C/Keio), Skip Snow (Citigroup), Yakov Sverdlov (CA Inc.), Mark Temple-Raston (Citigroup), Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
   </p><p>
     Previous members of the Working Group were:
-      Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.)
+      Jong Lee (BEA Systems, Inc.), Bijan Parsia (University of Manchester), Seumas Soltysik (IONA Technologies, Inc.).
   </p><p>
     The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-policy/">discussions
     on public-ws-policy@w3.org</a> are also gratefully

Received on Thursday, 22 February 2007 21:50:14 UTC