- From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 04 Jan 2007 18:56:50 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv28911
Modified Files:
ws-policy-primer.html
Log Message:
Implements Editors AI 110, to fix references to xml:id as per bug 4069 resolution.
Submitting for Maryann.
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- ws-policy-primer.html 13 Dec 2006 19:12:30 -0000 1.29
+++ ws-policy-primer.html 4 Jan 2007 18:56:44 -0000 1.30
@@ -347,8 +347,8 @@
and requirements consistently across all of their offerings without duplicating policy
expressions multiple times. How? It is simple - a policy expression can be named and
referenced for re-use.</p><p>A policy expression may be identified by an IRI and referenced for re-use as a standalone
- policy or within another policy expression. There are two mechanisms to identify a policy
- expression: the <code>wsu:Id</code> and <code>Name</code> attributes. A
+ policy or within another policy expression. There are three mechanisms to identify a policy
+ expression: the <code>wsu:Id</code> <code>xml:id</code> and <code>Name</code> attributes. A
<code>PolicyReference</code> element can be used to reference a policy expression
identified using either of these mechanisms.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-12. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
@@ -360,14 +360,21 @@
absolute IRI for referencing this policy expression is
<code>http://real.contoso.com/policy.xml#common. (</code>The absolute IRI is formed by
combining the document IRI, <code>#</code> and the value of the <code>wsu:Id</code>
- attribute.)</p><p>For re-use, a <code>PolicyReference</code> element can be used to reference a policy
+ attribute.)</p><p> In addition to the Example 2-12, Contoso could have used either the xml:id or wsu:Id.
+ An example of the use of xml:id similar to that of wsu:Id is shown in Example 2-13. </p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-13. </span>Common Policy Expression [xml:id]</i></p><div class="exampleInner"><pre><Policy xml:id=”common”>
+ <mtom:OptimizedMimeSerialization wsp:Optional="true"/>
+ <wsap:UsingAddressing />
+</Policy></pre></div></div><p> Conditions and constraints on the use of the |xml:id| attribute in conjunction with Canonical
+ XML 1.0 are specified in Appendix C of <cite><a href="#XMLID">XML ID</a></cite> and are further detailed in <cite><a href="#C14NNOTE">C14N 1.0 Note</a></cite>.
+ Significant care is suggested in the use of xml:id.
+ </p><p>For re-use, a <code>PolicyReference</code> element can be used to reference a policy
expression as a standalone policy or within another policy expression. The example below
- is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-13. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="#common"/></pre></div></div><p>For referencing a policy expression within the same XML document, Contoso uses the
+ is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-14. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="#common"/></pre></div></div><p>For referencing a policy expression within the same XML document, Contoso uses the
<code>wsu:Id</code> attribute for identifying a policy expression and an IRI to this ID
value for referencing this policy expression using a <code>PolicyReference</code> element.</p><p>The example below is a policy expression that re-uses the common policy expression within
another policy expression. This policy expression requires the use of addressing, one of
transport- or message-level security for protecting messages and allows the use of
- optimization.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-14. </span>Secure Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”secure”>
+ optimization.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-15. </span>Secure Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”secure”>
<All>
<PolicyReference URI="#common"/>
<ExactlyOne>
@@ -381,10 +388,10 @@
resides in. As such, referencing a policy expression using the <code>Name</code> attribute
relies on additional out of band information. In the example below, the <code>Name</code>
attribute identifies the policy expression. The IRI of this policy expression is
- <code>http://real.contoso.com/policy/common</code>.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-15. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy Name=”http://real.contoso.com/policy/common”>
+ <code>http://real.contoso.com/policy/common</code>.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-16. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy Name=”http://real.contoso.com/policy/common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
-</Policy></pre></div></div><p>The example below is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-16. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://real.contoso.com/policy/common"/></pre></div></div></div><div class="div2">
+</Policy></pre></div></div><p>The example below is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-17. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://real.contoso.com/policy/common"/></pre></div></div></div><div class="div2">
<h3><a name="attaching-policy-expressions-to-wsdl"></a>2.9 Attaching Policy Expressions to WSDL</h3><p>A majority of Contoso’s customers use WSDL for building their client applications.
Contoso leverages this usage by attaching policy expressions to the WSDL binding
descriptions.</p><p>In the example below, the <code>SecureBinding</code> WSDL binding description defines a
@@ -397,7 +404,7 @@
expression attached to the <code>SecureBinding</code> WSDL binding description applies to
any message exchange associated with any <code>port</code> that supports this binding
description. This includes all the message exchanges described by operations in the
- <code>RealTimeDataInterface</code>.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-17. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
+ <code>RealTimeDataInterface</code>.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-18. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
<PolicyReference URI="#secure" />
<wsdl:operation name="GetRealQuote">…</wsdl:operation>
…
@@ -407,7 +414,7 @@
<code>GetDelayedQuotes,</code>
<code>GetSymbol</code> and <code>GetSymbols</code>). Contoso does not require the use of
security for these services, but requires the use of addressing and allows the use of
- optimization.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-18. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
+ optimization.</p><div class="exampleOuter"><p style="text-align: left" class="exampleHead"><i><span>Example 2-19. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
<PolicyReference URI="#common" />
<wsdl:operation name="GetDelayedQuote">…</wsdl:operation>
…
@@ -697,7 +704,7 @@
Metadata Exchange) for such metadata retrieval. These protocols may require additional
out of band information.</p></li><li><p>Attempt to resolve the referenced IRI on the Web. This may resolve to a policy
element or a resource that contains a policy element.</p></li></ul><p>If the referenced policy expression is in the same XML document as the reference, then
- the policy expression should be identified using the <code>wsu:Id</code> (XML ID)
+ the policy expression should be identified using the <code>wsu:Id|xml:id</code> (XML ID)
attribute and referenced using an IRI reference to this XML ID value.</p><p>
WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] section 2.1 and WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] chapter 4
allow to import or include WSDL documents into another WSDL document with the
@@ -1108,7 +1115,19 @@
International Business Machines Corporation, Layer 7 Technologies, Microsoft Corporation,
Oblix Inc., OpenNetwork Technologies Inc., Ping Identity Corporation, Reactivity Inc., RSA
Security Inc., and VeriSign Inc., February 2005. Available at
- http://schemas.xmlsoap.org/ws/2005/02/trust. </dd></dl></div><div class="div1">
+ http://schemas.xmlsoap.org/ws/2005/02/trust. </dd><dt class="label"><a name="XMLID"></a>[XML ID] </dt><dd>
+ <cite><a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">xml:id Version 1.0</a></cite>,
+ J. Marsh, D. Veillard and N. Walsh, Editors. World Wide Web Consortium,
+ 9 September 2005. This version of
+ the xml:id Version 1.0 Recommendation is
+ http://www.w3.org/TR/2005/REC-xml-id-20050909/. The
+ <a href="http://www.w3.org/TR/xml-id/">latest
+ version of xml:id Version 1.0</a> is available at
+ http://www.w3.org/TR/xml-id/. </dd><dt class="label"><a name="C14NNOTE"></a>[C14N 1.0 Note] </dt><dd>
+ <cite><a href="http://www.w3.org/2006/04/c14n-note/c14n-note.html">Known Issues with Canonical XML 1.0 (C14N/1.0)</a></cite>,
+ J. Kahan and K. Lanz, Editors. World Wide Web
+ Consortium, 17 August 2006.
+ Available at http://www.w3.org/2006/04/c14n-note/c14n-note.html.> </dd></dl></div><div class="div1">
<h2><a name="acknowledgments"></a>D. Acknowledgements (Non-Normative)</h2><p>This document is the work of the <a href="http://www.w3.org/2002/ws/policy/">W3C Web Services Policy
Working Group</a>.</p><p>
Members of the Working Group are (at the time of writing, and by
@@ -1194,4 +1213,8 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3965">issue 3965</a>
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0016.html">as outlined.</a>
Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/94">94</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070104</td><td rowspan="1" colspan="1">MH</td><td rowspan="1" colspan="1">Implemented the resolution for
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4069">issue 4069</a>
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0081.html">as outlined.</a>
+ Editors' action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/110">110</a>.
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Received on Thursday, 4 January 2007 18:57:08 UTC