W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > October 2009

WWW/2002/ws/ra/edcopies wsenum.html,1.75,1.76 wsenum.xml,1.68,1.69 wseventing.html,1.105,1.106 wseventing.xml,1.97,1.98 wsfrag.html,1.26,1.27 wsfrag.xml,1.27,1.28 wsmex.html,1.69,1.70 wsmex.xml,1.59,1.60 wst.html,1.76,1.77 wst.xml,1.74,1.75

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 20 Oct 2009 23:59:23 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1N0Obs-0000Jb-1J@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1119

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsfrag.html wsfrag.xml wsmex.html wsmex.xml wst.html wst.xml 
Log Message:
7207


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -d -r1.74 -r1.75
--- wst.xml	20 Oct 2009 23:18:30 -0000	1.74
+++ wst.xml	20 Oct 2009 23:59:21 -0000	1.75
@@ -465,6 +465,14 @@
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
     </p>
+
+    <p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p>
         
     <p>
      A compliant SOAP Node that implements a resource MUST
@@ -671,7 +679,7 @@
         <p>
          Unless otherwise specified by an extension, this operation will 
          replace the entire XML representation of the 
-         resource, and any optional values (elements or attributes) not 
+         resource, and any OPTIONAL values (elements or attributes) not 
          specified in the Put request message will be set to a 
          resource-specific default value.
         </p>
@@ -1440,7 +1448,7 @@
             </tr>
             <tr>
               <th align="left"><kw>[Detail]</kw></th>
-              <td><emph>An optional list of the QNames of the elements or 
+              <td><emph>An OPTIONAL list of the QNames of the elements or 
               attributes that are not allowed to be updated.</emph></td>
             </tr>
           </tbody>
@@ -1621,7 +1629,7 @@
      In order to indicate that the subject supports WS-Transfer
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -1656,7 +1664,7 @@
          This policy assertion specifies that WS-Transfer protocol MUST be 
          used when communicating with this endpoint and that the subject is a 
          Transfer Resource. This assertion has Endpoint Policy Subject.  Unless 
-         support for optional operations is explicitly indicated by either 
+         support for OPTIONAL operations is explicitly indicated by either 
          the PutOperationSupported or DeleteOperationSupported parameters only 
          the Get operation is supported.
         </p>
@@ -1760,7 +1768,7 @@
      In order to indicate that the subject supports WS-Transfer
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -2578,6 +2586,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7968">7968</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -d -r1.105 -r1.106
--- wseventing.html	20 Oct 2009 23:25:53 -0000	1.105
+++ wseventing.html	20 Oct 2009 23:59:21 -0000	1.106
@@ -75,22 +75,22 @@
 &nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br/>
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
 9 <a href="#metadata">WS-Eventing Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2175">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2242">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2177">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2244">SubscriptionManager Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2313">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2434">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2315">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2436">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2740">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2756">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2761">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2779">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2742">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2758">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2763">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2781">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2806">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2822">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2808">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2824">Multiple Event Information Metadata Sections</a><br/>
 B <a href="#Schema">XML Schema</a><br/>
 C <a href="#WSDL">WSDL</a><br/>
 D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -450,6 +450,12 @@
     </p><p>
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
+    </p><p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
     </p></div></div><div class="div1">
 <h2><a name="SubMsgs" id="SubMsgs"/>4 Subscription Messages</h2><p>
     To create, renew, and delete subscriptions, subscribers send
@@ -521,7 +527,7 @@
         that notifications MUST be sent to the EndpointReference identified 
         by this element.
        </p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Format </dt><dd><p>
-        This optional element contains
+        This OPTIONAL element contains
         the delivery format to be used for notification messages sent in 
         relation to this subscription. Implied value is 
         "http://www.w3.org/2009/09/ws-evt/DeliveryFormats/Unwrap", which 
@@ -1153,7 +1159,7 @@
         This value MUST be used if the event source terminated the
         subscription for some other reason before it expired.
        </p></dd><dt class="label"><b>[Body]</b>/wse:SubscriptionEnd/wse:Reason </dt><dd><p>
-        This optional element contains text, in the language
+        This OPTIONAL element contains text, in the language
         specified by the @xml:lang attribute, describing the reason
         for the unexpected subscription termination.
        </p></dd></dl><p>
@@ -1310,7 +1316,7 @@
         minimum duration in milliseconds to wait before retransmitting the message. 
         Omission of this element indicates that a retry is never likely to succeed.
        </p></dd><dt class="label"> /wse:RetryAfter/@any</dt><dd><p>
-        Optional extensibility attributes that do not affect processing.
+        OPTIONAL extensibility attributes that do not affect processing.
        </p></dd></dl></div><div class="div2">
 <h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>6.2 InvalidExpirationTime</h3><p>
      This fault is generated when a request specifies an
@@ -1332,21 +1338,21 @@
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
 <h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"/>6.6 FilteringRequestedUnavailable</h3><p>
      This fault is generated when a Subscribe request specifies a filter
-     dialect that the event source does not support. Optionally, this
+     dialect that the event source does not support. OPTIONALLY, this
      fault MAY contain a list of supported filter dialect IRIs in the
      Detail property.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested filter dialect is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDialect&gt; + 
