- From: Umit Yalsinap via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 19 Oct 2006 23:52:54 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv31624
Modified Files:
ws-policy-guidelines.xml
Log Message:
fixed xml issues (wellformed/valid)
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- ws-policy-guidelines.xml 18 Oct 2006 21:25:06 -0000 1.5
+++ ws-policy-guidelines.xml 19 Oct 2006 23:52:51 -0000 1.6
@@ -625,18 +625,16 @@
delegated to the specific domain handlers that are not visible
to the WS-Policy framework. The tradeoff is the generality
vs. the flexibility and complexity of the comparison expected
- for a domain.
+ for a domain. </p>
<p>In the example below, <code>sp:Body</code> and <code>sp:Header</code> elements are the
two assertion parameters of the <code>sp:SignedParts</code> policy assertion (this
assertion requires the parts of a message to be protected). </p>
- </p> <head>Policy Assertion with Assertion Parameters</head>
- <example>
+ <example> <head>Policy Assertion with Assertion Parameters</head>
<eg xml:space="preserve"><Policy>
<sp:SignedParts>
<sp:Body />
<sp:Header />
</sp:SignedParts>
- …
</Policy></eg>
</example>
@@ -900,8 +898,7 @@
the assertion reasonably applies to any endpoint that ever
references that portType. Most of the known policy assertions
are designed for the endpoint, operation or message policy
- subject. The commonly used attachment points for these policy
- subjects are outlined in <specref ref="subject-scoping-considerations"/>. </p>
+ subject. </p>
<p> In using WSDL attachment, it should be noted that the
service policy subject is a collection of endpoint policy
subjects. The endpoint policy subject is a collection of
Received on Thursday, 19 October 2006 23:52:56 UTC