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

WWW/2002/ws/ra/edcopies wsevd.html,1.11,1.12 wsevd.xml,1.8,1.9 wseventing.html,1.174,1.175 wseventing.xml,1.167,1.168

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 20 Apr 2010 21:46:49 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1O4LHN-0005sM-SX@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv22444

Modified Files:
	wsevd.html wsevd.xml wseventing.html wseventing.xml 
Log Message:
9321


Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- wsevd.html	30 Mar 2010 22:20:57 -0000	1.11
+++ wsevd.html	20 Apr 2010 21:46:45 -0000	1.12
@@ -49,12 +49,12 @@
 &nbsp;&nbsp;&nbsp;3.5 <a href="#compliance">Compliance</a><br/>
 4 <a href="#Advertising">Advertising Event Information</a><br/>
 &nbsp;&nbsp;&nbsp;4.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#iddiv3_1_553">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.2 <a href="#iddiv3_1_593">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#iddiv3_1_555">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.2 <a href="#iddiv3_1_595">Bindings for Event Descriptions</a><br/>
 5 <a href="#acks">Acknowledgements</a><br/>
 6 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_608">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2_1_638">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_610">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2_1_640">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#EVDXSD">XML Schema for EventDescriptions</a><br/>
 B <a href="#changelog">Change Log</a><br/>
@@ -259,18 +259,22 @@
         that identifies this Event Type outside the context of the 
         enclosing wsevd:EventDescriptions element. 
        </p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType/@element </dt><dd><p>
-        This attribute refers to a GED defined or imported in the 
+        This OPTIONAL attribute refers to a GED defined or imported in the 
         /wsevd:EventDescriptions/wsevd:types element. The referenced GED 
-        serves as the definition of this Event Type.
+        serves as the definition of this Event Type. 
        </p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType/@actionURI </dt><dd><p>
         This OPTIONAL attribute provides a value for the 'action' 
         property which, depending upon the format of the 
         notification used to transmit the Event, serve as a potential aid 
         to identifying the semantics implied by the message. When not 
         present the implied value of this attribute is the concatenation 
-        of the wsevd:EventDescriptions' targetNamespace attribute and
+        of the wsevd:EventDescriptions' @targetNamespace attribute and
         the wsevd:eventType name attribute separated by the '/' character.
        </p></dd></dl><p>
+     Note, while the schema allows for the @element attribute and the
+     @actionURI attribute to be absent, at least one of them MUST be
+     present for each eventType.
+    </p><p>
      The following is an example of an EventDescriptions element that could 
      serve as a description of the Event Type used in 
      <a href="#EVDExample">Example 4-2</a>. 
@@ -324,7 +328,7 @@
 (24)     &lt;/ow:WindReport&gt;
 (25)   &lt;/s12:Body&gt;
 (26) &lt;/s12:Envelope&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_553" id="iddiv3_1_553"/>4.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_555" id="iddiv3_1_555"/>4.1.1 Retrieving Event Descriptions</h4><p>
       Although there are many ways in which an endpoint can make its 
       EventDescriptions available, this specification RECOMMENDS the use of 
       the mechanisms described in section 9 of WS-MetadataExchange 
@@ -363,7 +367,7 @@
       representation is the Event Description metadata. The data can be 
       retrieved via an HTTP GET to the specified URL.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_593" id="iddiv3_1_593"/>4.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_595" id="iddiv3_1_595"/>4.1.2 Bindings for Event Descriptions</h4><p>
       Any specification of a publish-subscribe system that uses 
       Event Descriptions to advertise the events that are generated
       MUST clearly define how those events are serialized when they
@@ -400,7 +404,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>6 References</h2><div class="div2">
-<h3><a name="iddiv2_1_608" id="iddiv2_1_608"/>6.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_610" id="iddiv2_1_610"/>6.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.
@@ -411,7 +415,7 @@
        , M. Duerst and M. Suignard, Authors.
        Internet Engineering Task Force, January 2005.
       Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_638" id="iddiv2_1_638"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+<h3><a name="iddiv2_1_640" id="iddiv2_1_640"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
         W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
        </cite></a>
        , D. Box, et al, Editors.
@@ -485,7 +489,7 @@
               &lt;xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/&gt;
             &lt;/xs:sequence&gt;
             &lt;xs:attribute name='name' type='xs:NCName' use='required'/&gt;
-            &lt;xs:attribute name='element' type='xs:QName' use='required'/&gt;
+            &lt;xs:attribute name='element' type='xs:QName' use='optional'/&gt;
             &lt;xs:attribute name='actionURI' type='xs:anyURI' use='optional'/&gt;
             &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
           &lt;/xs:complexType&gt;
@@ -503,4 +507,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8900">8900</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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=9031">9031</a></td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</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.167
retrieving revision 1.168
diff -u -d -r1.167 -r1.168
--- wseventing.xml	30 Mar 2010 23:39:58 -0000	1.167
+++ wseventing.xml	20 Apr 2010 21:46:47 -0000	1.168
@@ -3304,16 +3304,16 @@
      <head>EventDescriptions</head>
      <eg>(01) &lt;wsevd:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