-        <br/><em>Optional; one per filter dialect supported by the
+        <br/><em>OPTIONAL; one per filter dialect supported by the
         receiver</em></td></tr></tbody></table></div><div class="div2">
 <h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.7 DeliveryFormatRequestUnavailable</h3><p>
      This fault is generated when a Subscribe request specifies a delivery 
-     format that is not supported by the event source. Optionally, this 
+     format that is not supported by the event source. OPTIONALLY, this 
      fault MAY contain a list of supported delivery format IRIs in the 
      Detail property.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDeliveryFormat&gt; +
-        <br/><em> Optional, one per delivery format supported by the receiver.</em></td></tr></tbody></table></div><div class="div2">
+        <br/><em> OPTIONAL, one per delivery format supported by the receiver.</em></td></tr></tbody></table></div><div class="div2">
 <h3><a name="EmptyFilter" id="EmptyFilter"/>6.8 EmptyFilter</h3><p>
      This fault MAY be generated when an Event Source detects a 
      wse:Subscribe request containing a filter that, for whatever 
@@ -1430,7 +1436,7 @@
        for a variety of reasons. To detect and eliminate this
        attack, mechanisms SHOULD be used to identify replayed
        messages such as the timestamp/nonce outlined in WS-Security.
-       Alternatively, and optionally, other technologies, such as
+       Alternatively, and OPTIONALLY, other technologies, such as
        sequencing, can also be used to prevent replay of application
        messages.
       </p></li></ul></div><div class="div2">
@@ -1489,7 +1495,7 @@
     indicate a particular security mechanism used to protect the
     WS-Eventing operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_2175" id="iddiv2_1_2175"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2177" id="iddiv2_1_2177"/>9.1 EventSource Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Eventing specification's definition of an Event Source 
      is through the use of the Web Services
@@ -1513,7 +1519,7 @@
      In order to indicate that the subject supports WS-Eventing
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -1547,7 +1553,7 @@
          When present, this OPTIONAL parameter indicates support for the 
          specified event delivery format Name URI.
         </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2242" id="iddiv2_1_2242"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2244" id="iddiv2_1_2244"/>9.2 SubscriptionManager Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Eventing specification's definition of a Subscription Manager 
      is through the use of the Web Services
@@ -1573,7 +1579,7 @@
      In order to indicate that the subject supports WS-Eventing
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -1631,7 +1637,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2313" id="iddiv2_1_2313"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2315" id="iddiv2_1_2315"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1678,7 +1684,7 @@
        , A. Vedamuthu, et al., Editors.
        World Wide Web Consortium (W3C), 4 September 2007.
       Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2434" id="iddiv2_1_2434"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2436" id="iddiv2_1_2436"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
         OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
         Web Services Make Connection (WS-MakeConnection)
        </cite></a>
@@ -1764,7 +1770,7 @@
     There are many ways in which an Event Source could describe and 
     advertise the structure of the Events for which it will issue 
     Notifications. To provide a basic level of interoperability, this 
-    specification defines the following two optional mechanisms, in 
+    specification defines the following two OPTIONAL mechanisms, in 
     <a href="#ETypes"><b>A.1 Event Types &amp; Event Descriptions</b></a> and <a href="#NWSDL"><b>A.2 Notification WSDLs</b></a>, for describing and 
     advertising Event information. If an implementation of a WS-Eventing 
     Event Source chooses to describe the structure of its Events and 
@@ -1856,7 +1862,7 @@
         /wse:EventDescriptions/wse:types element. The referenced GED 
         serves as the definition of this Event Type.
        </p></dd><dt class="label"> /wse:EventDescriptions/wse:eventType/@actionURI </dt><dd><p>
-        This optional attribute provides a value for the various 'action' 
+        This OPTIONAL attribute provides a value for the various 'action' 
         properties and attributes which, depending upon the format of the 
         Notification used to transmit the Event, serve as a potential aide 
         to identifying the semantics implied by the message. When not 
@@ -1868,7 +1874,7 @@
      serve as a description of the Event Type used in 
      <a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>. 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2730" id="idexample_1_2730"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2732" id="idexample_1_2732"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2009/09/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1888,7 +1894,7 @@
      GED for this Event Type is defined on line (08) as being of type 
      "{http://www.example.org/oceanwatch}:WindReportType". 
     </p><div class="div3">
-<h4><a name="iddiv3_1_2740" id="iddiv3_1_2740"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2742" id="iddiv3_1_2742"/>A.1.1 Retrieving Event Descriptions</h4><p>
       Although there are many ways in which an Event Source can make its 
       EventDescriptions available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1899,7 +1905,7 @@
       be equal to the value of its wse:EventDescriptions/@targetNamespace. An 
       Event Source MUST NOT have more than one EventDescriptions document.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_2756" id="iddiv3_1_2756"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2758" id="iddiv3_1_2758"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it SHOULD be possible to determine how a 
       given wse:eventType will appear on the wire as a Notification in a 
       Subscription created with that format. The following sections define 
@@ -1911,7 +1917,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the Notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4_1_2761" id="iddiv4_1_2761"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2763" id="iddiv4_1_2763"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wse:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1925,7 +1931,7 @@
          of the wse:eventType element corresponding to the type of the 
          Event being transmitted.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2779" id="iddiv4_1_2779"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2781" id="iddiv4_1_2781"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
        The information about an Event Type contained in the eventType element 
        binds to a Wrapped Notification for that type as follows: 
       </p><ul><li><p>
