- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 09 Aug 2006 20:55:59 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv8412
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
removed "until Rec status is achieved" from wsdl 2.0 resolution
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- ws-policy-attachment.xml 9 Aug 2006 17:53:18 -0000 1.20
+++ ws-policy-attachment.xml 9 Aug 2006 20:55:57 -0000 1.21
@@ -94,7 +94,7 @@
ref="WSDL11" />] and UDDI [<bibref
ref="UDDIAPI20" />, <bibref ref="UDDIDataStructure20" />,
<bibref ref="UDDI30" />]. WSDL [<bibref ref="WSDL20" />] is
- deferred until it reaches RECOMMENDATION status. Specifically, this specification
+ deferred. Specifically, this specification
defines the following:
</p>
@@ -435,13 +435,13 @@
attached to <termref def='policy_scope'>policy scopes</termref> that
contain the <termref def='policy_subject'>policy subject</termref>.</termdef>
</p>
- <p>This combination can be achieved by a <emph>merge</emph>
- operation. This consists of serializing each policy as a
+ <p>This combination can be achieved by: <termdef id='merge' term='merge'>a <term>merge</term>
+ consists of serializing each policy as a
<termref def='policy_expression'>policy expression</termref>, replacing their
<el>wsp:Policy</el> element with a
<el>wsp:All</el> element, and placing each as
children of a wrapper <el>wsp:Policy</el>
- element. The resulting policy expression is considered to
+ element.</termdef> The resulting policy expression is considered to
represent the combined policy of all of the attachments to
that subject.</p>
<p>Such calculated policy expressions have no meaningful URI of their own. </p>
@@ -508,7 +508,9 @@
http://www.example.com/policies#RmPolicy
http://www.example.com/policies#X509EndpointPolicy" />
</eg>
- <p>have been processed and <emph>merged</emph>, it would result in an <termref def='element_policy'>element policy</termref> whose XML 1.0 representation is listed in <specref ref='Table4'/>:</p>
+ <p>have been processed and <termref def='merge'>merged</termref>,
+ it would result in an <termref def='element_policy'>element policy</termref>
+ whose XML 1.0 representation is listed in <specref ref='Table4'/>:</p>
<example id='Table4'>
<head>Example Merged Policy Expression.</head>
<eg xml:space="preserve">(01) <wsp:Policy
@@ -723,7 +725,7 @@
<p>For abstract WSDL definitions, the <termref def='element_policy'>element policy</termref> is considered an
intrinsic part of the definition and applies to all uses of that
definition. In particular, it <rfc2119>MUST</rfc2119> be
-<emph>merged</emph> into the <termref def='effective_policy'>effective policy</termref> of every implementation
+<termref def='merge'>merged</termref> into the <termref def='effective_policy'>effective policy</termref> 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 <termref def='effective_policy'>effective policy</termref> of that deployed
@@ -795,7 +797,7 @@
<p>The <termref def='effective_policy'>effective policy</termref> for a WSDL endpoint policy subject includes
the <termref def='element_policy'>element policy</termref> of the <el>wsdl11:port</el> element that defines
-the endpoint <emph>merged</emph> with the <termref def='element_policy'>element policy</termref> of the
+the endpoint <termref def='merge'>merged</termref> with the <termref def='element_policy'>element policy</termref> of the
referenced <el>wsdl11:binding</el> element and the <termref def='element_policy'>element policy</termref> of
the referenced <el>wsdl11:portType</el> element that defines the
interface of the endpoint.</p>
@@ -823,7 +825,7 @@
<p>The <termref def='effective_policy'>effective policy</termref> for a WSDL operation policy subject is
calculated in relation to a specific port, and includes the <termref def='element_policy'>element
policy</termref> of the <el>wsdl11:portType/wsdl11:operation</el> element that
-defines the operation <emph>merged</emph> with that of the
+defines the operation <termref def='merge'>merged</termref> with that of the
corresponding <el>wsdl11:binding/wsdl11:operation</el> element.</p>
</div3>
@@ -851,7 +853,7 @@
<p>The <termref def='effective_policy'>effective policy</termref> for a specific WSDL message (i.e., input,
output, or fault message) is calculated in relation to a specific
port, and includes the <termref def='element_policy'>element policy</termref> of the <el>wsdl11:message</el>
-element that defines the message's type <emph>merged</emph> with the
+element that defines the message's type <termref def='merge'>merged</termref> with the
<termref def='element_policy'>element policy</termref> of the <el>wsdl11:binding</el> and
<el>wsdl11:portType</el> message definitions that describe that
message. </p>
@@ -1053,7 +1055,7 @@
<p>For UDDI tModels that represent Web service types, the <termref def='element_policy'>element
policy</termref> is considered an intrinsic part of the tModel and applies to
all uses of that tModel. In particular, it <rfc2119>MUST</rfc2119> be
-<emph>merged</emph> into the <termref def='effective_policy'>effective policy</termref> of every bindingTemplate
+<termref def='merge'>merged</termref> into the <termref def='effective_policy'>effective policy</termref> of every bindingTemplate
that references that tModel.</p>
<p>Policies that apply to deployed Web services (bindingTemplates) are
@@ -1121,7 +1123,7 @@
<p>The <termref def='effective_policy'>effective policy</termref> for a UDDI endpoint includes the <termref def='element_policy'>element
policy</termref> of the <el>uddi:bindingTemplate</el> element that defines the
-endpoint <emph>merged</emph> with the <termref def='element_policy'>element policy</termref> of those
+endpoint <termref def='merge'>merged</termref> with the <termref def='element_policy'>element policy</termref> of those
<el>uddi:tModel</el> elements that are referenced in contained
<el>uddi:tModelInstanceInfo</el> elements.</p>
@@ -1893,7 +1895,9 @@
for issue
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3546">3546</loc>: wsdl 2.0 status mention.
</td>
- </tr>
+ </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.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- ws-policy-attachment.html 9 Aug 2006 17:53:18 -0000 1.24
+++ ws-policy-attachment.html 9 Aug 2006 20:55:57 -0000 1.25
@@ -95,7 +95,7 @@
service technologies, this specification describes the use of
these general-purpose mechanisms with WSDL [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] and UDDI [<cite><a href="#UDDIAPI20">UDDI API 2.0</a></cite>, <cite><a href="#UDDIDataStructure20">UDDI Data Structure 2.0</a></cite>,
<cite><a href="#UDDI30">UDDI 3.0</a></cite>]. WSDL [<cite><a href="#WSDL20">WSDL 2.0 Core Language</a></cite>] is
- deferred until it reaches RECOMMENDATION status. Specifically, this specification
+ deferred. Specifically, this specification
defines the following:
</p>
@@ -423,13 +423,13 @@
attached to <a title="policy scope" href="#policy_scope">policy scopes</a> that
contain the <a title="policy subject" href="#policy_subject">policy subject</a>.]
</p>
- <p>This combination can be achieved by a <em>merge</em>
- operation. This consists of serializing each policy as a
+ <p>This combination can be achieved by: [<a name="merge" title="merge">Definition</a>: a <b>merge</b>
+ consists of serializing each policy as a
<a title="policy expression" href="#policy_expression">policy expression</a>, replacing their
<code class="elt">wsp:Policy</code> element with a
<code class="elt">wsp:All</code> element, and placing each as
children of a wrapper <code class="elt">wsp:Policy</code>
- element. The resulting policy expression is considered to
+ element.] The resulting policy expression is considered to
represent the combined policy of all of the attachments to
that subject.</p>
<p>Such calculated policy expressions have no meaningful URI of their own. </p>
@@ -495,7 +495,9 @@
http://www.example.com/policies#RmPolicy
http://www.example.com/policies#X509EndpointPolicy" />
</pre></div>
- <p>have been processed and <em>merged</em>, it would result in an <a title="element policy" href="#element_policy">element policy</a> whose XML 1.0 representation is listed in <a href="#Table4">Example 3-1</a>:</p>
+ <p>have been processed and <a title="merge" href="#merge">merged</a>,
+ it would result in an <a title="element policy" href="#element_policy">element policy</a>
+ whose XML 1.0 representation is listed in <a href="#Table4">Example 3-1</a>:</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
@@ -713,7 +715,7 @@
<p>For abstract WSDL definitions, the <a title="element policy" href="#element_policy">element policy</a> is considered an
intrinsic part of the definition and applies to all uses of that
definition. In particular, it <span class="rfc2119">MUST</span> be
-<em>merged</em> into the <a title="effective policy" href="#effective_policy">effective policy</a> of every implementation
+<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
@@ -786,7 +788,7 @@
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a WSDL endpoint policy subject includes
the <a title="element policy" href="#element_policy">element policy</a> of the <code class="elt">wsdl11:port</code> element that defines
-the endpoint <em>merged</em> with the <a title="element policy" href="#element_policy">element policy</a> of the
+the endpoint <a title="merge" href="#merge">merged</a> with the <a title="element policy" href="#element_policy">element policy</a> of the
referenced <code class="elt">wsdl11:binding</code> element and the <a title="element policy" href="#element_policy">element policy</a> of
the referenced <code class="elt">wsdl11:portType</code> element that defines the
interface of the endpoint.</p>
@@ -815,7 +817,7 @@
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a WSDL operation policy subject is
calculated in relation to a specific port, and includes the <a title="element policy" href="#element_policy">element
policy</a> of the <code class="elt">wsdl11:portType/wsdl11:operation</code> element that
-defines the operation <em>merged</em> with that of the
+defines the operation <a title="merge" href="#merge">merged</a> with that of the
corresponding <code class="elt">wsdl11:binding/wsdl11:operation</code> element.</p>
</div>
@@ -844,7 +846,7 @@
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a specific WSDL message (i.e., input,
output, or fault message) is calculated in relation to a specific
port, and includes the <a title="element policy" href="#element_policy">element policy</a> of the <code class="elt">wsdl11:message</code>
-element that defines the message's type <em>merged</em> with the
+element that defines the message's type <a title="merge" href="#merge">merged</a> with the
<a title="element policy" href="#element_policy">element policy</a> of the <code class="elt">wsdl11:binding</code> and
<code class="elt">wsdl11:portType</code> message definitions that describe that
message. </p>
@@ -1044,7 +1046,7 @@
<p>For UDDI tModels that represent Web service types, the <a title="element policy" href="#element_policy">element
policy</a> is considered an intrinsic part of the tModel and applies to
all uses of that tModel. In particular, it <span class="rfc2119">MUST</span> be
-<em>merged</em> into the <a title="effective policy" href="#effective_policy">effective policy</a> of every bindingTemplate
+<a title="merge" href="#merge">merged</a> into the <a title="effective policy" href="#effective_policy">effective policy</a> of every bindingTemplate
that references that tModel.</p>
<p>Policies that apply to deployed Web services (bindingTemplates) are
@@ -1113,7 +1115,7 @@
<p>The <a title="effective policy" href="#effective_policy">effective policy</a> for a UDDI endpoint includes the <a title="element policy" href="#element_policy">element
policy</a> of the <code class="elt">uddi:bindingTemplate</code> element that defines the
-endpoint <em>merged</em> with the <a title="element policy" href="#element_policy">element policy</a> of those
+endpoint <a title="merge" href="#merge">merged</a> with the <a title="element policy" href="#element_policy">element policy</a> of those
<code class="elt">uddi:tModel</code> elements that are referenced in contained
<code class="elt">uddi:tModelInstanceInfo</code> elements.</p>
@@ -1878,7 +1880,9 @@
for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3546">3546</a>: wsdl 2.0 status mention.
</td>
- </tr>
+ </tr>
+
+
</tbody>
</table><br>
</div>
Received on Wednesday, 9 August 2006 20:56:08 UTC