- From: Toufic Boubez via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 25 Sep 2006 03:14:59 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv9514
Modified Files:
ws-policy-attachment.html ws-policy-attachment.xml
Log Message:
Implemented
http://www.w3.org/2006/09/14-ws-policy-minutes.html#item12
for issue
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3709
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- ws-policy-attachment.xml 23 Sep 2006 05:23:23 -0000 1.39
+++ ws-policy-attachment.xml 25 Sep 2006 03:14:56 -0000 1.40
@@ -1097,7 +1097,7 @@
system and is defined in Appendix <specref
ref='RemotePolicyReferenceCategorySystem'/>.</p>
-<p>UDDI registries <rfc2119>MUST</rfc2119> use the <att>tModelKey</att>
+ <p>UDDI registries <rfc2119>MUST</rfc2119> use the (UDDI V2 [<bibref ref="UDDIDataStructure20" />]) <att>tModelKey</att>
<code>uuid:a27078e4-fd38-320a-806f-6749e84f8005</code> to uniquely identify this
tModel so that UDDI registry users can expect the same behavior across
different UDDI registries.</p>
@@ -1321,8 +1321,9 @@
</categoryBag>
</bindingTemplate></eg>
-<p>Third, inquiries for reusable <termref def='policy_expression'>policy expression</termref> tModels and UDDI
-entities that are associated with remote <termref def='policy_expression'>policy expression</termref> is enhanced
+<p>Third, inquiries for reusable <termref def='policy_expression'>policy expression</termref> tModels
+ described in Section <specref ref='RegisteringReusablePolicyExpressions'/> and UDDI
+tModel entities that are associated with remote <termref def='policy_expression'>policy expression</termref> is enhanced
by the wildcard mechanism for keyValues in keyedReferences. For
example, searching for all <termref def='policy_expression'>policy expression</termref> tModels whose IRI starts
with <code>http://www.example.com/</code>, the following <code>find_tModel</code> API call can
@@ -1729,7 +1730,7 @@
specification for further details.</td>
</tr>
<tr><th>UDDI Key (V3):</th>
-<td><code>uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03</code></td>
+<td><code>uddi:schemas.xmlsoap.org:localpolicyreference:2003_03</code></td>
</tr>
<tr><th>UDDI V1,V2 format key:</th>
<td><code>uuid:a27f7d45-ec90-31f7-a655-efe91433527c</code></td>
@@ -1754,9 +1755,13 @@
keyValue="categorization"
tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />
<keyedReference
- keyName="uddi-org:entityKeyValues"
- keyValue="tModelKey"
- tModelKey="uuid:916b87bf-0756-3919-8eae-97dfa325e5a4" />
+ keyName="uddi-org:types:checked"
+ keyValue="checked"
+ tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />
+ <keyedReference
+ keyName="uddi-org:entityKeyValues"
+ keyValue="tModelKey"
+ tModelKey="uuid:916b87bf-0756-3919-8eae-97dfa325e5a4" />
</categoryBag>
</tModel> </eg>
</div3>
@@ -1945,7 +1950,16 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3557">3557</loc>: clarify the use of domain expressions.
</td>
</tr>
- </tbody>
+ <tr>
+ <td>20060924</td>
+ <td>TIB</td>
+ <td>Implemented the
+ <loc href="http://www.w3.org/2006/09/14-ws-policy-minutes.html#item12">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3709">3709</loc>: Editorial corrections from UDDI team.
+ </td>
+ </tr>
+ </tbody>
</table>
</inform-div1>
</back>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- ws-policy-attachment.html 12 Sep 2006 22:14:03 -0000 1.42
+++ ws-policy-attachment.html 25 Sep 2006 03:14:56 -0000 1.43
@@ -1,4 +1,4 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Attachment</title><style type="text/css">
code { font-family: monospace; }
@@ -47,7 +47,7 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
-</style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link href="#contents" rel="contents"></head><body>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="contents" href="#contents"></head><body>
<div class="head">
<h1>Web Services Policy 1.5 - Attachment</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
@@ -75,7 +75,7 @@
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange">Introduction</a><br>2. <a href="#NotationsTerminology">Notations and Terminology</a><br> 2.1 <a href="#NotationalConventions">Notational Conventions</a><br> 2.2 <a href="#XMLNamespaces">XML Namespaces</a><br> 2.3 <a href="#Glossary">Terminology</a><br> 2.4 <a href="#Example">Example</a><br>3. <a href="#rPolicyAttachment">Policy Attachment</a><br> 3.1 <a href="#rEffectivePolicy">Effective Policy</a><br> 3.2 <a href="#PolicyAttachmentMechanisms">Policy Attachment Mechanisms</a><br> 3.3 <a href="#XMLElementAttachement">XML Element Attachment</a><br> 3.4 <a href="#ExternalPolicyAttachment">External Policy Attachment</a><br>4. <a href="#AttachingPolicyUsingWSDL1.1">Attaching Policies Using WSDL 1.1</a><br> 4.1 <a href="#CaculatingEffectivyPolicywithWSDL1.1">Calculating Effective Policy in WSDL 1.1</a><br> 4.1.1 <a href="#ServicePolicySubject">Service Policy Subject</a><br> 4.1.2 <a href="#EndpointPolicySubject">Endpoint Policy Subject</a><br> 4.1.3 <a href="#OperationPolicySubject">Operation Policy Subject</a><br> 4.1.4 <a href="#MessagePolicySubject">Message Policy Subject</a><br> 4.1.5 <a href="#Example2">Example</a><br>5. <a href="#AttachingPoliciesUsingUDDI">Attaching Policies Using UDDI</a><br> 5.1 <a href="#CalculatingEffectivePolicyElementPolicyUDDI">Calculating Effective Policy and Element Policy in UDDI</a><br> 5.1.1 <a href="#ServiceProviderPolicySubjectUDDI">Service Provider Policy Subject</a><br> nbsp; 5.1.2 <a href="#ServicePolicySubjectUDDI">Service Policy Subject</a><br> 5.1.3 <a href="#EndpointPolicySubjectUDDI">Endpoint Policy Subject</a><br> 5.2 <a href="#ReferencingRemotePolicyExpressions">Referencing Remote Policy Expressions</a><br> 5.3 <a href="#RegisteringReusablePolicyExpressions">Registering Reusable Policy Expressions</a><br> 5.4 <a href="#RegisteringPoliciesUDDIVersion3">Registering Policies in UDDI Version 3</a><br>6. <a href="#SecurityConsiderations">Security Considerations</a><br>7. <a href="#Conformance">Conformance</a><br></p>
-<h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#References">References</a><br> A.1 <a href="#Normative-References">Normative References</a><br> A.2 <a href="#Informative-References">Other References</a><br>B. <a href="#AppendixA">UDDI tModel Definitions</a><br> B.1 <a href="#RemotePolicyReferenceCategorySystem">Remote Policy Reference Category System</a><br> B.1.1 <a href="#DesigGoals1">Design Goals</a><br> B.1.2 <a href="#tModelDefinition1">tModel Definition</a><br> B.1.3 <a href="#ModelStructure1">tModel Structure</a><br> B.2 <a href="#WS-PolicyTypesCategorySystem">Web Services Policy Types Category System</a><br> B.2.1 <a href="#DesignGoals2">Design Goals</a><br> &bsp; B.2.2 <a href="#tModelDefinition2">tModel Definition</a><br> B.2.3 <a href="#ModelStructure2">tModel Structure</a><br> B.3 <a href="#LocalPolicyReferenceCategorySystem">Local Policy Reference Category System</a><br> B.3.1 <a href="#DesignGoals3">Design Goals</a><br> B.3.2 <a href="#tModelDefinition3">tModel Definition</a><br> B.3.3 <a href="#ModelStructure3">tModel Structure</a><br>C. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>D. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>E. <a href="#change-log">Web Services Policy 1.5 - Attachment Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
+<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#References">References</a><br> A.1 <a href="#Normative-References">Normative References</a><br> A.2 <a href="#Informative-References">Other References</a><br>B. <a href="#AppendixA">UDDI tModel Definitions</a><br> B.1 <a href="#RemotePolicyReferenceCategorySystem">Remote Policy Reference Category System</a><br> B.1.1 <a href="#DesigGoals1">Design Goals</a><br> B.1.2 <a href="#tModelDefinition1">tModel Definition</a><br> B.1.3 <a href="#ModelStructure1">tModel Structure</a><br> B.2 <a href="#WS-PolicyTypesCategorySystem">Web Services Policy Types Category System</a><br> B.2.1 <a href="#DesignGoals2">Design Goals</a><br> &bsp; B.2.2 <a href="#tModelDefinition2">tModel Definition</a><br> B.2.3 <a href="#ModelStructure2">tModel Structure</a><br> B.3 <a href="#LocalPolicyReferenceCategorySystem">Local Policy Reference Category System</a><br> B.3.1 <a href="#DesignGoals3">Design Goals</a><br> B.3.2 <a href="#tModelDefinition3">tModel Definition</a><br> B.3.3 <a href="#ModelStructure3">tModel Structure</a><br>C. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>D. <a href="#change-description">Changes in this Version of the Document</a> (Non-Normative)<br>E. <a href="#change-log">Web Services Policy 1.5 - Attachment Change Log</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
@@ -272,47 +272,112 @@
<p>We introduce the following terms that are used throughout this document:</p>
-<dl><dt class="label"><a href="#effective_policy">effective policy</a></dt><dd><p>the
-<b>effective policy</b>, for a given <a title="policy subject" href="#policy_subject">policy subject</a>, is the
+<dl>
+
+ <dt class="label">
+ <a href="#effective_policy">effective policy</a>
+ </dt>
+ <dd>
+ <p>the
+<b>effective policy</b>, for a given <a title="" href="#policy_subject">policy subject</a>, is the
combination of relevant policies. The relevant policies are those
-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></dd><dt class="label"><a href="#element_policy">element policy</a></dt><dd><p>The
- <b>element policy</b> is the <a title="policy" href="#policy">policy</a> attached to the <a title="policy subject" href="#policy_subject">policy subjects</a> associated with
- the element information item that contains it.</p></dd><dt class="label"><a href="#merge">merge</a></dt><dd><p>a <b>merge</b>
+attached to <a title="" href="#policy_scope">policy scopes</a> that
+contain the <a title="" href="#policy_subject">policy subject</a>.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="#element_policy">element policy</a>
+ </dt>
+ <dd>
+ <p>The
+ <b>element policy</b> is the <a title="" href="#policy">policy</a> attached to the <a title="" href="#policy_subject">policy subjects</a> associated with
+ the element information item that contains it.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="#merge">merge</a>
+ </dt>
+ <dd>
+ <p>a <b>merge</b>
consists of serializing each policy as a
- <a title="policy expression" href="#policy_expression">policy expression</a>, replacing their
+ <a title="" 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.</p></dd><dt class="label"><a href="ws-policy-framework.html#policy">policy</a></dt><dd><p id="policy">A <b>policy</b> is a
-collection of <a title="policy alternative" href="#policy_alternative">policy
-alternatives</a>. </p></dd><dt class="label"><a href="ws-policy-framework.html#policy_alternative">policy alternative</a></dt><dd><p id="policy_alternative">A
-<b>policy alternative</b> is a collection of <a title="policy assertion" href="#policy_assertion">policy assertions</a>.</p></dd><dt class="label"><a href="ws-policy-framework.html#policy_assertion">policy assertion</a></dt><dd><p id="policy_assertion">A
-<b>policy assertion</b> represents an individual requirement,
-capability, or other property of a behavior.</p></dd><dt class="label"><a href="ws-policy-framework.html#policy_attachment">policy attachment</a></dt><dd><p id="policy_attachment">A
-<b>policy attachment</b> is a mechanism for associating <a title="policy" href="#policy">policy</a> with one or more <a title="policy scope" href="#policy_scope">policy scopes</a>.</p></dd><dt class="label"><a href="ws-policy-framework.html#policy_expression">policy expression</a></dt><dd><p id="policy_expression">A
-<b>policy expression</b> is an XML Infoset representation of a
-<a title="policy" href="#policy">policy</a>, either in a normal form or in
-an equivalent compact form. </p></dd><dt class="label"><a href="ws-policy-framework.html#policy_scope">policy scope</a></dt><dd><p id="policy_scope">A <b>policy
-scope</b> is a collection of <a title="policy subject" href="#policy_subject">policy
-subjects</a> to which a policy may apply.</p></dd><dt class="label"><a href="ws-policy-framework.html#policy_subject">policy subject</a></dt><dd><p id="policy_subject">A <b>policy
-subject</b> is an entity (e.g., an endpoint, message, resource,
-interaction) with which a <a title="policy" href="#policy">policy</a> can
-be associated. </p></dd></dl>
-
+ element.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy">policy</a>
+ </dt>
+ <dd>
+ <p id="policy">A <b>policy</b> is a collection of
+ <a title="" href="#policy_alternative">policy alternatives</a>, </p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_alternative">policy alternative</a>
+ </dt>
+ <dd>
+ <p id="policy_alternative">a <b>policy alternative</b>
+ is a collection of <a title="" href="#policy_assertion">policy assertions</a>.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_assertion">policy assertion</a>
+ </dt>
+ <dd>
+ <p id="policy_assertion">A <b>policy assertion</b>
+ represents an individual requirement, capability, or other property of a behavior.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_attachment">policy attachment</a>
+ </dt>
+ <dd>
+ <p id="policy_attachment">A
+ <b>policy attachment</b> is a mechanism for associating
+ <a title="" href="#policy">policy</a> with one or more <a title="" href="#policy_scope">policy scopes</a>.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_expression">policy expression</a>
+ </dt>
+ <dd>
+ <p id="policy_expression">A <b>policy expression</b>
+ is an XML Infoset representation of a <a title="" href="#policy">policy</a>,
+ either in a normal form or in an equivalent compact form.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_scope">policy scope</a>
+ </dt>
+ <dd>
+ <p id="policy_scope">A <b>policy scope</b> is a collection of
+ <a title="" href="#policy_subject">policy subjects</a> to which a policy may apply.</p>
+ </dd>
+
+
+ <dt class="label">
+ <a href="ws-policy-framework.html#policy_subject">policy subject</a>
+ </dt>
+ <dd>
+ <p id="policy_subject">A <b>policy subject</b> is an entity
+ (e.g., an endpoint, message, resource, interaction) with which a
+ <a title="" href="#policy">policy</a> can be associated. </p>
+ </dd>
+
+</dl>
-
-
-
-
-
-
-
-
-
-
-
</div>
<div class="div2">
@@ -320,15 +385,15 @@
<p>This specification defines several mechanisms for
associating policies (Web Services Policy 1.5 - Framework, [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]) with various XML Web service entities. For
- brevity, we define two sample <a title="policy expression" href="#policy_expression">policy expressions</a> that the
+ brevity, we define two sample <a title="" href="#policy_expression">policy expressions</a> that the
remainder of this document references. </p>
- <p>The example in <a href="#Table2">Example 2-1</a> indicates a <a title="policy" href="#policy">policy</a> for reliable messaging [<cite><a href="#WS-RMPolicy">WS-RM Policy</a></cite>]. The example in <a href="#Table3">Example 2-2</a>
+ <p>The example in <a href="#Table2">Example 2-1</a> indicates a <a title="" href="#policy">policy</a> for reliable messaging [<cite><a href="#WS-RMPolicy">WS-RM Policy</a></cite>]. The example in <a href="#Table3">Example 2-2</a>
is a policy for securing messages using X509 certificates
[<cite><a href="#WS-SecurityPolicy">WS-SecurityPolicy</a></cite>].</p>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p>
+ <p style="text-align: left" class="exampleHead"><a name="Table2"></a><i><span>Example 2-1. </span>Example RM Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
@@ -343,7 +408,7 @@
(08) </wsp:Policy></pre></div>
</div>
<div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p>
+ <p style="text-align: left" class="exampleHead"><a name="Table3"></a><i><span>Example 2-2. </span>Example X509 Security Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
@@ -390,7 +455,7 @@
assumed to be located at
<code>http://www.example.com/policies</code>. Per Section
<a href="http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8/#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 URIs used for these <a title="policy expression" href="#policy_expression">policy expressions</a>
+ Policy Identification</a> of Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>], the URIs 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
<code>http://www.example.com/policies#X509EndpointPolicy</code>,
@@ -402,8 +467,8 @@
<h2><a name="rPolicyAttachment"></a>3. Policy Attachment</h2>
<p>This section defines two general-purpose mechanisms for
- associating <a title="policy" href="#policy">policies</a> with one or
- more <a title="policy subject" href="#policy_subject">policy
+ associating <a title="" href="#policy">policies</a> with one or
+ more <a title="" href="#policy_subject">policy
subjects</a>. The first allows XML-based descriptions of
resources (represented as XML elements) to associate policy as
part of their intrinsic definition. The second allows policies
@@ -415,23 +480,23 @@
<div class="div2">
<h3><a name="rEffectivePolicy"></a>3.1 Effective Policy</h3>
- <p><a title="policy" href="#policy">Policies</a> will often be
- associated with a particular <a title="policy subject" href="#policy_subject">policy subject</a> using multiple
- <a title="policy attachment" href="#policy_attachment">policy
+ <p><a title="" href="#policy">Policies</a> will often be
+ associated with a particular <a title="" href="#policy_subject">policy subject</a> using multiple
+ <a title="" href="#policy_attachment">policy
attachments</a>. For example, there may be attachments
at different points in a WSDL description that apply to a
subject, and other attachments may be made by UDDI and other
mechanisms.</p>
- <p>When multiple attachments are made, [<a title="effective policy" name="effective_policy">Definition</a>: the
-<b>effective policy</b>, for a given <a title="policy subject" href="#policy_subject">policy subject</a>, is the
+ <p>When multiple attachments are made, [<a name="effective_policy" title="effective policy">Definition</a>: the
+<b>effective policy</b>, for a given <a title="" href="#policy_subject">policy subject</a>, is the
combination of relevant policies. The relevant policies are those
-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>.]
+attached to <a title="" href="#policy_scope">policy scopes</a> that
+contain the <a title="" href="#policy_subject">policy subject</a>.]
</p>
- <p>This combination can be achieved by: [<a title="merge" name="merge">Definition</a>: a <b>merge</b>
+ <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
+ <a title="" 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>
@@ -445,9 +510,9 @@
<h3><a name="PolicyAttachmentMechanisms"></a>3.2 Policy Attachment Mechanisms</h3>
<p>This section defines two general-purpose mechanisms for
associating policies [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>] with one or
- more <a title="policy subject" href="#policy_subject">policy
+ more <a title="" href="#policy_subject">policy
subjects</a>. The first allows XML-based descriptions of
- resources to associate <a title="policy" href="#policy">policy</a>
+ resources to associate <a title="" href="#policy">policy</a>
as part of their intrinsic definition. The second allows
policies to be associated with arbitrary policy subjects
independently from their definition.</p>
@@ -468,7 +533,7 @@
on WSDL [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] and Policy.</p>
<p>This specification defines a global attribute that allows
- <a title="policy expression" href="#policy_expression">policy expressions</a> to be attached to an arbitrary XML
+ <a title="" href="#policy_expression">policy expressions</a> to be attached to an arbitrary XML
element. The following is the schema definition for the
<code class="attr">wsp:PolicyURIs</code> attribute:</p>
@@ -484,24 +549,24 @@
<p>The <code class="attr">wsp:PolicyURIs</code> attribute contains a white
space-separated list of one or more IRIs [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]. When this attribute is used,
-each of the values identifies a <a title="policy expression" href="#policy_expression">policy expression</a> as defined by
+each of the values identifies a <a title="" href="#policy_expression">policy expression</a> as defined by
[<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]. If more than one IRI is specified, the
-individual referenced <a title="policy" href="#policy">policies</a> need to be <a title="merge" href="#merge">merged</a> together
-to form a single element <a title="policy expression" href="#policy_expression">policy expression</a>.
-The resultant <a title="policy" href="#policy">policy</a> is
+individual referenced <a title="" href="#policy">policies</a> need to be <a title="merge" href="#merge">merged</a> together
+to form a single element <a title="" href="#policy_expression">policy expression</a>.
+The resultant <a title="" href="#policy">policy</a> is
then associated with the element information item's <a title="element policy" href="#element_policy">element policy</a>
-property. [<a title="element policy" name="element_policy">Definition</a>: The
- <b>element policy</b> is the <a title="policy" href="#policy">policy</a> attached to the <a title="policy subject" href="#policy_subject">policy subjects</a> associated with
+property. [<a name="element_policy" title="element policy">Definition</a>: The
+ <b>element policy</b> is the <a title="" href="#policy">policy</a> attached to the <a title="" href="#policy_subject">policy subjects</a> associated with
the element information item that contains it.]</p>
-<p>Note that the <a title="policy scope" href="#policy_scope">policy scope</a> of the attachment is specific to the
-<a title="policy attachment" href="#policy_attachment">policy attachment</a> Mechanism using it; accordingly, any <a title="policy attachment" href="#policy_attachment">policy
+<p>Note that the <a title="" href="#policy_scope">policy scope</a> of the attachment is specific to the
+<a title="" href="#policy_attachment">policy attachment</a> Mechanism using it; accordingly, any <a title="" href="#policy_attachment">policy
attachment</a> mechanism using this attribute <span class="rfc2119">MUST</span>
-define the <a title="policy scope" href="#policy_scope">policy scope</a> of the attachment.</p>
+define the <a title="" href="#policy_scope">policy scope</a> of the attachment.</p>
<p>An example of <a title="element policy" href="#element_policy">element policy</a> through the use of this global
attribute is given below using the sample policies stated in Section
<a href="#Example"><b>2.4 Example</b></a>.</p>
-<p>If the <a title="policy" href="#policy">policies</a> referenced by the following XML element</p>
+<p>If the <a title="" href="#policy">policies</a> referenced by the following XML element</p>
<div class="exampleInner"><pre><MyElement wsp:PolicyURIs="
http://www.example.com/policies#RmPolicy
http://www.example.com/policies#X509EndpointPolicy" />
@@ -510,7 +575,7 @@
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 class="exampleHead" style="text-align: left"><a name="Table4"></a><i><span>Example 3-1. </span>Example Merged Policy Expression.</i></p>
+ <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
xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -533,7 +598,7 @@
<p>Note that this <a title="element policy" href="#element_policy">element policy</a> has no meaningful IRI.</p>
<p>The presence of the <code class="attr">wsp:PolicyURIs</code> attribute does not
prohibit implementations from using additional mechanisms for
-associating <a title="policy expression" href="#policy_expression">policy expressions</a> with XML-based constructs.</p>
+associating <a title="" href="#policy_expression">policy expressions</a> with XML-based constructs.</p>
<p>Alternatively, rather than using the global attribute, XML elements
may use the <code class="elt">wsp:Policy</code> or <code class="elt">wsp:PolicyReference</code> elements directly as
children, in order to support <a title="element policy" href="#element_policy">element policy</a>, and the semantics for
@@ -550,27 +615,27 @@
<div class="div2">
<h3><a name="ExternalPolicyAttachment"></a>3.4 External Policy Attachment</h3>
-<p>This mechanism allows <a title="policy" href="#policy">policies</a> to be associated with a <a title="policy subject" href="#policy_subject">policy
+<p>This mechanism allows <a title="" href="#policy">policies</a> to be associated with a <a title="" href="#policy_subject">policy
subject</a> independent of that subject's definition and/or representation
through the use of a <code class="elt">wsp:PolicyAttachment</code>
gelement.</p>
-<p>This element has three components: the <a title="policy scope" href="#policy_scope">policy scope</a> of the
-attachment, the <a title="policy expression" href="#policy_expression">policy expressions</a> being bound, and optional security
-information. The <a title="policy scope" href="#policy_scope">policy scope</a> of the attachment is defined using one
-or more extensible domain expressions that identify <a title="policy subject" href="#policy_subject">policy subjects</a>,
+<p>This element has three components: the <a title="" href="#policy_scope">policy scope</a> of the
+attachment, the <a title="" href="#policy_expression">policy expressions</a> being bound, and optional security
+information. The <a title="" href="#policy_scope">policy scope</a> of the attachment is defined using one
+or more extensible domain expressions that identify <a title="" href="#policy_subject">policy subjects</a>,
typically using IRIs.</p>
<p>Domain expressions identify the domain of the association. That is,
-the set of <a title="policy subject" href="#policy_subject">policy subjects</a> that will be considered for inclusion in
+the set of <a title="" href="#policy_subject">policy subjects</a> that will be considered for inclusion in
the scope using an extensible domain expression model. Domain
-expressions identify <a title="policy subject" href="#policy_subject">policy subjects</a> to be included within the <a title="policy scope" href="#policy_scope">policy
-scope</a>. Domain expressions yield an unordered set of <a title="policy subject" href="#policy_subject">policy subjects</a>
+expressions identify <a title="" href="#policy_subject">policy subjects</a> to be included within the <a title="" href="#policy_scope">policy
+scope</a>. Domain expressions yield an unordered set of <a title="" href="#policy_subject">policy subjects</a>
for consideration. </p>
-<p>For the purposes of attaching <a title="policy" href="#policy">policy</a> to a <a title="policy subject" href="#policy_subject">policy subject</a> through
-this mechanism, any <a title="policy expression" href="#policy_expression">policy expression</a> contained inside of the
+<p>For the purposes of attaching <a title="" href="#policy">policy</a> to a <a title="" href="#policy_subject">policy subject</a> through
+this mechanism, any <a title="" href="#policy_expression">policy expression</a> contained inside of the
<code class="elt">wsp:AppliesTo</code> element <span class="rfc2119">MUST NOT</span> be
considered in scope. For example, an Endpoint Reference may be used as
-a domain expression, and it may contain <a title="policy expression" href="#policy_expression">policy expressions</a> within it,
-but this <a title="policy expression" href="#policy_expression">policy expressions</a> are not considered in scope with respect
+a domain expression, and it may contain <a title="" href="#policy_expression">policy expressions</a> within it,
+but this <a title="" href="#policy_expression">policy expressions</a> are not considered in scope with respect
to the <code class="elt">wsp:PolicyAttachment</code> element using it.</p>
<p>The following is the pseudo-schema for the <code class="elt">wsp:PolicyAttachment</code> element:</p>
<div class="exampleInner"><pre><wsp:PolicyAttachment … >
@@ -586,22 +651,22 @@
<dl>
<dt class="label"><code class="elt">/wsp:PolicyAttachment</code> </dt>
-<dd><p>This describes an external <a title="policy attachment" href="#policy_attachment">policy attachment</a>.</p></dd>
+<dd><p>This describes an external <a title="" href="#policy_attachment">policy attachment</a>.</p></dd>
<dt class="label"><code class="elt">/wsp:PolicyAttachment/wsp:AppliesTo</code> </dt>
-<dd><p>This required element's children describe the <a title="policy scope" href="#policy_scope">policy scope</a>.</p></dd>
+<dd><p>This required element's children describe the <a title="" href="#policy_scope">policy scope</a>.</p></dd>
<dt class="label"><code class="elt">/wsp:PolicyAttachment/wsp:AppliesTo/{any}</code> </dt>
<dd><p>These child elements <span class="rfc2119">MUST</span> specify and/or
-refine the domain expression(s) that define the <a title="policy scope" href="#policy_scope">policy scope</a>. They
+refine the domain expression(s) that define the <a title="" href="#policy_scope">policy scope</a>. They
<span class="rfc2119">MUST NOT</span> contradict the semantics of their root
element; if an element is not recognized, it <span class="rfc2119">SHOULD</span>
-be ignored. Domain expressions are XML elements that describe <a title="policy subject" href="#policy_subject">policy
-subjects</a> within a <a title="policy scope" href="#policy_scope">policy scope</a>. When more than one domain expression
-is present, the <a title="policy scope" href="#policy_scope">policy scope</a> contains the union of the <a title="policy subject" href="#policy_subject">policy subjects</a>
+be ignored. Domain expressions are XML elements that describe <a title="" href="#policy_subject">policy
+subjects</a> within a <a title="" href="#policy_scope">policy scope</a>. When more than one domain expression
+is present, the <a title="" href="#policy_scope">policy scope</a> contains the union of the <a title="" href="#policy_subject">policy subjects</a>
identified by each expression. </p>
</dd>
@@ -609,14 +674,14 @@
<dt class="label"><code class="elt">/wsp:PolicyAttachment/wsp:Policy</code> </dt>
-<dd><p>This element is a <a title="policy expression" href="#policy_expression">policy expression</a> representing a <a title="policy" href="#policy">policy</a> that
-is attached to the <a title="policy subject" href="#policy_subject">policy subjects</a> within the <a title="policy scope" href="#policy_scope">policy scope</a>.</p>
+<dd><p>This element is a <a title="" href="#policy_expression">policy expression</a> representing a <a title="" href="#policy">policy</a> that
+is attached to the <a title="" href="#policy_subject">policy subjects</a> within the <a title="" href="#policy_scope">policy scope</a>.</p>
</dd>
<dt class="label"><code class="elt">/wsp:PolicyAttachment/wsp:PolicyReference</code> </dt>
-<dd><p>This element references a <a title="policy expression" href="#policy_expression">policy expression</a> to be attached to
-the <a title="policy subject" href="#policy_subject">policy subjects</a> that are in the <a title="policy scope" href="#policy_scope">policy scope</a>. Refer to Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]
+<dd><p>This element references a <a title="" href="#policy_expression">policy expression</a> to be attached to
+the <a title="" href="#policy_subject">policy subjects</a> that are in the <a title="" href="#policy_scope">policy scope</a>. Refer to Web Services Policy 1.5 - Framework [<cite><a href="#WS-Policy">Web Services Policy Framework</a></cite>]
for additional details.</p>
</dd>
@@ -660,7 +725,7 @@
URI="http://www.example.com/policies#RmPolicy" />
</wsp:PolicyAttachment></pre></div>
-<p>In this example, the <a title="policy expression" href="#policy_expression">policy expression</a> at
+<p>In this example, the <a title="" href="#policy_expression">policy expression</a> at
<code>http://www.example.com/policies#RmPolicy</code> applies to all
interactions with the endpoint at
<code>http://www.example.com/acct</code>.</p>
@@ -670,16 +735,16 @@
<div class="div1">
<h2><a name="AttachingPolicyUsingWSDL1.1"></a>4. Attaching Policies Using WSDL 1.1</h2>
-<p>The <span class="rfc2119">RECOMMENDED</span> means of associating a <a title="policy" href="#policy">policy</a>
-with a <a title="policy subject" href="#policy_subject">policy subject</a> that has a WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>]
-description is to attach a reference to the <a title="policy" href="#policy">policy</a> within the WSDL
-component corresponding to the target <a title="policy subject" href="#policy_subject">policy subject</a>. </p>
+<p>The <span class="rfc2119">RECOMMENDED</span> means of associating a <a title="" href="#policy">policy</a>
+with a <a title="" href="#policy_subject">policy subject</a> that has a WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>]
+description is to attach a reference to the <a title="" href="#policy">policy</a> within the WSDL
+component corresponding to the target <a title="" href="#policy_subject">policy subject</a>. </p>
<p>WSDL 1.1 disallows the use of extensibility elements on certain
elements and the use of extensibility attributes on others. However,
the WS-I Basic Profile 1.1 [<cite><a href="#BP11">BP 1.1</a></cite>] overrules this
restriction and allows element extensibility everywhere. Therefore,
-the <a title="policy" href="#policy">policy</a> reference <span class="rfc2119">SHOULD</span> be attached using
+the <a title="" href="#policy">policy</a> reference <span class="rfc2119">SHOULD</span> be attached using
<code class="elt">wsp:PolicyReference</code> as child element unless it is
absolutely necessary to maintain the original WSDL 1.1 restriction, in
which case the <code class="attr">@wsp:PolicyURIs</code> attribute MAY be used
@@ -691,45 +756,45 @@
<li><p><code class="elt">wsdl11:portType/wsdl11:operation/wsdl11:fault</code> </p></li>
</ul>
-<p>If it is necessary to include the actual <a title="policy expression" href="#policy_expression">policy expressions</a> within
+<p>If it is necessary to include the actual <a title="" href="#policy_expression">policy expressions</a> within
the WSDL description itself, it is <span class="rfc2119">RECOMMENDED</span> that
their <code class="elt">wsp:Policy</code> elements be included as children of
the <code class="elt">wsdl11:definition</code> element, and referenced using
-the mechanisms just described. Alternatively, the <a title="policy expression" href="#policy_expression">policy expressions</a>
+the mechanisms just described. Alternatively, the <a title="" href="#policy_expression">policy expressions</a>
<span class="rfc2119">MAY</span> be made available through some other means,
such as WS-MetadataExchange [<cite><a href="#WS-MetadataExchange">WS-MetadataExchange</a></cite>].</p>
<p>To ensure that consumers of policy-annotated WSDL elements are
-capable of processing such <a title="policy attachment" href="#policy_attachment">policy attachments</a>, attachments using
+capable of processing such <a title="" href="#policy_attachment">policy attachments</a>, attachments using
<code class="elt">wsp:PolicyReference</code> <span class="rfc2119">SHOULD</span> be
marked as a mandatory extension (e.g., with a
<code>@wsdl11:required="true"</code> attribute).</p>
-<p>The rest of this section defines how to interpret the <a title="policy attachment" href="#policy_attachment">policy
+<p>The rest of this section defines how to interpret the <a title="" href="#policy_attachment">policy
attachments</a> when they appear within a WSDL description. </p>
<div class="div2">
<h3><a name="CalculatingEffectivyPolicywithWSDL1.1"></a>4.1 Calculating Effective Policy in WSDL 1.1</h3>
-<p><a title="policy attachment" href="#policy_attachment">Policy attachments</a> in WSDL 1.1 can be used to associate <a title="policy" href="#policy">policies</a>
-with four different types of <a title="policy subject" href="#policy_subject">policy subject</a>, identified as the service
+<p><a title="" href="#policy_attachment">Policy attachments</a> in WSDL 1.1 can be used to associate <a title="" href="#policy">policies</a>
+with four different types of <a title="" href="#policy_subject">policy subject</a>, identified as the service
policy subject, the endpoint policy subject, the operation policy
subject, and the message policy subject. These subjects should be
considered as nested, due to the hierarchical nature of WSDL. </p>
-<p>When attaching a <a title="policy" href="#policy">policy</a> to a WSDL element, a <a title="policy scope" href="#policy_scope">policy scope</a> is
-implied for that attachment. The <a title="policy scope" href="#policy_scope">policy scope</a> only contains the <a title="policy subject" href="#policy_subject">policy
+<p>When attaching a <a title="" href="#policy">policy</a> to a WSDL element, a <a title="" href="#policy_scope">policy scope</a> is
+implied for that attachment. The <a title="" href="#policy_scope">policy scope</a> only contains the <a title="" href="#policy_subject">policy
subject</a> associated with that element and not those associated with the
children of that element. Therefore, it is
-<span class="rfc2119">RECOMMENDED</span> that each <a title="policy assertion" href="#policy_assertion">policy assertion</a> contained
+<span class="rfc2119">RECOMMENDED</span> that each <a title="" href="#policy_assertion">policy assertion</a> contained
within a WSDL element's <a title="element policy" href="#element_policy">element policy</a> should have the correct
semantic such that the subject for that assertion is that WSDL
element. For example, assertions that describe behaviours regarding
the manipulation of messages should only be contained within policies
attached to WSDL message elements.</p>
<p>Figure 1 represents how the <a title="effective policy" href="#effective_policy">effective policies</a>, with regard to
-WSDL, are calculated for each of these <a title="policy subject" href="#policy_subject">policy subjects</a>. In the
-diagram, the dashed boxes represent <a title="policy scope" href="#policy_scope">policy scope</a>s implied by WSDL
-elements. For a particular <a title="policy subject" href="#policy_subject">policy subject</a>, the <a title="effective policy" href="#effective_policy">effective policy</a>
+WSDL, are calculated for each of these <a title="" href="#policy_subject">policy subjects</a>. In the
+diagram, the dashed boxes represent <a title="" href="#policy_scope">policy scope</a>s implied by WSDL
+elements. For a particular <a title="" href="#policy_subject">policy subject</a>, the <a title="effective policy" href="#effective_policy">effective policy</a>
<span class="rfc2119">MUST</span> <em>merge</em> the <a title="element policy" href="#element_policy">element policy</a> of each
-element with a <a title="policy scope" href="#policy_scope">policy scope</a> that contains the <a title="policy subject" href="#policy_subject">policy subject</a>.</p>
+element with a <a title="" href="#policy_scope">policy scope</a> that contains the <a title="" href="#policy_subject">policy subject</a>.</p>
<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
@@ -739,7 +804,7 @@
or ports) are only considered in the <a title="effective policy" href="#effective_policy">effective policy</a> of that deployed
resource itself.</p>
-<div style="text-align: center" class="figure"><a name="Figure1"></a><br><img src="effective-policy-scope.png" 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>
+<div class="figure" style="text-align: center"><a name="Figure1"></a><br><img src="effective-policy-scope.png" 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="effective-policy-scope.svg">here</a>.)</p>
<p>When attaching policies at different levels of the WSDL hierarchy, care must be taken.
@@ -748,31 +813,31 @@
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
-endpoint, there are four <a title="policy subject" href="#policy_subject">policy subjects</a> involved, each with their own
+endpoint, there are four <a title="" href="#policy_subject">policy subjects</a> involved, each with their own
<a title="effective policy" href="#effective_policy">effective policy</a>. There is an <a title="effective policy" href="#effective_policy">effective policy</a> for the message, as
well as an <a title="effective policy" href="#effective_policy">effective policy</a> for the parent operation of that message,
an <a title="effective policy" href="#effective_policy">effective policy</a> for the deployed endpoint, and the <a title="effective policy" href="#effective_policy">effective
policy</a> for the service as a whole. All four <a title="effective policy" href="#effective_policy">effective policies</a> are
applicable in relation to that specific input message.</p>
-<p>It is <span class="rfc2119">RECOMMENDED</span> that, where specific <a title="policy assertion" href="#policy_assertion">policy
-assertions</a> associated with one <a title="policy subject" href="#policy_subject">policy subject</a> are only compatible with
-specific <a title="policy assertion" href="#policy_assertion">policy assertions</a> on another <a title="policy subject" href="#policy_subject">policy subject</a> in the same
+<p>It is <span class="rfc2119">RECOMMENDED</span> that, where specific <a title="" href="#policy_assertion">policy
+assertions</a> associated with one <a title="" href="#policy_subject">policy subject</a> are only compatible with
+specific <a title="" href="#policy_assertion">policy assertions</a> on another <a title="" href="#policy_subject">policy subject</a> in the same
hierarchical chain, the policies containing these assertions should be
attached within a single WSDL binding hierarchy. </p>
-<p>For any given port, the <a title="policy alternative" href="#policy_alternative">policy
-alternatives</a> for each <a title="policy subject" href="#policy_subject">policy
+<p>For any given port, the <a title="" href="#policy_alternative">policy
+alternatives</a> for each <a title="" href="#policy_subject">policy
subject</a> type <span class="rfc2119">SHOULD</span> be compatible with
-each of the <a title="policy attachment" href="#policy_attachment">policy
-alternatives</a> at each of the <a title="policy subject" href="#policy_subject">policy subjects</a> parent and child
-<a title="policy subject" href="#policy_subject">policy subjects</a>, such that
-choices between <a title="policy alternative" href="#policy_alternative">policy
+each of the <a title="" href="#policy_attachment">policy
+alternatives</a> at each of the <a title="" href="#policy_subject">policy subjects</a> parent and child
+<a title="" href="#policy_subject">policy subjects</a>, such that
+choices between <a title="" href="#policy_alternative">policy
alternatives</a> at each level are independent of each
other.</p>
-<p>The rest of this section describes these <a title="policy subject" href="#policy_subject">policy subject</a> types, and
-how the <a title="effective policy" href="#effective_policy">effective policy</a> for each <a title="policy subject" href="#policy_subject">policy subject</a> is calculated.</p>
+<p>The rest of this section describes these <a title="" href="#policy_subject">policy subject</a> types, and
+how the <a title="effective policy" href="#effective_policy">effective policy</a> for each <a title="" href="#policy_subject">policy subject</a> is calculated.</p>
<div class="div3">
@@ -796,7 +861,7 @@
<li><p><code class="elt">wsdl11:port</code> </p></li>
<li><p><code class="elt">wsdl11:portType</code> </p></li>
<li><p><code class="elt">wsdl11:binding</code> </p></li>
-</ul><p>These elements <span class="rfc2119">MAY</span> have <a title="element policy" href="#element_policy">element policy</a> as per Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>. The <a title="policy scope" href="#policy_scope">policy scope</a> implied by each of these elements contains the endpoint policy subject representing the deployed endpoint.</p>
+</ul><p>These elements <span class="rfc2119">MAY</span> have <a title="element policy" href="#element_policy">element policy</a> as per Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>. The <a title="" href="#policy_scope">policy scope</a> implied by each of these elements contains the endpoint policy subject representing the deployed endpoint.</p>
<p>Since the <code class="elt">wsdl11:portType</code> may be used by more than one
binding, it is <span class="rfc2119">RECOMMENDED</span> that only policies
@@ -820,7 +885,7 @@
<li><p><code class="elt">wsdl11:binding/wsdl11:operation</code> </p></li>
</ul><p>These elements <span class="rfc2119">MAY</span> have <a title="element policy" href="#element_policy">element policy</a> as per Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>. </p>
-<p>The <a title="policy scope" href="#policy_scope">policy scope</a> implied by each of these elements contains the
+<p>The <a title="" href="#policy_scope">policy scope</a> implied by each of these elements contains the
operation policy subject representing the specific operation of the
endpoint policy subject.</p>
@@ -854,7 +919,7 @@
</ul>
<p>These elements <span class="rfc2119">MAY</span> have <a title="element policy" href="#element_policy">element policy</a> as per Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>.</p>
-<p>The <a title="policy scope" href="#policy_scope">policy scope</a> implied by these elements contains the message
+<p>The <a title="" href="#policy_scope">policy scope</a> implied by these elements contains the message
policy subject representing the specific input, output, or fault
message in relation to the operation policy subject.</p>
@@ -894,21 +959,21 @@
choice on a service's outbound message without a mechanism for a
requester of that service to communicate its choice to the service
before the outbound message is sent may not result in the desired
-behaviours. It is therefore <span class="rfc2119">RECOMMENDED</span> that <a title="policy alternative" href="#policy_alternative">policy
+behaviours. It is therefore <span class="rfc2119">RECOMMENDED</span> that <a title="" href="#policy_alternative">policy
alternatives</a> on outbound messages <span class="rfc2119">SHOULD</span> be avoided
-without the use of some form of mutual <a title="policy" href="#policy">policy</a> exchange between the
+without the use of some form of mutual <a title="" href="#policy">policy</a> exchange between the
parties involved.</p>
</div>
<div class="div3">
<h4><a name="Example2"></a>4.1.5 Example</h4>
-<p>As an example of the combination of these <a title="policy subject" href="#policy_subject">policy subjects</a> and
+<p>As an example of the combination of these <a title="" href="#policy_subject">policy subjects</a> and
<a title="effective policy" href="#effective_policy">effective policy</a> calculation, consider the WSDL type definition in
<a href="#Table5">Example 4-1</a> that references policies. </p>
<div class="exampleOuter">
-<p class="exampleHead" style="text-align: left"><a name="Table5"></a><i><span>Example 4-1. </span>Example Policy Attached to WSDL.</i></p>
+<p style="text-align: left" class="exampleHead"><a name="Table5"></a><i><span>Example 4-1. </span>Example Policy Attached to WSDL.</i></p>
<div class="exampleInner"><pre>(01) <wsdl11:definitions name="StockQuote"
targetNamespace="http://www.example.com/stock/binding"
xmlns:tns="http://www.example.com/stock/binding"
@@ -975,7 +1040,7 @@
whose XML 1.0 representation is listed in <a href="#Table6">Example 4-2</a>.</p>
<div class="exampleOuter">
-<p class="exampleHead" style="text-align: left"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p>
+<p style="text-align: left" class="exampleHead"><a name="Table6"></a><i><span>Example 4-2. </span>Example Message Security Policy Expression.</i></p>
<div class="exampleInner"><pre>(01) <wsp:Policy
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
@@ -997,36 +1062,36 @@
<h2><a name="AttachingPoliciesUsingUDDI"></a>5. Attaching Policies Using UDDI</h2>
<p>This section defines a mechanism for associating policies with
-<a title="policy subject" href="#policy_subject">policy subjects</a> through the use of UDDI. It defines a minimum level of
-support for associating <a title="policy expression" href="#policy_expression">policy expressions</a> with entities in a UDDI
+<a title="" href="#policy_subject">policy subjects</a> through the use of UDDI. It defines a minimum level of
+support for associating <a title="" href="#policy_expression">policy expressions</a> with entities in a UDDI
registry. The calculation of <a title="effective policy" href="#effective_policy">effective policy</a> for UDDI entities is
described in Section <a href="#CalculatingEffectivePolicyElementPolicyUDDI"><b>5.1 Calculating Effective Policy and Element Policy in UDDI</b></a>. While the general
-concept for associating <a title="policy expression" href="#policy_expression">policy expressions</a> with UDDI entities, which
+concept for associating <a title="" href="#policy_expression">policy expressions</a> with UDDI entities, which
is specified in Sections <a href="#ReferencingRemotePolicyExpressions"><b>5.2 Referencing Remote Policy Expressions</b></a> and <a href="#RegisteringReusablePolicyExpressions"><b>5.3 Registering Reusable Policy Expressions</b></a>, is based on UDDI Version 2 [<cite><a href="#UDDIAPI20">UDDI API 2.0</a></cite>, <cite><a href="#UDDIDataStructure20">UDDI Data Structure 2.0</a></cite>], the necessary
changes with respect to UDDI Version 3 [<cite><a href="#UDDI30">UDDI 3.0</a></cite>] are
explained in Section <a href="#RegisteringPoliciesUDDIVersion3"><b>5.4 Registering Policies in UDDI Version 3</b></a>.</p>
<p>There are essentially two approaches for registering policies in
-UDDI. One approach is to directly reference remotely accessible <a title="policy expression" href="#policy_expression">policy
-expressions</a> in UDDI entities, the other is to register <a title="policy expression" href="#policy_expression">policy
+UDDI. One approach is to directly reference remotely accessible <a title="" href="#policy_expression">policy
+expressions</a> in UDDI entities, the other is to register <a title="" href="#policy_expression">policy
expressions</a> as distinct tModels and then reference these tModels in
-each UDDI entity that is using the <a title="policy expression" href="#policy_expression">policy expression</a>. While the former
+each UDDI entity that is using the <a title="" href="#policy_expression">policy expression</a>. While the former
approach (see Section <a href="#ReferencingRemotePolicyExpressions"><b>5.2 Referencing Remote Policy Expressions</b></a>) is expected to be used for
-<a title="policy expression" href="#policy_expression">policy expressions</a> that are mainly unique for a given Web service, the
+<a title="" href="#policy_expression">policy expressions</a> that are mainly unique for a given Web service, the
latter approach (see Section <a href="#RegisteringReusablePolicyExpressions"><b>5.3 Registering Reusable Policy Expressions</b></a>) is expected to be used
-for more modular and reusable <a title="policy expression" href="#policy_expression">policy expressions</a>.</p>
+for more modular and reusable <a title="" href="#policy_expression">policy expressions</a>.</p>
<div class="div2">
<h3><a name="CalculatingEffectivePolicyElementPolicyUDDI"></a>5.1 Calculating Effective Policy and Element Policy in UDDI</h3>
-<p>When attaching a <a title="policy" href="#policy">policy</a> to a UDDI entity a <a title="policy scope" href="#policy_scope">policy scope</a> is implied
-for that attachment. The <a title="policy scope" href="#policy_scope">policy scope</a> only contains the <a title="policy subject" href="#policy_subject">policy
+<p>When attaching a <a title="" href="#policy">policy</a> to a UDDI entity a <a title="" href="#policy_scope">policy scope</a> is implied
+for that attachment. The <a title="" href="#policy_scope">policy scope</a> only contains the <a title="" href="#policy_subject">policy
subjects</a> associated with that entity, and not those associated with
-the children of that entity. This <a title="policy" href="#policy">policy</a> is the entity's <a title="element policy" href="#element_policy">element
+the children of that entity. This <a title="" href="#policy">policy</a> is the entity's <a title="element policy" href="#element_policy">element
policy</a>.</p>
-<p>Each <a title="policy assertion" href="#policy_assertion">policy assertion</a> contained within a UDDI entity's <a title="element policy" href="#element_policy">element
+<p>Each <a title="" href="#policy_assertion">policy assertion</a> contained within a UDDI entity's <a title="element policy" href="#element_policy">element
policy</a> should have the correct semantic such that the subject for that
assertion is that UDDI entity. For example, assertions that describe
behaviours regarding a service provider should only be contained
@@ -1093,7 +1158,7 @@
</ul>
<p>These elements <span class="rfc2119">MAY</span> have <a title="element policy" href="#element_policy">element policy</a> as per
-Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>. The <a title="policy scope" href="#policy_scope">policy scope</a> implied by
+Section <a href="#rPolicyAttachment"><b>3. Policy Attachment</b></a>. The <a title="" href="#policy_scope">policy scope</a> implied by
each of these elements contains the endpoint policy subject
representing the deployed endpoint.</p>
@@ -1117,25 +1182,25 @@
metadata with services and other entities in a UDDI registry. To
properly integrate Web Services Policy into the UDDI model, Web Services Policy 1.5 - Attachment
pre-defines one tModel that is used to associate a remotely accessible
-<a title="policy" href="#policy">policy</a> with an entity in a UDDI registry.</p>
+<a title="" href="#policy">policy</a> with an entity in a UDDI registry.</p>
<p>This new tModel is called the remote policy reference category
system and is defined in Appendix <a href="#RemotePolicyReferenceCategorySystem"><b>B.1 Remote Policy Reference Category System</b></a>.</p>
-<p>UDDI registries <span class="rfc2119">MUST</span> use the <code class="attr">tModelKey</code>
+ <p>UDDI registries <span class="rfc2119">MUST</span> use the (UDDI V2 [<cite><a href="#UDDIDataStructure20">UDDI Data Structure 2.0</a></cite>]) <code class="attr">tModelKey</code>
<code>uuid:a27078e4-fd38-320a-806f-6749e84f8005</code> to uniquely identify this
tModel so that UDDI registry users can expect the same behavior across
different UDDI registries.</p>
<p>The tModel's valid values are those IRIs that identify external
-<a title="policy expression" href="#policy_expression">policy expressions</a>; that is, when referencing this category system in
+<a title="" href="#policy_expression">policy expressions</a>; that is, when referencing this category system in
a <code class="elt">categoryBag</code> , the corresponding <code class="attr">keyValue</code> of the <code class="elt">keyedReference</code> is the
-IRI of the <a title="policy expression" href="#policy_expression">policy expression</a>.</p>
+IRI of the <a title="" href="#policy_expression">policy expression</a>.</p>
<p>Using the remote policy reference category system, one can then
-associate a <a title="policy expression" href="#policy_expression">policy expression</a> with a <code class="elt">businessEntity</code> , a
+associate a <a title="" href="#policy_expression">policy expression</a> with a <code class="elt">businessEntity</code> , a
<code class="elt">businessService</code> , and a tModel using the entity's <code class="elt">categoryBag</code> . For
-example, associating the <a title="policy expression" href="#policy_expression">policy expression</a> that is identified by the
+example, associating the <a title="" href="#policy_expression">policy expression</a> that is identified by the
IRI <code>http://www.example.com/myservice/policy</code> with a <code class="elt">businessService</code> is
done as follows: </p>
@@ -1154,9 +1219,9 @@
<p>The <code class="attr">tModelKey</code> of the <code class="elt">keyedReference</code> <span class="rfc2119">MUST</span> match
the fixed <code class="attr">tModelKey</code> from the remote policy reference category
system. The <code class="attr">keyValue</code> <span class="rfc2119">MUST</span> be the IRI that
-identifies the <a title="policy expression" href="#policy_expression">policy expression</a>.</p>
+identifies the <a title="" href="#policy_expression">policy expression</a>.</p>
-<p>A different approach has to be taken to associate a <a title="policy expression" href="#policy_expression">policy
+<p>A different approach has to be taken to associate a <a title="" href="#policy_expression">policy
expression</a> with a <code class="elt">bindingTemplate</code> , since bindingTemplates do not
contain a <code class="elt">categoryBag</code> in UDDI Version 2. Therefore, the
<code class="elt">bindingTemplate</code> 's <code class="elt">tModelInstanceInfo</code> and <code class="elt">instanceParms</code>
@@ -1179,20 +1244,20 @@
<p>The <code class="attr">tModelKey</code> of the <code class="elt">tModelInstanceInfo</code> <span class="rfc2119">MUST</span>
match the fixed <code class="attr">tModelKey</code> from the remote policy reference category
system as defined above. The <code class="elt">instanceParms</code> <span class="rfc2119">MUST</span> be
-the IRI that identifies the <a title="policy expression" href="#policy_expression">policy expression</a>.</p>
+the IRI that identifies the <a title="" href="#policy_expression">policy expression</a>.</p>
</div>
<div class="div2">
<h3><a name="RegisteringReusablePolicyExpressions"></a>5.3 Registering Reusable Policy Expressions</h3>
<p>In addition to using the approach outlined in the section above,
-publishers may register a specific <a title="policy expression" href="#policy_expression">policy expression</a> in a UDDI
+publishers may register a specific <a title="" href="#policy_expression">policy expression</a> in a UDDI
registry as a distinct tModel. To properly categorize tModels as
-<a title="policy expression" href="#policy_expression">policy expressions</a>, Web Services Policy 1.5 - Attachment pre-defines the Web Services Policy
+<a title="" href="#policy_expression">policy expressions</a>, Web Services Policy 1.5 - Attachment pre-defines the Web Services Policy
Types category system as a tModel. This tModel is defined in Appendix
<a href="#WS-PolicyTypesCategorySystem"><b>B.2 Web Services Policy Types Category System</b></a>.</p>
-<p>The following illustrates a tModel for the <a title="policy expression" href="#policy_expression">policy expression</a>
+<p>The following illustrates a tModel for the <a title="" href="#policy_expression">policy expression</a>
identified by the IRI
<code>http://www.example.com/myservice/policy</code>.</p>
@@ -1218,21 +1283,21 @@
</tModel></pre></div>
<p>The first <code class="elt">keyedReference</code> specifies that the tModel represents a
-<a title="policy expression" href="#policy_expression">policy expression</a> — rather than only being associated with one
+<a title="" href="#policy_expression">policy expression</a> — rather than only being associated with one
— by using the Web Services Policy Types category system's built-in
category <code>"policy"</code>, which is its single valid value. This is necessary
-in order to enable UDDI inquiries for <a title="policy expression" href="#policy_expression">policy expressions</a> in
-general. The second <code class="elt">keyedReference</code> designates the <a title="policy expression" href="#policy_expression">policy expression</a>
+in order to enable UDDI inquiries for <a title="" href="#policy_expression">policy expressions</a> in
+general. The second <code class="elt">keyedReference</code> designates the <a title="" href="#policy_expression">policy expression</a>
the tModel represents by using the approach from the section
above. This is necessary in order to enable UDDI inquiries for
-particular <a title="policy expression" href="#policy_expression">policy expressions</a> based on their IRI.</p>
+particular <a title="" href="#policy_expression">policy expressions</a> based on their IRI.</p>
-<p>Note that the <a title="policy expression" href="#policy_expression">policy expression</a> IRI is also specified in the
+<p>Note that the <a title="" href="#policy_expression">policy expression</a> IRI is also specified in the
tModel's overview URL to indicate that it is a resolvable URL to
-actually retrieve the <a title="policy expression" href="#policy_expression">policy expression</a>.</p>
+actually retrieve the <a title="" href="#policy_expression">policy expression</a>.</p>
<p>Web Services Policy 1.5 - Attachment pre-defines another tModel that is used to
-associate such a pre-registered, locally available <a title="policy expression" href="#policy_expression">policy expressions</a>
+associate such a pre-registered, locally available <a title="" href="#policy_expression">policy expressions</a>
with an entity in a UDDI registry</p>
<p>This new tModel is called the local policy reference category
@@ -1254,12 +1319,12 @@
<p>That is, when referencing this category system in a category bag,
the corresponding <code class="attr">keyValue</code> of the <code class="elt">keyedReference</code> is the <code class="attr">tModelKey</code> of
-the tModel that represents the <a title="policy expression" href="#policy_expression">policy expression</a>.</p>
+the tModel that represents the <a title="" href="#policy_expression">policy expression</a>.</p>
<p>Given the local policy reference category system, one can then
-associate a <a title="policy expression" href="#policy_expression">policy expression</a> tModel with a <code class="elt">businessEntity</code> , a
+associate a <a title="" href="#policy_expression">policy expression</a> tModel with a <code class="elt">businessEntity</code> , a
<code class="elt">businessService</code> , and a tModel using the entity's <code class="elt">categoryBag</code> . For
-example, associating the <a title="policy expression" href="#policy_expression">policy expression</a> tModel with the <code class="attr">tModelKey</code>
+example, associating the <a title="" href="#policy_expression">policy expression</a> tModel with the <code class="attr">tModelKey</code>
<code>"uuid:04cfa…"</code> from above with a <code class="elt">businessService</code> is done as
follows: </p>
@@ -1278,9 +1343,9 @@
<p>The <code class="attr">tModelKey</code> of the <code class="elt">keyedReference</code> <span class="rfc2119">MUST</span> match
the fixed <code class="attr">tModelKey</code> from the local policy reference category
system. The keyValue <span class="rfc2119">MUST</span> be the <code class="attr">tModelKey</code> of the
-<a title="policy expression" href="#policy_expression">policy expression</a> that is registered with the UDDI registry.</p>
+<a title="" href="#policy_expression">policy expression</a> that is registered with the UDDI registry.</p>
-<p>A different approach has to be taken to associate a <a title="policy expression" href="#policy_expression">policy
+<p>A different approach has to be taken to associate a <a title="" href="#policy_expression">policy
expression</a> with a <code class="elt">bindingTemplate</code> , since bindingTemplates do not
contain a <code class="elt">categoryBag</code> in UDDI Version 2. Therefore, the
<code class="elt">bindingTemplate</code> 's <code class="elt">tModelInstanceInfo</code> and <code class="elt">instanceParms</code>
@@ -1301,7 +1366,7 @@
<p>The tModelKey of the <code class="elt">tModelInstanceInfo</code>
<span class="rfc2119">MUST</span> match the fixed <code class="attr">tModelKey</code> from the
local policy reference category system. The <code class="elt">instanceParms</code>
-<span class="rfc2119">MUST</span> be the <code class="attr">tModelKey</code> of the <a title="policy expression" href="#policy_expression">policy
+<span class="rfc2119">MUST</span> be the <code class="attr">tModelKey</code> of the <a title="" href="#policy_expression">policy
expression</a> that is registered with the UDDI registry.</p>
</div>
@@ -1328,7 +1393,7 @@
<p>The <code class="attr">tModelKey</code> for the Web Services Policy Types tModel changes from <code>"uuid:fa1d77dc-edf0-3a84-a99a-5972e434e993"</code> to <code>"uddi:schemas.xmlsoap.org:policytypes:2003_03"</code>.</p>
<p>The <code class="attr">tModelKey</code> for the local policy reference tModel changes from <code>"uuid:a27f7d45-ec90-31f7-a655-efe91433527c"</code> to <code>"uddi:schemas.xmlsoap.org:localpolicyreference:2003_03"</code>.</p>
-<p>Second, rather than putting <a title="policy expression" href="#policy_expression">policy expression</a> references in a
+<p>Second, rather than putting <a title="" href="#policy_expression">policy expression</a> references in a
<code class="elt">bindingTemplate</code> 's <code class="elt">tModelInstanceInfo</code> , they are added to the
<code class="elt">bindingTemplate</code> 's <code class="elt">categoryBag</code> , analogous to the mechanism described
for other UDDI entities. For example, the example <code class="elt">bindingTemplate</code> from
@@ -1347,10 +1412,11 @@
</categoryBag>
</bindingTemplate></pre></div>
-<p>Third, inquiries for reusable <a title="policy expression" href="#policy_expression">policy expression</a> tModels and UDDI
-entities that are associated with remote <a title="policy expression" href="#policy_expression">policy expression</a> is enhanced
+<p>Third, inquiries for reusable <a title="" href="#policy_expression">policy expression</a> tModels
+ described in Section <a href="#RegisteringReusablePolicyExpressions"><b>5.3 Registering Reusable Policy Expressions</b></a> and UDDI
+tModel entities that are associated with remote <a title="" href="#policy_expression">policy expression</a> is enhanced
by the wildcard mechanism for keyValues in keyedReferences. For
-example, searching for all <a title="policy expression" href="#policy_expression">policy expression</a> tModels whose IRI starts
+example, searching for all <a title="" href="#policy_expression">policy expression</a> tModels whose IRI starts
with <code>http://www.example.com/</code>, the following <code>find_tModel</code> API call can
be used: </p>
@@ -1368,7 +1434,7 @@
<p>Fourth, all UDDI entities may be digitally signed using XML digital
signatures [<cite><a href="#XML-Signature">XML-Signature</a></cite>]. Publishers who want to
-digitally sign their <a title="policy expression" href="#policy_expression">policy expression</a> tModels or <a title="policy expression" href="#policy_expression">policy expression</a>
+digitally sign their <a title="" href="#policy_expression">policy expression</a> tModels or <a title="" href="#policy_expression">policy expression</a>
references in UDDI <span class="rfc2119">MUST</span> use the Schema-centric
canonicalization algorithm [<cite><a href="#SCC14N">SCC14N</a></cite>].</p>
@@ -1378,14 +1444,14 @@
<h2><a name="SecurityConsiderations"></a>6. Security Considerations</h2>
-<p>It is <span class="rfc2119">RECOMMENDED</span> that <a title="policy attachment" href="#policy_attachment">policy attachments</a> be
+<p>It is <span class="rfc2119">RECOMMENDED</span> that <a title="" href="#policy_attachment">policy attachments</a> be
signed to prevent tampering. This also provides a mechanism for
-authenticating <a title="policy attachment" href="#policy_attachment">policy attachments</a> by determining if the signer has the
-right to "speak for" the scope of the <a title="policy attachment" href="#policy_attachment">policy attachment</a>.</p>
+authenticating <a title="" href="#policy_attachment">policy attachments</a> by determining if the signer has the
+right to "speak for" the scope of the <a title="" href="#policy_attachment">policy attachment</a>.</p>
<p>Policies <span class="rfc2119">SHOULD NOT</span> be accepted unless they are
signed and have an associated security token to specify the signer has
-the right to "speak for" the scope containing the <a title="policy" href="#policy">policy</a>.</p>
+the right to "speak for" the scope containing the <a title="" href="#policy">policy</a>.</p>
</div>
<div class="div1">
@@ -1605,7 +1671,7 @@
<div class="div3">
<h4><a name="DesigGoals1"></a>B.1.1 Design Goals</h4>
-<p>This tModel is used to attach a <a title="policy" href="#policy">policy</a> to a UDDI entity by referencing the policy's IRI.</p>
+<p>This tModel is used to attach a <a title="" href="#policy">policy</a> to a UDDI entity by referencing the policy's IRI.</p>
</div>
<div class="div3">
@@ -1656,11 +1722,11 @@
<div class="div3">
<h4><a name="DesignGoals2"></a>B.2.1 Design Goals</h4>
-<p>This tModel is used to categorize tModels as representing <a title="policy expression" href="#policy_expression">policy
+<p>This tModel is used to categorize tModels as representing <a title="" href="#policy_expression">policy
expressions</a>. There is only one valid value, namely <code>"policy"</code>, that
indicates this very fact. It is <span class="rfc2119">RECOMMENDED</span> that tModels categorized as
-representing <a title="policy expression" href="#policy_expression">policy expressions</a> reference no more and no less than
-this very <a title="policy expression" href="#policy_expression">policy expression</a> using the remote policy reference category
+representing <a title="" href="#policy_expression">policy expressions</a> reference no more and no less than
+this very <a title="" href="#policy_expression">policy expression</a> using the remote policy reference category
system.</p>
</div>
<div class="div3">
@@ -1673,7 +1739,7 @@
</tr>
<tr><th rowspan="1" colspan="1">Description:</th>
<td rowspan="1" colspan="1">Web services policy types category system used for UDDI tModels to
-characterize them as Web services policy–based <a title="policy expression" href="#policy_expression">policy expressions</a>.</td>
+characterize them as Web services policy–based <a title="" href="#policy_expression">policy expressions</a>.</td>
</tr>
<tr><th rowspan="1" colspan="1">UDDI Key (V3):</th>
<td rowspan="1" colspan="1"><code>uddi:schemas.xmlsoap.org:policytypes:2003_03</code></td>
@@ -1709,11 +1775,11 @@
<div class="div3">
<h4><a name="DesignGoals3"></a>B.3.1 Design Goals</h4>
-<p>This tModel is used to attach a <a title="policy expression" href="#policy_expression">policy expression</a> to a UDDI entity
-by referencing the UDDI entity that represents this <a title="policy expression" href="#policy_expression">policy expression</a>. The local policy
+<p>This tModel is used to attach a <a title="" href="#policy_expression">policy expression</a> to a UDDI entity
+by referencing the UDDI entity that represents this <a title="" href="#policy_expression">policy expression</a>. The local policy
reference category system is based on tModelKeys. It is expected that
referenced tModels are registered with the same UDDI registry and are
-categorized as representing <a title="policy expression" href="#policy_expression">policy
+categorized as representing <a title="" href="#policy_expression">policy
expressions</a> using the Web services policy types category
system.</p>
</div>
@@ -1727,12 +1793,12 @@
</tr>
<tr><th rowspan="1" colspan="1">Description:</th>
<td rowspan="1" colspan="1">Category system used for UDDI entities to point to a Web services
-policy <a title="policy expression" href="#policy_expression">policy expression</a>
+policy <a title="" href="#policy_expression">policy expression</a>
tModel that describes their characteristics. See Web Services Policy 1.5 - Attachment
specification for further details.</td>
</tr>
<tr><th rowspan="1" colspan="1">UDDI Key (V3):</th>
-<td rowspan="1" colspan="1"><code>uddi:schemas.xmlsoap.org:remotepolicyreference:2003_03</code></td>
+<td rowspan="1" colspan="1"><code>uddi:schemas.xmlsoap.org:localpolicyreference:2003_03</code></td>
</tr>
<tr><th rowspan="1" colspan="1">UDDI V1,V2 format key:</th>
<td rowspan="1" colspan="1"><code>uuid:a27f7d45-ec90-31f7-a655-efe91433527c</code></td>
@@ -1758,9 +1824,13 @@
keyValue="categorization"
tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />
<keyedReference
- keyName="uddi-org:entityKeyValues"
- keyValue="tModelKey"
- tModelKey="uuid:916b87bf-0756-3919-8eae-97dfa325e5a4" />
+ keyName="uddi-org:types:checked"
+ keyValue="checked"
+ tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62aB4" />
+ <keyedReference
+ keyName="uddi-org:entityKeyValues"
+ keyValue="tModelKey"
+ tModelKey="uuid:916b87bf-0756-3919-8eae-97dfa325e5a4" />
</categoryBag>
</tModel> </pre></div>
</div>
@@ -1955,9 +2025,7 @@
for adding document attribute extensbility of wsp:Policy/@{any} and wsp:Policy/.../wsp:PolicyReference/@{any},
specifically making attribute extensibility for any namespace.
</td>
- </tr>
-
- </tbody>
+ </tr>
<tr>
<td rowspan="1" colspan="1">20060906</td>
<td rowspan="1" colspan="1">ASV</td>
@@ -1967,6 +2035,16 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3557">3557</a>: clarify the use of domain expressions.
</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060924</td>
+ <td rowspan="1" colspan="1">TIB</td>
+ <td rowspan="1" colspan="1">Implemented the
+ <a href="http://www.w3.org/2006/09/14-ws-policy-minutes.html#item12">resolution</a>
+ for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3709">3709</a>: Editorial corrections from UDDI team.
+ </td>
+ </tr>
+ </tbody>
</table><br>
</div>
</div>
Received on Monday, 25 September 2006 03:15:18 UTC