- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 02 Oct 2006 02:33:32 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv13307/ws/policy
Modified Files:
build.xml ws-policy-attachment.html ws-policy-attachment.xml
ws-policy-framework.html ws-policy-framework.xml
ws-policy-primer.html
Log Message:
Made framework and attachment doc valid again. Changed build file so that it validates the XML documents (was not the case before).
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- ws-policy-primer.html 29 Sep 2006 18:02:08 -0000 1.16
+++ ws-policy-primer.html 2 Oct 2006 02:33:29 -0000 1.17
@@ -1,5 +1,6 @@
-<!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 - Primer</title><style type="text/css">
+<!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 - Primer</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -47,196 +48,124 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...2506 lines suppressed...]
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0165.html">reported by Paul Cotton.</a>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">20060928</td>
- <td rowspan="1" colspan="1">PY</td>
- <td rowspan="1" colspan="1">Completed making remaining changes to address issues
+ </td></tr><tr><td rowspan="1" colspan="1">20060928</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed making remaining changes to address issues
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0165.html">reported by Paul Cotton.</a>
Fixing up the Acknowledgements is pending
- </td>
- </tr>
- </tbody>
- </table><br>
- </div>
- </div>
-</body></html>
\ No newline at end of file
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- ws-policy-framework.xml 27 Sep 2006 22:46:28 -0000 1.55
+++ ws-policy-framework.xml 2 Oct 2006 02:33:29 -0000 1.56
@@ -798,8 +798,7 @@
assertions. The reason for requring least an empty <code><wsp:Policy/></code>
Element above is to ensure that two assertions of the same type will always be
compatible and an intersection would not fail
-(see Section <specref ref="Policy_Intersection"/>).</p></def>
-
+(see Section <specref ref="Policy_Intersection"/>).</p>
<p>Note: This specification does not define processing for arbitrary
<el>wsp:Policy</el> Element Information Items in the descendants
of an assertion parameter, e.g., in the <emph
@@ -807,6 +806,7 @@
role="infoset-property">children</emph> as in
<code><Lorem><Ipsum><wsp:Policy> …
</wsp:Policy></Ipsum></Lorem></code>.</p>
+</def>
</gitem>
</glist>
<p>Policy assertions containing a nested policy expression are
@@ -1912,16 +1912,16 @@
<tr>
<td>20060920</td>
<td>DBO</td>
- <td>Completed action item:
- <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/24">24</loc>
- for issue
+ <td>Completed action item:<ulist>
+ <item><p><loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/24">24</loc>
+ for issues
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3662">3662</loc>,
- Add PolicyReference extensibility as ##any.
- <br/>
+ Add PolicyReference extensibility as ##any.</p></item>
+ <item><p>
and <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/25">25</loc>
for issue
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3590">3590</loc>,
- Add PolicyReference extensibility.
+ Add PolicyReference extensibility.</p></item></ulist>
</td>
</tr>
<tr>
Index: ws-policy-attachment.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- ws-policy-attachment.html 26 Sep 2006 07:38:22 -0000 1.46
+++ ws-policy-attachment.html 2 Oct 2006 02:33:29 -0000 1.47
@@ -1,5 +1,6 @@
-<!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">
+<!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; }
div.constraint,
@@ -47,40 +48,24 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...2970 lines suppressed...]
<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>
- <tr>
- <td rowspan="1" colspan="1">20060925</td>
- <td rowspan="1" colspan="1">ASV</td>
- <td rowspan="1" colspan="1">Created <a href="#ws-policy-attachment-for-wsdl20"><b>5. WS-Policy Attachment for WSDL 2.0</b></a> per action item <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/37">2</a> from the
- Bellevue F2F. This section is based on a <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0037.html">contribution</a> from BEA, IBM, Microsoft and Oracle.</td>
- </tr>
- </tbody>
- </table><br>
- </div>
-</div>
-</body></html>
\ No newline at end of file
+ </td></tr><tr><td rowspan="1" colspan="1">20060925</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Created <a href="#ws-policy-attachment-for-wsdl20"><b>5. WS-Policy Attachment for WSDL 2.0</b></a> per action item <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/37">2</a> from the
+ Bellevue F2F. This section is based on a <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Sep/0037.html">contribution</a> from BEA, IBM, Microsoft and Oracle.</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: build.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/build.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- build.xml 24 Sep 2006 12:49:29 -0000 1.12
+++ build.xml 2 Oct 2006 02:33:29 -0000 1.13
@@ -29,13 +29,9 @@
</target>
<target name="validate-policy-specs" description="Validates all WS Policy spec files." depends="glossaries">
- <xmlvalidate lenient="false" warn="yes">
- <fileset dir=".">
- <filename name="ws-policy-framework.xml"/>
- <filename name="ws-policy-attachment.xml"/>
- <filename name="ws-policy-primer.xml"/>
- </fileset>
- </xmlvalidate>
+ <xmlvalidate lenient="false" warn="yes" file="ws-policy-framework.xml"/>
+ <xmlvalidate lenient="false" warn="yes" file="ws-policy-attachment.xml"/>
+ <xmlvalidate lenient="false" warn="yes" file="ws-policy-primer.xml"/>
</target>
<target name="validate" depends="validate-xsl,validate-svg,validate-policy-specs" />
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- ws-policy-framework.html 27 Sep 2006 22:48:04 -0000 1.41
+++ ws-policy-framework.html 2 Oct 2006 02:33:29 -0000 1.42
@@ -1,5 +1,6 @@
-<!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 - Framework</title><style type="text/css">
+<!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 - Framework</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -47,49 +48,30 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...2136 lines suppressed...]
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">20060927</td>
- <td rowspan="1" colspan="1">PY</td>
- <td rowspan="1" colspan="1">Completed action item:
+ </td></tr><tr><td rowspan="1" colspan="1">20060927</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed action item:
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/46">46</a>
resolution for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3752">3752</a> - Clarify restrictions of ID type usage.
- </td>
- </tr>
- </tbody>
- </table><br>
- </div>
- </div>
-</body></html>
\ No newline at end of file
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- ws-policy-attachment.xml 26 Sep 2006 07:38:22 -0000 1.43
+++ ws-policy-attachment.xml 2 Oct 2006 02:33:29 -0000 1.44
@@ -988,16 +988,16 @@
<p>This section describes a mechanism for associating policy expressions with Web
service constructs in WSDL 2.0. The mechanism consists of:</p>
<ulist>
- <item>A model for attaching policies to WSDL 2.0 constructs. The model defines:<ulist>
- <item>A partitioning of WSDL constructs into service, endpoint, operation
- and message policy subjects.</item>
- <item>The semantics of attaching a policy to each policy subject.</item>
- <item>How to combine policies attached to more than one WSDL component
- within a single policy subject.</item>
- </ulist></item>
- <item>An XML representation of policy expressions attached to WSDL 2.0 constructs
+ <item><p>A model for attaching policies to WSDL 2.0 constructs. The model defines:<ulist>
+ <item><p>A partitioning of WSDL constructs into service, endpoint, operation
+ and message policy subjects.</p></item>
+ <item><p>The semantics of attaching a policy to each policy subject.</p></item>
+ <item><p>How to combine policies attached to more than one WSDL component
+ within a single policy subject.</p></item>
+ </ulist></p></item>
+ <item><p>An XML representation of policy expressions attached to WSDL 2.0 constructs
and annotating those policy expressions as required extensions using the
- WSDL-defined extensibility flag <code>@wsdl20:required</code>.</item>
+ WSDL-defined extensibility flag <code>@wsdl20:required</code>.</p></item>
</ulist>
<p><specref ref="XMLNamespaces"/> lists all the XML Namespaces that are used in this section. (XML
elements without a namespace prefix are from the Web Services Policy XML Namespace.)</p>
@@ -1080,52 +1080,52 @@
<head>Attaching Policy Expressions</head>
<p>Policy attachment points in a WSDL 2.0 document are:</p>
<ulist>
- <item>
+ <item><p>
<code>wsdl20:service</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:endpoint</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:operation</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:fault</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:operation/wsdl20:input</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:operation/wsdl20:output</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:operation/wsdl20:infault</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:binding/wsdl20:operation/wsdl20:outfault</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:interface</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:interface/wsdl20:operation</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:interface/wsdl20:fault</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:interface/wsdl20:operation/wsdl20:input</code>
- </item>
- <item>
+ </p></item>
+ <item><p>
<code>wsdl20:interface/wsdl20:operation/wsdl20:output</code>
- </item>
- <item><code>wsdl20:interface/wsdl20:operation/wsdl20:infault</code> and</item>
- <item>
+ </p></item>
+ <item><p><code>wsdl20:interface/wsdl20:operation/wsdl20:infault</code> and</p></item>
+ <item><p>
<code>wsdl20:interface/wsdl20:operation/wsdl20:outfault.</code>
- </item>
+ </p></item>
</ulist>
<p>Any of these elements <rfc2119>MAY</rfc2119> have one or more <code>Policy</code> or
<code>PolicyReference</code> child elements.</p>
@@ -1136,7 +1136,6 @@
attached to a <termref def="policy_subject">policy subject</termref> in a WSDL document, capabilities and requirements
represented by the <termref def="policy_expression">policy expression</termref> apply to any message exchange or message
associated with (or described by) the <termref def="policy_subject">policy subject</termref>.</p>
- <div>
<table id="association-of-policy-attachment-points-with-policy-subjects" border="1" cellspacing='0' cellpadding='5'>
<caption>Association of Policy Attachment Points with Policy Subjects</caption>
<thead>
@@ -1268,7 +1267,6 @@
</tr>
</tbody>
</table>
- </div>
<p>For a WSDL component, the attached <termref def="policy">policy</termref> (extension to the WSDL component model
is described in <specref ref="extension-to-wsdl-component-model"/>) is
considered an intrinsic part of the WSDL component definition and applies to all
@@ -1322,30 +1320,29 @@
<termref def="policy_expression">policy expressions</termref> may be included as children of the <code>wsdl20:description</code>
element and may not be attached to any policy attachment point in a WSDL
document.)</p>
- </div2>
+ </div2>
<div2 id="extension-to-wsdl-component-model">
<head>Extension to WSDL Component Model</head>
<p>This document adds an optional {policy} property to the following WSDL
components:</p>
<ulist>
- <item>Service</item>
- <item>Endpoint</item>
- <item>Binding</item>
- <item>Binding Operation</item>
- <item>Binding Fault</item>
- <item>Binding Message Reference</item>
- <item>Binding Fault Reference</item>
- <item>Interface</item>
- <item>Interface Operation</item>
- <item>Interface Fault</item>
- <item>Interface Message Reference</item>
- <item>Interface Fault Reference</item>
+ <item><p>Service</p></item>
+ <item><p>Endpoint</p></item>
+ <item><p>Binding</p></item>
+ <item><p>Binding Operation</p></item>
+ <item><p>Binding Fault</p></item>
+ <item><p>Binding Message Reference</p></item>
+ <item><p>Binding Fault Reference</p></item>
+ <item><p>Interface</p></item>
+ <item><p>Interface Operation</p></item>
+ <item><p>Interface Fault</p></item>
+ <item><p>Interface Message Reference</p></item>
+ <item><p>Interface Fault Reference</p></item>
</ulist>
<p>The {policy} property, when present, represents the capabilities and requirements
as a <termref def="policy">policy</termref>. The value of the {policy} property is a <termref def="policy">policy</termref> as defined by
Section 3 - Policy Model in the WS-Policy specification [<bibref ref="WS-Policy"/>]. The following table
describes the mapping from XML representation to the {policy} property.</p>
- <div>
<table border="1" cellspacing="0" cellpadding="5"
id="mapping-from-xml-representation-to-policy-property">
<caption>Mapping from XML representation to the {policy} property</caption>
@@ -1452,7 +1449,6 @@
</tr>
</tbody>
</table>
- </div>
</div2>
<div2 id="effective-policy">
<head>Effective Policy</head>
@@ -1481,13 +1477,13 @@
<p>The <termref def="effective_policy">effective policy</termref> of an endpoint policy subject is the <termref def="merge">merge</termref> of <termref def="policy">policies</termref>
in the {policy} properties of:</p>
<ulist>
- <item>An Endpoint component that describes the endpoint,</item>
- <item>The Binding component in the Endpoint component’s {binding} property, </item>
- <item>The Interface component in the Service component’s {interface}
- property of the Endpoint component’s {parent} property and</item>
- <item>The Interface components in the {extended interfaces} property of the
+ <item><p>An Endpoint component that describes the endpoint,</p></item>
+ <item><p>The Binding component in the Endpoint component’s {binding} property, </p></item>
+ <item><p>The Interface component in the Service component’s {interface}
+ property of the Endpoint component’s {parent} property and</p></item>
+ <item><p>The Interface components in the {extended interfaces} property of the
Interface component in the Service component’s {interface} property of
- the Endpoint component’s {parent} property.</item>
+ the Endpoint component’s {parent} property.</p></item>
</ulist>
</div3>
<div3 id="operation-policy-subject">
@@ -1496,9 +1492,9 @@
property, then the <termref def="effective_policy">effective policy</termref> of an operation policy subject <rfc2119>MAY</rfc2119> be
calculated by <termref def="merge">merging</termref> the <termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Operation component that describes the operation and</item>
- <item>The Binding Operation component (if any) whose {interface operation}
- property has the Interface Operation component.</item>
+ <item><p>The Interface Operation component that describes the operation and</p></item>
+ <item><p>The Binding Operation component (if any) whose {interface operation}
+ property has the Interface Operation component.</p></item>
</ulist>
<p>If the Binding component does not have an Interface component in the
{interface} property, then the <termref def="effective_policy">effective policy</termref> of an operation policy
@@ -1511,11 +1507,11 @@
property, then the <termref def="effective_policy">effective policy</termref> of an input message <rfc2119>MAY</rfc2119> be calculated by
<termref def="merge">merging</termref> the <termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Message Reference component that describes the input
- message and</item>
- <item>The Binding Message Reference component whose {interface message
+ <item><p>The Interface Message Reference component that describes the input
+ message and</p></item>
+ <item><p>The Binding Message Reference component whose {interface message
reference} property has the Interface Message Reference
- component.</item>
+ component.</p></item>
</ulist>
<p>If the Binding component does not have an Interface component in the
{interface} property, then the <termref def="effective_policy">effective policy</termref> of an input message <rfc2119>MUST</rfc2119> be
@@ -1529,11 +1525,11 @@
property, then the <termref def="effective_policy">effective policy</termref> of an output message <rfc2119>MAY</rfc2119> be calculated
by <termref def="merge">merging</termref> the <termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Message Reference component that describes the output
- message and</item>
- <item>The Binding Message Reference component whose {interface message
+ <item><p>The Interface Message Reference component that describes the output
+ message and</p></item>
+ <item><p>The Binding Message Reference component whose {interface message
reference} property has the Interface Message Reference
- component.</item>
+ component.</p></item>
</ulist>
<p>If the Binding component does not have an Interface component in the
{interface} property, then the effective policy of an output message <rfc2119>MUST</rfc2119> be
@@ -1547,25 +1543,25 @@
property, then the <termref def="effective_policy">effective policy</termref> of an input fault message <rfc2119>MAY</rfc2119> be
calculated by <termref def="merge">merging</termref> the <termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Fault Reference component that describes the input fault
- message, </item>
- <item>The Interface Fault component in the Interface Fault Reference
- component’s {interface fault} property, </item>
- <item>The Binding Fault Reference component whose {interface fault
- reference} property has the Interface Fault Reference component and</item>
- <item>The Binding Fault component whose {interface fault} property has the
+ <item><p>The Interface Fault Reference component that describes the input fault
+ message, </p></item>
+ <item><p>The Interface Fault component in the Interface Fault Reference
+ component’s {interface fault} property, </p></item>
+ <item><p>The Binding Fault Reference component whose {interface fault
+ reference} property has the Interface Fault Reference component and</p></item>
+ <item><p>The Binding Fault component whose {interface fault} property has the
Interface Fault component in the Interface Fault Reference component’s
- {interface fault} property.</item>
+ {interface fault} property.</p></item>
</ulist>
<p>If the Binding component does not have an Interface component in the
{interface} property, then the <termref def="effective_policy">effective policy</termref> of an input fault message
<rfc2119>MUST</rfc2119> be calculated in relation to a specific endpoint, and is the <termref def="merge">merge</termref> of
<termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Fault Reference component that describes the input fault
- message and</item>
- <item>The Interface Fault component in the Interface Fault Reference
- component’s {interface fault} property.</item>
+ <item><p>The Interface Fault Reference component that describes the input fault
+ message and</p></item>
+ <item><p>The Interface Fault component in the Interface Fault Reference
+ component’s {interface fault} property.</p></item>
</ulist>
</div3>
<div3 id="message-policy-subject-output-fault">
@@ -1574,25 +1570,25 @@
property, then the <termref def="effective_policy">effective policy</termref> of an output fault message <rfc2119>MAY</rfc2119> be
calculated by <termref def="merge">merging</termref> the <termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Fault Reference component that describes the output
- fault message,</item>
- <item>The Interface Fault component in the Interface Fault Reference
- component’s {interface fault} property, </item>
- <item>The Binding Fault Reference component whose {interface fault
- reference} property has the Interface Fault Reference component and</item>
- <item>The Binding Fault component whose {interface fault} property has the
+ <item><p>The Interface Fault Reference component that describes the output
+ fault message,</p></item>
+ <item><p>The Interface Fault component in the Interface Fault Reference
+ component’s {interface fault} property, </p></item>
+ <item><p>The Binding Fault Reference component whose {interface fault
+ reference} property has the Interface Fault Reference component and</p></item>
+ <item><p>The Binding Fault component whose {interface fault} property has the
Interface Fault component in the Interface Fault Reference component’s
- {interface fault} property for the endpoint.</item>
+ {interface fault} property for the endpoint.</p></item>
</ulist>
<p>If the Binding component does not have an Interface component in the
{interface} property, then the <termref def="effective_policy">effective policy</termref> of an output fault message
<rfc2119>MUST</rfc2119> be calculated in relation to a specific endpoint, and is the <termref def="merge">merge</termref> of
<termref def="policy">policies</termref> in the {policy} properties of:</p>
<ulist>
- <item>The Interface Fault Reference component that describes the output
- fault message and</item>
- <item>The Interface Fault component in the Interface Fault Reference
- component’s {interface fault} property.</item>
+ <item><p>The Interface Fault Reference component that describes the output
+ fault message and</p></item>
+ <item><p>The Interface Fault component in the Interface Fault Reference
+ component’s {interface fault} property.</p></item>
</ulist>
</div3>
</div2>
Received on Monday, 2 October 2006 02:33:43 UTC