@@ -1949,7 +1955,7 @@
      successful Subscribe request that used a particular Format IRI. The 
      following is an example of a Notification WSDL: 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2800" id="idexample_1_2800"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2802" id="idexample_1_2802"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 (02)                   targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)                   xmlns:xs="http://www.w3.org/2001/XMLSchema"
 (04)                   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1984,7 +1990,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2806" id="iddiv3_1_2806"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2808" id="iddiv3_1_2808"/>A.2.1 Retrieving Notification WSDLs</h4><p>
       Although there are many ways in which an Event Source can make 
       Notification WSDLs available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -2000,7 +2006,7 @@
       Format IRI/@Identifier, there MUST NOT exist more than one 
       Notification WSDL document. 
      </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2822" id="iddiv2_1_2822"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2824" id="iddiv2_1_2824"/>A.3 Multiple Event Information Metadata Sections</h3><p>
      When WS-MetadataExchange is used to retrieve metadata about an Event 
      Source, recipients of mex:Metadata elements that contain Metadata 
      Sections with both the 
@@ -2597,4 +2603,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7982">7982</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- wsfrag.xml	20 Oct 2009 23:16:40 -0000	1.27
+++ wsfrag.xml	20 Oct 2009 23:59:21 -0000	1.28
@@ -476,6 +476,14 @@
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
     </p>
+
+    <p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p>
         
    </div2>
   </div1>
@@ -1661,7 +1669,7 @@
      In order to indicate that the subject supports WS-Fragment
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -2083,6 +2091,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -d -r1.26 -r1.27
--- wsfrag.html	20 Oct 2009 23:16:40 -0000	1.26
+++ wsfrag.html	20 Oct 2009 23:59:21 -0000	1.27
@@ -53,8 +53,8 @@
 &nbsp;&nbsp;&nbsp;3.2 <a href="#Put">Put</a><br/>
 &nbsp;&nbsp;&nbsp;3.3 <a href="#Delete">Delete</a><br/>
 &nbsp;&nbsp;&nbsp;3.4 <a href="#Create">Create</a><br/>
-4 <a href="#iddiv1_1_788">Examples</a><br/>
-&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_791">Examples</a><br/>
+4 <a href="#iddiv1_1_790">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_793">Examples</a><br/>
 5 <a href="#QName">QName Expression Language</a><br/>
 6 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
 7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
@@ -64,10 +64,10 @@
 &nbsp;&nbsp;&nbsp;8.3 <a href="#InvalidExpression">InvalidExpression</a><br/>
 &nbsp;&nbsp;&nbsp;8.4 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
 9 <a href="#metadata">WS-Fragment Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1453">Fragment Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1455">Fragment Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1506">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1508">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#policyXSD">Fragment Policy Schema</a><br/>
@@ -237,6 +237,12 @@
     </p><p>
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
+    </p><p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
     </p></div></div><div class="div1">
 <h2><a name="fragments" id="fragments"/>3 Fragment WS-Transfer Dialect</h2><p>
     This section defines the fragment transfer mechanism that the expression
@@ -409,8 +415,8 @@
      This specification does not extend the Create operation defined in
      WS-Transfer.
     </p></div></div><div class="div1">
-<h2><a name="iddiv1_1_788" id="iddiv1_1_788"/>4 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_791" id="iddiv2_1_791"/>4.1 Examples</h3><p>
+<h2><a name="iddiv1_1_790" id="iddiv1_1_790"/>4 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_793" id="iddiv2_1_793"/>4.1 Examples</h3><p>
      In the following examples, and Expression Language definitions,
      the following representation of a resource is used for
      informational purposes:
@@ -834,7 +840,7 @@
     doing so the endpoint is indicating that the corresponding WS-Fragment
     features are supported by that endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1453" id="iddiv2_1_1453"/>9.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2_1_1455" id="iddiv2_1_1455"/>9.1 Fragment Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Fragment specification is through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -857,7 +863,7 @@
      In order to indicate that the subject supports WS-Fragment
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -901,7 +907,7 @@
      Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1506" id="iddiv2_1_1506"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1508" id="iddiv2_1_1508"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1067,4 +1073,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a></td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6407">6407</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -d -r1.76 -r1.77
--- wst.html	20 Oct 2009 23:18:29 -0000	1.76
+++ wst.html	20 Oct 2009 23:59:21 -0000	1.77
@@ -58,12 +58,12 @@
 &nbsp;&nbsp;&nbsp;5.3 <a href="#PutDenied">PutDenied</a><br/>
 6 <a href="#Security_Considerations">Security Considerations</a><br/>
 7 <a href="#metadata">WS-Transfer Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2_1_1377">TransferResource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1447">TransferResourceFactory Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2_1_1379">TransferResource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1449">TransferResourceFactory Assertion</a><br/>
 8 <a href="#acks">Acknowledgements</a><br/>
 9 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1500">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1673">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1502">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1675">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -236,6 +236,12 @@
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
     </p><p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p><p>
      A compliant SOAP Node that implements a resource MUST
      provide the Get operation as defined in this specification, and MAY provide
      the Put and Delete operations.
@@ -366,7 +372,7 @@
         </p><p>
          Unless otherwise specified by an extension, this operation will 
          replace the entire XML representation of the 
-         resource, and any optional values (elements or attributes) not 
+         resource, and any OPTIONAL values (elements or attributes) not 
          specified in the Put request message will be set to a 
          resource-specific default value.
         </p><p>