-(03)        xmlns:wse="http://www.w3.org/&wsevt.nsprefix;/ws-evt"
+(03)        xmlns:wsevd="http://www.w3.org/&wsevt.nsprefix;/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch">
-(05)   &lt;wse:types>
+(05)   &lt;wsevd:types>
 (06)     &lt;xs:schema targetNamespace="http://www.example.org/oceanwatch">
 (07)       &lt;xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/>
 (08)       &lt;xs:element name="WindReport" type="ow:WindReportType"/>
 (09)     &lt;/xs:schema>
-(10)   &lt;/wse:types>
+(10)   &lt;/wsevd:types>
 (11)
-(12)   &lt;wse:eventType name="WindReportEvent"
+(12)   &lt;wsevd:eventType name="WindReportEvent"
 (13)                  element="ow:WindReport"
 (14)                  actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
 (15) &lt;/wsevd:EventDescriptions></eg>
@@ -3391,12 +3391,12 @@
      <head>Bindings for Event Descriptions</head>
      <p>
       For any Notification Format it MUST be possible to determine how a 
-      given wse:eventType will appear on the wire as a notification in a 
+      given wsevd:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
-      how wse:eventTypes bind to notifications for the two Notification 
+      how wsevd:eventTypes bind to notifications for the two Notification 
       Formats defined in this specification; Unwrapped and Wrapped. 
       Specifications or profiles that define additional Notification Formats 
-      MUST define how wse:eventTypes bind to the notifications for those 
+      MUST define how wsevd:eventTypes bind to the notifications for those 
       formats. In the absence of a mapping for a particular Notification 
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
@@ -3405,7 +3405,7 @@
      <div4>
       <head>Binding for Unwrapped Notifications</head>
       <p>
-       The information about an Event Type contained in the wse:eventType 
+       The information about an Event Type contained in the wsevd:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p>
 
@@ -3413,7 +3413,7 @@
        <item>
         <p>
          The <kw>[Action]</kw> property of the notification has the value of 
-         the actionURI attribute of the wse:eventType element 
+         the @actionURI attribute of the wsevd:eventType element 
          corresponding to the type of the event being transmitted.
         </p>
        </item>
@@ -3421,9 +3421,10 @@
         <p>
          The <kw>[Body]</kw> property of the notification
          has a single child element. This child element is an instance of 
-         the Global Element Declaration referenced by the element attribute 
-         of the wse:eventType element corresponding to the type of the 
-         event being transmitted.
+         the Global Element Declaration referenced by the @element attribute 
+         of the wsevd:eventType element corresponding to the type of the 
+         event being transmitted. If the @element attribute is absent then
+         the <kw>[Body]</kw> property has no children.
         </p>
        </item>
       </ulist>
@@ -3440,7 +3441,7 @@
        <item>
         <p>
          The /soap:Envelope/soap:Body/wse:Notify/@actionURI attribute of the 
-         Wrapped Notification has the value of the actionURI attribute of 
+         Wrapped Notification has the value of the @actionURI attribute of 
          the eventType element corresponding to the type of the event 
          being transmitted. 
         </p>
@@ -3449,8 +3450,10 @@
         <p>
          The /soap:Envelope/soap:Body/wse:Notify element has a single child 
          element. This child element is an instance of the Global Element 
-         Declaration referenced by the element attribute of the eventType 
+         Declaration referenced by the @element attribute of the eventType 
          element corresponding to the type of the event being transmitted. 
+         If the @element attribute is absent then the wse:Notify element
+         has no children.
         </p>
        </item>
       </ulist>
@@ -5002,6 +5005,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/04/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.174
retrieving revision 1.175
diff -u -d -r1.174 -r1.175
--- wseventing.html	30 Mar 2010 23:39:58 -0000	1.174
+++ wseventing.html	20 Apr 2010 21:46:46 -0000	1.175
@@ -88,9 +88,9 @@
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2689">Retrieving Event Descriptions</a><br/>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2726">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_2731">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_2749">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2752">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_2776">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2779">Retrieving Notification WSDLs</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/>
@@ -1847,16 +1847,16 @@
     </p><div class="exampleOuter">
 <div class="exampleHeader"><a name="idexample_1_2679" id="idexample_1_2679"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
-(03)        xmlns:wse="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
+(03)        xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
-(05)   &lt;wse:types&gt;
+(05)   &lt;wsevd:types&gt;
 (06)     &lt;xs:schema targetNamespace="http://www.example.org/oceanwatch"&gt;
 (07)       &lt;xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/&gt;
 (08)       &lt;xs:element name="WindReport" type="ow:WindReportType"/&gt;
 (09)     &lt;/xs:schema&gt;
-(10)   &lt;/wse:types&gt;
+(10)   &lt;/wsevd:types&gt;
 (11)
-(12)   &lt;wse:eventType name="WindReportEvent"
+(12)   &lt;wsevd:eventType name="WindReportEvent"
 (13)                  element="ow:WindReport"
 (14)                  actionURI="http://www.example.org/oceanwatch/2003/WindReport"/&gt;
 (15) &lt;/wsevd:EventDescriptions&gt;</pre></div></div><p>
