issue 9031 - please review from Doug Davis on 2010-03-30 (public-ws-resource-access@w3.org from March 2010)

From: Doug Davis <dug@us.ibm.com>
Date: Tue, 30 Mar 2010 18:21:04 -0400
To: public-ws-resource-access@w3.org
Message-ID: <OFC36FFB38.D155D2B6-ON852576F6.00794FCE-852576F6.007AC86B@us.ibm.com>
All,
  please review the latest WSMex, WS-Eventing and WS-EVD specs - 9031 
impacted all of these.

MEX:
- most of the edits here are obvious, but please note that I had to change 
the "URI" attribute to "Type" - since its not a URI any more.  I used the 
word "Type" to match what we used for the MOAP stuff

Eventing/EVD:
- both of these specs talked about retrieving Notification WSDL and/or EVD 
metadata. For notification wsdl it still talked about a dedicated MEX 
Dialect URI that is meant to be used.  I think this bit was missed as part 
of the other MOAP stuff.  I modified the text so that it mentions the MOAP 
way of getting it - adding a reference to it from the policy.
- WS-Eventing talked about how to retrieve the EVD data but it didn't 
exactly match what EVD said so I made it align.
- WS-Eventing talked about what the MEX @Identifier attribute MUST be for 
EVD data - but oddly enough, the EVD spec didn't so I added a paragraph to 
EVD for this.  Also, I added the phrase "if present" since the use of the 
attribute is optional.
- I removed the "Multiple Event Information Metadata Sections" section 
from WS-Eventing since I don't think this issue applies any more now that 
we're doing MOAP.
- In EVD I added the definition of the "wse" namespace to the NS table.

Please let me know if there are any concerns.

I've copied the diffs for evd and evening below:

D:\wsra\cvs\edcopies>cvs diff wseventing.xml
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.165
diff -u -r1.165 wseventing.xml
--- wseventing.xml      30 Mar 2010 20:46:46 -0000      1.165
+++ wseventing.xml      30 Mar 2010 22:11:18 -0000
@@ -3353,7 +3353,7 @@

     <example>
      <head>EventDescriptions</head>
-     <eg>(01) &lt;wse:EventDescriptions
+     <eg>(01) &lt;wsevd:EventDescriptions
 (02) targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/&wsevt.nsprefix;/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch">
@@ -3367,7 +3367,7 @@
 (12)   &lt;wse:eventType name="WindReportEvent"
 (13)                  element="ow:WindReport"
 (14) actionURI="http://www.example.org/oceanwatch/2003/WindRep
ort"/>
-(15) &lt;/wse:EventDescriptions></eg>
+(15) &lt;/wsevd:EventDescriptions></eg>
     </example>

     <p>
@@ -3383,19 +3383,59 @@
       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 <bibref 
ref="MEX"/>.
-      This specification defines the following IRI to serve as the 
Dialect
-      IRI for the wse:EventDescriptions element.
+      In particular, this specification RECOMMENDS that the Event 
Description
+      metadata be made available through the EventSource Policy 
assertion.
+      This MAY be done by either embedding the Event Description metadata
+      directly within the assertion, or by including a MetadataExchange
+      reference to the data.
      </p>

-     <example>
-      <eg><loc 
href="http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescription
s">http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions</loc></eg>
+     <p>
+      The value of the @Identifier attribute, if present, for this
+      MetadataSection MUST
+      be equal to the value of its 
wsevd:EventDescriptions/@targetNamespace. An

+      event source MUST NOT have more than one EventDescriptions 
document.
+     </p>
+
+     <p>
+      The following examples show how Event Description metadata might
+      appear within a WS-Eventing EventSource Policy assertion.
+     </p>
+
+     <example id="embedEVD">
+      <head>Sample Embedded EventDescription Metadata</head>
+      <eg>(01) &lt;wse:EventSource ...>
+(02)   &lt;wse:FormatName URI="..."/>
+(03)   &lt;wsevd:EventDescritions ...>
+(04)     ...
+(05)   &lt;/wsevd:EventDescriptions>
+(06) &lt;/wse:EventSource></eg>
      </example>

      <p>