@@ -824,7 +830,7 @@
          to modify a portion of a resource but is not allowed to do so.
         </p><a name="Table4" id="Table4"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UpdateDenied</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
                 One or more elements or attributes cannot be updated.
-              </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>An optional list of the QNames of the elements or 
+              </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>An OPTIONAL list of the QNames of the elements or 
               attributes that are not allowed to be updated.</em></td></tr></tbody></table></div></div><div class="div1">
 <h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>It is strongly RECOMMENDED that the communication between services be
     secured using the mechanisms described in <a href="#WSSecurity">[WS-Security]</a>.</p><p>In order to properly secure messages, the body (even if empty) and all
@@ -894,7 +900,7 @@
     indicate a particular security mechanism used to protect the
     WS-Transfer operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1377" id="iddiv2_1_1377"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1379" id="iddiv2_1_1379"/>7.1 TransferResource Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Transfer specification's definition of a Transfer Resource
      is through the use of the Web Services
@@ -919,7 +925,7 @@
      In order to indicate that the subject supports WS-Transfer
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -939,7 +945,7 @@
          This policy assertion specifies that WS-Transfer protocol MUST be 
          used when communicating with this endpoint and that the subject is a 
          Transfer Resource. This assertion has Endpoint Policy Subject.  Unless 
-         support for optional operations is explicitly indicated by either 
+         support for OPTIONAL operations is explicitly indicated by either 
          the PutOperationSupported or DeleteOperationSupported parameters only 
          the Get operation is supported.
         </p></dd><dt class="label"> /wstrp:TransferResource/wstrp:PutOperationSupported </dt><dd><p>
@@ -962,7 +968,7 @@
          the Global Element Declaration (GED) or type of this resource.  This 
          QName may be used in order to retrieve the schema of the resource.
         </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1447" id="iddiv2_1_1447"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1449" id="iddiv2_1_1449"/>7.2 TransferResourceFactory Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Transfer specification's definition of a Transfer Resource Factory
      is through the use of the Web Services
@@ -990,7 +996,7 @@
      In order to indicate that the subject supports WS-Transfer
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -1034,7 +1040,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1500" id="iddiv2_1_1500"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1502" id="iddiv2_1_1502"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1102,7 +1108,7 @@
        , P. Biron, A. Malhotra, Editors.
        World Wide Web Consortium (W3C), 28 October 2004.
       Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1673" id="iddiv2_1_1673"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1675" id="iddiv2_1_1675"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
        W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
       </cite></a>
       , D. Davis, et al., Editors.
@@ -1422,4 +1428,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7812">7812</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7968">7968</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7968">7968</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -d -r1.59 -r1.60
--- wsmex.xml	20 Oct 2009 23:16:40 -0000	1.59
+++ wsmex.xml	20 Oct 2009 23:59:21 -0000	1.60
@@ -120,7 +120,7 @@
     To bootstrap communication with Web services this specification defines 
     how metadata can be treated as <bibref ref='WS-Transfer'/> resources 
     for retrieval purposes, how metadata can be embedded in Web service 
-    endpoint references, and how Web service endpoints can optionally 
+    endpoint references, and how Web service endpoints can OPTIONALLY 
     support a request-response interaction for the retrieval of metadata.
     When the type of metadata sought is clearly known, e.g., 
     <bibref ref='wspolicy'/>, a requester MAY indicate that only that 
@@ -162,7 +162,7 @@
 
      <item>
       <p>
-       Define an optional bootstrap mechanism for metadata-driven 
+       Define an OPTIONAL bootstrap mechanism for metadata-driven 
        <bibref ref='XMLSchema1'/>, <bibref ref='WSDL11'/>, 
        <bibref ref='wspolicy'/> message exchange.
       </p>
@@ -196,7 +196,7 @@
 
      <item>
       <p>
-       Enable description in <bibref ref='WSDL11'/> of the optional 
+       Enable description in <bibref ref='WSDL11'/> of the OPTIONAL 
        request-response interaction.
       </p>
      </item>
@@ -725,10 +725,18 @@
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
     </p>
+
+    <p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p>
     
     <p>
      Support for the GetMetadata operation by a Web service is 
-     optional. If metadata about a Web service endpoint is referenced by 
+     OPTIONAL. If metadata about a Web service endpoint is referenced by 
      a Metadata Reference, which is a 
      <bibref ref='AddrCore'/> endpoint reference, then the Metadata 
      Reference MUST refer to a <bibref ref='WS-Transfer'/> resource. 
@@ -794,7 +802,7 @@
    
    <p>
     To facilitate processing, Metadata Sections are tagged with a 
-    @Dialect and (optionally) @Identifier of the metadata unit. To ensure 
+    @Dialect and (OPTIONALLY) @Identifier of the metadata unit. To ensure 
     scalability, a unit of metadata MAY be included in-line within its 
     Metadata Section or MAY be included by reference, either an endpoint 
     reference <bibref ref='AddrCore'/> 
@@ -1598,7 +1606,7 @@
       <kw>Replay</kw> - Messages can be replayed for a variety of 
       reasons. To detect and eliminate this attack, mechanisms SHOULD 
       be used to identify replayed messages such as the timestamp/nonce 
