- From: Maryann Hondo via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 15 Nov 2006 16:46:18 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv24120
Modified Files:
ws-policy-guidelines.xml
Log Message:
first pass at updating as per editor action item 77
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- ws-policy-guidelines.xml 1 Nov 2006 02:40:25 -0000 1.10
+++ ws-policy-guidelines.xml 15 Nov 2006 16:46:15 -0000 1.11
@@ -62,333 +62,398 @@
</revisiondesc>
</header>
<body>
- <div1 id="introduction">
- <head>Introduction</head>
+ <div1 id="introduction">
+ <head>Introduction</head>
- <p>WS-Policy specification defines a policy to be a collection
- of policy alternatives, where each policy alternative is a
- collection of policy assertions. <emph>&guideline.title;</emph>
[...1336 lines suppressed...]
- interaction will be <emph>undefined</emph>. For example,
+ <item> <p>When optional behaviors are indicated by attaching assertions with only
+ one side of an interaction, such as an inbound message of
+ a request-response, the engagement of the rest of the
+ interaction will be <emph>undefined</emph>. For example,
if a request-response interaction only specified MTOM
optimization for an inbound message, it would not be clear
whether the outbound message from the provider could also
@@ -1642,6 +1710,11 @@
<td>UY</td>
<td>Optionality discussion feedback integration</td>
</tr>
+ <tr>
+ <td>20061115</td>
+ <td>MH</td>
+ <td>First attempt at restructuring to include primer content</td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Wednesday, 15 November 2006 16:58:56 UTC