@@ -1905,43 +1905,46 @@
      </p></div><div class="div3">
 <h4><a name="iddiv3_1_2726" id="iddiv3_1_2726"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it MUST be possible to determine how a 
-      given wse:eventType will appear on the wire as a notification in a 
+      given wsevd:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
-      how wse:eventTypes bind to notifications for the two Notification 
+      how wsevd:eventTypes bind to notifications for the two Notification 
       Formats defined in this specification; Unwrapped and Wrapped. 
       Specifications or profiles that define additional Notification Formats 
-      MUST define how wse:eventTypes bind to the notifications for those 
+      MUST define how wsevd:eventTypes bind to the notifications for those 
       formats. In the absence of a mapping for a particular Notification 
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
      </p><div class="div4">
 <h5><a name="iddiv4_1_2731" id="iddiv4_1_2731"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
-       The information about an Event Type contained in the wse:eventType 
+       The information about an Event Type contained in the wsevd:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
          The <b>[Action]</b> property of the notification has the value of 
-         the actionURI attribute of the wse:eventType element 
+         the @actionURI attribute of the wsevd:eventType element 
          corresponding to the type of the event being transmitted.
         </p></li><li><p>
          The <b>[Body]</b> property of the notification
          has a single child element. This child element is an instance of 
-         the Global Element Declaration referenced by the element attribute 
-         of the wse:eventType element corresponding to the type of the 
-         event being transmitted.
+         the Global Element Declaration referenced by the @element attribute 
+         of the wsevd:eventType element corresponding to the type of the 
+         event being transmitted. If the @element attribute is absent then
+         the <b>[Body]</b> property has no children.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2749" id="iddiv4_1_2749"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2752" id="iddiv4_1_2752"/>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>
          The /soap:Envelope/soap:Body/wse:Notify/@actionURI attribute of the 
-         Wrapped Notification has the value of the actionURI attribute of 
+         Wrapped Notification has the value of the @actionURI attribute of 
          the eventType element corresponding to the type of the event 
          being transmitted. 
         </p></li><li><p>
          The /soap:Envelope/soap:Body/wse:Notify element has a single child 
          element. This child element is an instance of the Global Element 
-         Declaration referenced by the element attribute of the eventType 
+         Declaration referenced by the @element attribute of the eventType 
          element corresponding to the type of the event being transmitted. 
+         If the @element attribute is absent then the wse:Notify element
+         has no children.
         </p></li></ul></div></div></div><div class="div2">
 <h3><a name="NWSDL" id="NWSDL"/>A.2 Notification WSDLs</h3><p>
      As described previously, events are transmitted to event sinks as 
@@ -1953,7 +1956,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_2770" id="idexample_1_2770"/>Example A-4: 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_2773" id="idexample_1_2773"/>Example A-4: 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/"
@@ -1988,7 +1991,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_2776" id="iddiv3_1_2776"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2779" id="iddiv3_1_2779"/>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>.
@@ -2678,4 +2681,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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=9266">9266</a></td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- wsevd.xml	30 Mar 2010 22:20:57 -0000	1.8
+++ wsevd.xml	20 Apr 2010 21:46:46 -0000	1.9
@@ -534,9 +534,9 @@
       <label> /wsevd:EventDescriptions/wsevd:eventType/@element </label>
       <def>
        <p>
-        This attribute refers to a GED defined or imported in the 
+        This OPTIONAL attribute refers to a GED defined or imported in the 
         /wsevd:EventDescriptions/wsevd:types element. The referenced GED 
-        serves as the definition of this Event Type.
+        serves as the definition of this Event Type. 
        </p>
       </def>
      </gitem>
@@ -549,12 +549,18 @@
         notification used to transmit the Event, serve as a potential aid 
         to identifying the semantics implied by the message. When not 
         present the implied value of this attribute is the concatenation 
-        of the wsevd:EventDescriptions' targetNamespace attribute and
+        of the wsevd:EventDescriptions' @targetNamespace attribute and
         the wsevd:eventType name attribute separated by the '/' character.
        </p>
       </def>
      </gitem>
     </glist>
+
+    <p>
+     Note, while the schema allows for the @element attribute and the
+     @actionURI attribute to be absent, at least one of them MUST be
+     present for each eventType.
+    </p>
     
     <p>
      The following is an example of an EventDescriptions element that could 
@@ -891,7 +897,7 @@
               &lt;xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
             &lt;/xs:sequence>
             &lt;xs:attribute name='name' type='xs:NCName' use='required'/>
-            &lt;xs:attribute name='element' type='xs:QName' use='required'/>
+            &lt;xs:attribute name='element' type='xs:QName' use='optional'/>
             &lt;xs:attribute name='actionURI' type='xs:anyURI' use='optional'/>
             &lt;xs:anyAttribute namespace='##other' processContents='lax'/>
           &lt;/xs:complexType>
@@ -946,6 +952,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/04/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 20 April 2010 21:46:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 April 2010 21:47:00 GMT