-      outlined in WS-Security. Alternatively, and optionally, other 
+      outlined in WS-Security. Alternatively, and OPTIONALLY, other 
       technologies, such as sequencing, can also be used to prevent 
       replay of application messages.
      </p>
@@ -1682,7 +1690,7 @@
      In order to indicate that the subject supports WS-MetadataExchange
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -2421,6 +2429,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- wsenum.html	20 Oct 2009 23:34:04 -0000	1.75
+++ wsenum.html	20 Oct 2009 23:59:21 -0000	1.76
@@ -67,11 +67,11 @@
 &nbsp;&nbsp;&nbsp;4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
 5 <a href="#Security">Security Considerations</a><br/>
 6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1941">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1943">Enumeration Assertion</a><br/>
 7 <a href="#acks">Acknowledgements</a><br/>
 8 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2030">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2216">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2032">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2218">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
 B <a href="#WSDL">WSDL</a><br/>
@@ -301,6 +301,12 @@
      </p><p>
       Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison 
       MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
+     </p><p>
+      For any message defined by this specification, any OPTIONAL elements 
+      or attributes in the message MAY be used by senders of the message, 
+      however receivers of those messages MUST understand those OPTIONAL 
+      elements and attributes, unless other behavior is explicitly defined 
+      by this specification.
      </p></div></div><div class="div1">
 <h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
     Enumeration contexts represent a specific
@@ -370,7 +376,7 @@
      The following describes additional, normative
      constraints on the outline listed above:
     </p><dl><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:EndTo </dt><dd><p>
-        This optional element denotes where to send
+        This OPTIONAL element denotes where to send
         an EnumerationEnd message if the enumeration is terminated
         unexpectedly 
         (see <a href="#EnumerationEnd"><b>3.6 EnumerationEnd</b></a>). 
@@ -403,7 +409,7 @@
         attributes MUST be ignored and are treated as if they had the same
         value as the wsen:Expires element.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Filter </dt><dd><p>
-        This optional element contains a Boolean
+        This OPTIONAL element contains a Boolean
         predicate in some dialect (see <b>[<a href="#Dialect">[Body]/wsen:Enumerate/wsen:Filter/@Dialect </a>]</b>) 
         that all elements of
         interest MUST satisfy. The resultant enumeration context MUST NOT
@@ -615,7 +621,7 @@
         enumeration context and refreshed on every
         PullResponse.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxTime </dt><dd><p>
-        This optional element (of type xs:duration)
+        This OPTIONAL element (of type xs:duration)
         indicates the maximum amount of time the initiator is willing to
         allow the data source to assemble the Pull response. When this
         element is absent, the data source is not required to limit the
@@ -626,7 +632,7 @@
         accumulate elements over time and package them into a single Pull
         response.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxElements </dt><dd><p>
-        This optional element (of type xs:long)
+        This OPTIONAL element (of type xs:long)
         indicates the number of items (child elements of wsen:Items in the
         Pull response) the consumer is willing to accept. When this element
         is absent, its implied value is 1. Implementations MUST NOT return
@@ -635,7 +641,7 @@
         the wsen:MaxTime timeout, the wsen:MaxCharacters size limit, or
         implementation-specific constraints.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxCharacters </dt><dd><p>
-        This optional element (of type xs:long)
+        This OPTIONAL element (of type xs:long)
         indicates the maximum size of the returned elements, in Unicode
         characters, that the initiator is willing to accept. When this
         element is absent, the data source is not required to limit the
@@ -700,16 +706,16 @@
      constraints on the outline listed above:
     </p><dl><dt class="label"><b>[Body]</b>/wsen:PullResponse/wsen:EnumerationContext 
       </dt><dd><p>
-        The optional EnumerationContext element, if
+        The OPTIONAL EnumerationContext element, if
         present, contains a new XML representation of the current
         enumeration context. The consumer is required to replace the prior
         representation with the contents of this element.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:PullResponse/wsen:Items/<em>xs:any</em></dt><dd><p>
-        The optional Items element contains one or
+        The OPTIONAL Items element contains one or
         more enumeration-specific elements, one for each element being
         returned. 
        </p></dd><dt class="label"><b>[Body]</b>/wsen:PullResponse/wsen:EndOfSequence </dt><dd><p>
-        This optional element indicates that no more
+        This OPTIONAL element indicates that no more
         elements are available from this enumeration. Additionally, once
         this element is returned in a Pull response message, subsequent
         Pull requests using that enumeration context MUST generate a
@@ -868,7 +874,7 @@
         source starts processing the Renew request.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:RenewResponse/wsen:EnumerationContext
       </dt><dd><p>
-        This element is optional in this response.
+        This element is OPTIONAL in this response.
        </p></dd></dl><p>
      If the data source chooses not to renew this enumeration, the request
      MUST fail, and the data source MUST generate a SOAP 1.1 Server fault
@@ -1040,7 +1046,7 @@
         terminated the enumeration for some other reason before it
         expired.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:EnumerationEnd/wsen:Reason </dt><dd><p>
-        This optional element contains text, in the
+        This OPTIONAL element contains text, in the
         language specified by the @xml:lang attribute, describing the
         reason for the unexpected enumeration termination.
        </p></dd></dl><p>
@@ -1126,7 +1132,7 @@
         Filer dialect requested unavailable.
        </td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wsen:SupportedDialect&gt; +