-      The value of the @Identifier attribute for this Metadata Section 
MUST
-      be equal to the value of its 
wse:EventDescriptions/@targetNamespace. An
-      event source MUST NOT have more than one EventDescriptions 
document.
+      <specref ref="embedEVD"/> shows how the Event Description metadata
+      might be embedded directly within a WS-Eventing EventSource Policy
+      assertion.
      </p>
+
+     <example id="refEVD">
+      <head>Sample Reference to EventDescription Metadata</head>
+      <eg>(01) &lt;wse:EventSource ...>
+(02)   &lt;wse:FormatName URI="..."/>
+(03)   &lt;mex:Location
+(04)     Type="evd:EventDescriptions"
+(05)     URI="http://example.com/EVD_Metadata" />
+(06) &lt;/wse:EventSource> </eg>
+     </example>
+
+     <p>
+      <specref ref="refEVD"/> shows the same policy assertion from
+      <specref ref="embedEVD"/> except the embedded Event Description
+      metadata is replaced with a reference to an HTTP resource whose
+      representation is the Event Description metadata. The data can be
+      retrieved via an HTTP GET to the specified URL.
+     </p>
+
     </div3>

     <div3>
@@ -3529,45 +3569,13 @@
       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 <bibref 
ref="MEX"/>.
-      This specification defines the following IRI to serve as the 
Dialect
-      IRI for the Notification WSDL.
-     </p>
-
-     <example>
-      <eg><loc 
href="http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL
">http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL</loc></eg>
-     </example>
-
-     <p>
-      Because the Notification Format specified in a Subscribe request 
can
-      affect various aspects of the Notification WSDL, it is necessary to
-      correlate Notification WSDLs with their corresponding Notification
-      Formats. When using WS-MetadataExchange to transfer Notification 
WSDLs,
-      the corresponding Format IRI for that Notification WSDL MUST be
-      represented via the @Identifier attribute. For any particular
-      Format IRI/@Identifier, there MUST NOT exist more than one
-      Notification WSDL document.
+      In particular, if an event source has Notification WSDL then it
+      SHOULD be referenced from the wse:EventSource policy assertion.
      </p>
     </div3>

    </div2>

-   <div2>
-    <head>Multiple Event Information Metadata Sections</head>
-    <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
-     "http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions" and
-     "http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL" 
dialects MUST

-     regard these Metadata Sections as relating to the same set of 
events.
-     In cases where the mex:Metadata element contains multiple
-     Notification WSDLs (i.e. multiple Metadata Sections with a @Dialect
-     of "http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL"), 
recipien
ts MUST
-     similarly regard these Notification WSDLs as relating to the same 
set
-     of events although their Notification Formats differ.
-    </p>
-   </div2>
-
   </div1>

   <div1 id="Schema">
@@ -5031,6 +5039,13 @@
        <loc 
href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</loc
>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/30 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc 
href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc
>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

D:\wsra\cvs\edcopies>cvs diff wsevd.xml
Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.7
diff -u -r1.7 wsevd.xml
--- wsevd.xml   17 Mar 2010 03:25:47 -0000      1.7
+++ wsevd.xml   30 Mar 2010 22:15:37 -0000
@@ -325,6 +325,15 @@
         XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
        </td>
       </tr>
+      <tr>
+       <td>wse</td>
+       <td>
+        <loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt">
+         http://www.w3.org/&wsevt.nsprefix;/ws-evt
+        </loc>
+       </td>
+       <td>WS-Eventing <bibref ref="Eventing"/></td>
+      </tr>
      </tbody>
     </table>

@@ -629,6 +638,13 @@
      </p>

      <p>
+      The value of the @Identifier attribute, if present, for this
+      MetadataSection MUST be equal to the value of its
+      wsevd:EventDescriptions/@targetNamespace. An event source MUST NOT 
have
+      more than one EventDescriptions document.
+     </p>
+
+     <p>
       The following examples show how Event Description metadata might
       appear within a WS-Eventing EventSource Policy assertion.
      </p>

D:\wsra\cvs\edcopies>

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.
Received on Tuesday, 30 March 2010 22:21:50 UTC