-        <br/><em>Optional; repeating; one per filter dialect supported by the
+        <br/><em>OPTIONAL; repeating; one per filter dialect supported by the
         receiver</em></td></tr></tbody></table></div><div class="div2">
 <h3><a name="CannotProcessFilter" id="CannotProcessFilter"/>4.6 CannotProcessFilter</h3><p>
      This fault is generated if the data source can not process the
@@ -1261,7 +1267,7 @@
     indicate a particular security mechanism used to protect the 
     WS-Enumeration operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1941" id="iddiv2_1_1941"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1943" id="iddiv2_1_1943"/>6.1 Enumeration Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the 
      WS-Enumeration specification is through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1284,7 +1290,7 @@
      In order to indicate that the subject supports WS-Enumeration 
      but does not require its use, an additional policy alternative should 
      be provided which does not contain this assertion. The compact 
-     authoring style for an optional policy assertion (the wsp:Optional 
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional 
      attribute) provided by WS-Policy may be used to indicate two policy 
      alternatives, one which contains the policy assertion, and another 
      which does not. 
@@ -1350,7 +1356,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2030" id="iddiv2_1_2030"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2032" id="iddiv2_1_2032"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author. 
@@ -1422,7 +1428,7 @@
        , J. Clark, S. DeRose, Editors.
        World Wide Web Consortium (W3C), 16 November 1999. 
       Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2216" id="iddiv2_1_2216"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_2218" id="iddiv2_1_2218"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
         OASIS Standard, "Web Services Secure Conversation 
           (WS-SecureConversation) 1.4"
        </cite></a>
@@ -1916,4 +1922,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7587">7587</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7811">7811</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7811">7811</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- wsenum.xml	20 Oct 2009 23:34:04 -0000	1.68
+++ wsenum.xml	20 Oct 2009 23:59:21 -0000	1.69
@@ -535,6 +535,14 @@
       Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison 
       MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
      </p>
+
+     <p>
+      For any message defined by this specification, any OPTIONAL elements 
+      or attributes in the message MAY be used by senders of the message, 
+      however receivers of those messages MUST understand those OPTIONAL 
+      elements and attributes, unless other behavior is explicitly defined 
+      by this specification.
+     </p>
      
     </div2>
 
@@ -632,7 +640,7 @@
       <label> <kw>[Body]</kw>/wsen:Enumerate/wsen:EndTo </label>
       <def>
        <p>
-        This optional element denotes where to send
+        This OPTIONAL element denotes where to send
         an EnumerationEnd message if the enumeration is terminated
         unexpectedly 
         (see <specref ref="EnumerationEnd"/>). 
@@ -703,7 +711,7 @@
       <label> <kw>[Body]</kw>/wsen:Enumerate/wsen:Filter </label>
       <def>
        <p>
-        This optional element contains a Boolean
+        This OPTIONAL element contains a Boolean
         predicate in some dialect (see <specref ref="Dialect"/>) 
         that all elements of
         interest MUST satisfy. The resultant enumeration context MUST NOT
@@ -1054,7 +1062,7 @@
       <label> <kw>[Body]</kw>/wsen:Pull/wsen:MaxTime </label>
       <def>
        <p>
-        This optional element (of type xs:duration)
+        This OPTIONAL element (of type xs:duration)
         indicates the maximum amount of time the initiator is willing to
         allow the data source to assemble the Pull response. When this
         element is absent, the data source is not required to limit the
@@ -1073,7 +1081,7 @@
       <label> <kw>[Body]</kw>/wsen:Pull/wsen:MaxElements </label>
       <def>
        <p>
-        This optional element (of type xs:long)
+        This OPTIONAL element (of type xs:long)
         indicates the number of items (child elements of wsen:Items in the
         Pull response) the consumer is willing to accept. When this element
         is absent, its implied value is 1. Implementations MUST NOT return
@@ -1089,7 +1097,7 @@
       <label> <kw>[Body]</kw>/wsen:Pull/wsen:MaxCharacters </label>
       <def>
        <p>
-        This optional element (of type xs:long)
+        This OPTIONAL element (of type xs:long)
         indicates the maximum size of the returned elements, in Unicode
         characters, that the initiator is willing to accept. When this
         element is absent, the data source is not required to limit the
@@ -1180,7 +1188,7 @@
       </label>
       <def>
        <p>
-        The optional EnumerationContext element, if
+        The OPTIONAL EnumerationContext element, if
         present, contains a new XML representation of the current
         enumeration context. The consumer is required to replace the prior
         representation with the contents of this element.
@@ -1194,7 +1202,7 @@
       </label>
       <def>
        <p>
-        The optional Items element contains one or
+        The OPTIONAL Items element contains one or
         more enumeration-specific elements, one for each element being
         returned. 
        </p>
@@ -1205,7 +1213,7 @@
       <label> <kw>[Body]</kw>/wsen:PullResponse/wsen:EndOfSequence </label>
       <def>
        <p>
-        This optional element indicates that no more
+        This OPTIONAL element indicates that no more
         elements are available from this enumeration. Additionally, once
         this element is returned in a Pull response message, subsequent
         Pull requests using that enumeration context MUST generate a
@@ -1440,7 +1448,7 @@
       </label>
       <def>
        <p>
-        This element is optional in this response.
+        This element is OPTIONAL in this response.
        </p>
       </def>
      </gitem>
@@ -1731,7 +1739,7 @@
       <label> <kw>[Body]</kw>/wsen:EnumerationEnd/wsen:Reason </label>
       <def>
        <p>
-        This optional element contains text, in the
+        This OPTIONAL element contains text, in the
         language specified by the @xml:lang attribute, describing the
         reason for the unexpected enumeration termination.
        </p>
@@ -1996,7 +2004,7 @@
        <td>
         &lt;wsen:SupportedDialect&gt; +
         <phrase/>
-        <emph>Optional; repeating; one per filter dialect supported by the
+        <emph>OPTIONAL; repeating; one per filter dialect supported by the
         receiver</emph>
        </td>
       </tr>
@@ -2362,7 +2370,7 @@
      In order to indicate that the subject supports WS-Enumeration 
      but does not require its use, an additional policy alternative should 
      be provided which does not contain this assertion. The compact 
-     authoring style for an optional policy assertion (the wsp:Optional 
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional 
      attribute) provided by WS-Policy may be used to indicate two policy 
      alternatives, one which contains the policy assertion, and another 
      which does not. 
@@ -3438,6 +3446,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7811">7811</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- wsmex.html	20 Oct 2009 23:16:40 -0000	1.69
+++ wsmex.html	20 Oct 2009 23:59:21 -0000	1.70
@@ -60,11 +60,11 @@
 8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
 9 <a href="#Security">Security Considerations</a><br/>
 10 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1418">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1420">MetadataExchange Assertion</a><br/>
 11 <a href="#Acknowledgements">Acknowledgements</a><br/>
 12 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1482">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1655">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1484">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1657">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
 B <a href="#Appendix-B">WSDL</a><br/>
@@ -91,7 +91,7 @@
     To bootstrap communication with Web services this specification defines 
     how metadata can be treated as <a href="#WS-Transfer">[WS-Transfer]</a> resources 
     for retrieval purposes, how metadata can be embedded in Web service 
-    endpoint references, and how Web service endpoints can optionally 
+    endpoint references, and how Web service endpoints can OPTIONALLY 
     support a request-response interaction for the retrieval of metadata.
     When the type of metadata sought is clearly known, e.g., 
     <a href="#wspolicy">[WS-Policy]</a>, a requester MAY indicate that only that 
@@ -115,7 +115,7 @@
        Treat the metadata about a Web service endpoint as 
        <a href="#WS-Transfer">[WS-Transfer]</a> resources.
       </p></li><li><p>
-       Define an optional bootstrap mechanism for metadata-driven 
+       Define an OPTIONAL bootstrap mechanism for metadata-driven 
        <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#WSDL11">[WSDL11]</a>, 
        <a href="#wspolicy">[WS-Policy]</a> message exchange.
       </p></li><li><p>
@@ -129,7 +129,7 @@
        Support both <a href="#SOAP11">[SOAP11]</a> and <a href="#SOAP121">[SOAP12]</a> 
        Envelopes.
       </p></li><li><p>
-       Enable description in <a href="#WSDL11">[WSDL11]</a> of the optional 
+       Enable description in <a href="#WSDL11">[WSDL11]</a> of the OPTIONAL 
        request-response interaction.
       </p></li></ul></div><div class="div2">
 <h3><a name="Example" id="Example"/>2.2 Example</h3><p><a href="#GetRequest">Example 2-1</a> illustrates a sample 
@@ -445,8 +445,14 @@
      Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
      MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
     </p><p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p><p>
      Support for the GetMetadata operation by a Web service is 
-     optional. If metadata about a Web service endpoint is referenced by 
+     OPTIONAL. If metadata about a Web service endpoint is referenced by 
      a Metadata Reference, which is a 
      <a href="#AddrCore">[WS-Addressing]</a> endpoint reference, then the Metadata 
      Reference MUST refer to a <a href="#WS-Transfer">[WS-Transfer]</a> resource. 
@@ -491,7 +497,7 @@
     within the collection are represented by Metadata Section elements.
    </p><p>
     To facilitate processing, Metadata Sections are tagged with a 
-    @Dialect and (optionally) @Identifier of the metadata unit. To ensure 
+    @Dialect and (OPTIONALLY) @Identifier of the metadata unit. To ensure 
     scalability, a unit of metadata MAY be included in-line within its 
     Metadata Section or MAY be included by reference, either an endpoint 
     reference <a href="#AddrCore">[WS-Addressing]</a> 
@@ -944,7 +950,7 @@
      </p></li><li><p><b>Replay</b> - Messages can be replayed for a variety of 
       reasons. To detect and eliminate this attack, mechanisms SHOULD 
       be used to identify replayed messages such as the timestamp/nonce 
-      outlined in WS-Security. Alternatively, and optionally, other 
+      outlined in WS-Security. Alternatively, and OPTIONALLY, other 
       technologies, such as sequencing, can also be used to prevent 
       replay of application messages.
      </p></li></ul></div><div class="div1">
@@ -968,7 +974,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1418" id="iddiv2_1_1418"/>10.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1420" id="iddiv2_1_1420"/>10.1 MetadataExchange Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-MetadataExchange specification is through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -992,7 +998,7 @@
      In order to indicate that the subject supports WS-MetadataExchange
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -1046,7 +1052,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1482" id="iddiv2_1_1482"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1484" id="iddiv2_1_1484"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1113,7 +1119,7 @@
        , P. Biron, A. Malhotra, Editors.
        World Wide Web Consortium (W3C), 28 October 2004.
       Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1655" id="iddiv2_1_1655"/>12.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1657" id="iddiv2_1_1657"/>12.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
         OASIS Standard, "Web Services Secure Conversation
           (WS-SecureConversation) 1.4"
        </cite></a>
@@ -1337,4 +1343,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406">6406</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -d -r1.97 -r1.98
--- wseventing.xml	20 Oct 2009 23:25:53 -0000	1.97
+++ wseventing.xml	20 Oct 2009 23:59:21 -0000	1.98
@@ -779,6 +779,14 @@
      MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
     </p>
 
+    <p>
+     For any message defined by this specification, any OPTIONAL elements
+     or attributes in the message MAY be used by senders of the message,
+     however receivers of those messages MUST understand those OPTIONAL
+     elements and attributes, unless other behavior is explicitly defined
+     by this specification.
+    </p>
+
    </div2>
   </div1>
 
@@ -897,7 +905,7 @@
       <label> <kw>[Body]</kw>/wse:Subscribe/wse:Format </label>
       <def>
        <p>
-        This optional element contains
+        This OPTIONAL element contains
         the delivery format to be used for notification messages sent in 
         relation to this subscription. Implied value is 
         "http://www.w3.org/&wsevt.nsprefix;/ws-evt/DeliveryFormats/Unwrap", which 
@@ -1869,7 +1877,7 @@
       <label> <kw>[Body]</kw>/wse:SubscriptionEnd/wse:Reason </label>
       <def>
        <p>
-        This optional element contains text, in the language
+        This OPTIONAL element contains text, in the language
         specified by the @xml:lang attribute, describing the reason
         for the unexpected subscription termination.
        </p>
@@ -2119,7 +2127,7 @@
       <label> /wse:RetryAfter/@any</label>
       <def>
        <p>
-        Optional extensibility attributes that do not affect processing.
+        OPTIONAL extensibility attributes that do not affect processing.
        </p>
       </def>
      </gitem>
@@ -2266,7 +2274,7 @@
 
     <p>
      This fault is generated when a Subscribe request specifies a filter
-     dialect that the event source does not support. Optionally, this
+     dialect that the event source does not support. OPTIONALLY, this
      fault MAY contain a list of supported filter dialect IRIs in the
      Detail property.
     </p>
@@ -2293,7 +2301,7 @@
        <td>
         &lt;wse:SupportedDialect&gt; + 
         <phrase/>
-        <emph>Optional; one per filter dialect supported by the
+        <emph>OPTIONAL; one per filter dialect supported by the
         receiver</emph>
        </td>
       </tr>
@@ -2306,7 +2314,7 @@
 
     <p>
      This fault is generated when a Subscribe request specifies a delivery 
-     format that is not supported by the event source. Optionally, this 
+     format that is not supported by the event source. OPTIONALLY, this 
      fault MAY contain a list of supported delivery format IRIs in the 
      Detail property.
     </p>
@@ -2333,7 +2341,7 @@
        <td>
         &lt;wse:SupportedDeliveryFormat> +
         <phrase/>
-        <emph> Optional, one per delivery format supported by the receiver.</emph>
+        <emph> OPTIONAL, one per delivery format supported by the receiver.</emph>
        </td>
       </tr>
      </tbody>
@@ -2555,7 +2563,7 @@
        for a variety of reasons. To detect and eliminate this
        attack, mechanisms SHOULD be used to identify replayed
        messages such as the timestamp/nonce outlined in WS-Security.
-       Alternatively, and optionally, other technologies, such as
+       Alternatively, and OPTIONALLY, other technologies, such as
        sequencing, can also be used to prevent replay of application
        messages.
       </p>
@@ -2702,7 +2710,7 @@
      In order to indicate that the subject supports WS-Eventing
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -2822,7 +2830,7 @@
      In order to indicate that the subject supports WS-Eventing
      but does not require its use, an additional policy alternative should
      be provided which does not contain this assertion. The compact
-     authoring style for an optional policy assertion (the wsp:Optional
+     authoring style for an OPTIONAL policy assertion (the wsp:Optional
      attribute) provided by WS-Policy may be used to indicate two policy
      alternatives, one which contains the policy assertion, and another
      which does not.
@@ -3176,7 +3184,7 @@
     There are many ways in which an Event Source could describe and 
     advertise the structure of the Events for which it will issue 
     Notifications. To provide a basic level of interoperability, this 
-    specification defines the following two optional mechanisms, in 
+    specification defines the following two OPTIONAL mechanisms, in 
     <specref ref="ETypes"/> and <specref ref="NWSDL"/>, for describing and 
     advertising Event information. If an implementation of a WS-Eventing 
     Event Source chooses to describe the structure of its Events and 
@@ -3326,7 +3334,7 @@
       <label> /wse:EventDescriptions/wse:eventType/@actionURI </label>
       <def>
        <p>
-        This optional attribute provides a value for the various 'action' 
+        This OPTIONAL attribute provides a value for the various 'action' 
         properties and attributes which, depending upon the format of the 
         Notification used to transmit the Event, serve as a potential aide 
         to identifying the semantics implied by the message. When not 
@@ -4592,6 +4600,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 20 October 2009 23:59:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 October 2009 23:59:32 GMT