- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 13 May 2010 22:39:20 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv8219
Modified Files:
wseventing.html wseventing.xml xmlspec.dtd
Log Message:
9610
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.193
retrieving revision 1.194
diff -u -d -r1.193 -r1.194
--- wseventing.xml 13 May 2010 21:33:10 -0000 1.193
+++ wseventing.xml 13 May 2010 22:39:18 -0000 1.194
@@ -1580,13 +1580,47 @@
<kw>[Body]</kw>
<wse:GetStatus ...>
+ <wse:Verify ...>
+ <emph>xs:any</emph>*
+ </wse:Verify> ?
<emph>xs:any</emph>*
</wse:GetStatus></eg>
</example>
<p>
- Components of the outline listed above are not further constrained
- by this specification.
+ The following describes additional, normative constraints on
+ the outline listed above:
+ </p>
+
+ <glist>
+ <gitem>
+ <label> <kw>[Body]</kw>/wse:GetStatus/wse:Verify </label>
+ <def>
+ <p>
+ This OPTIONAL element can be used by the subscriber in its
+ GetStatus request to ask the subscription manager to verify that
+ notifications can be transmitted from the event source to the
+ event sink. Conformant subscription managers MAY elect not to
+ perform the requested verification.
+ </p>
+
+ <p>
+ If the subscription manager opts to support the wse:Verify request,
+ it MUST include a wse:VerificationInitiated element in its
+ GetStatus response, and it MUST cause the event source to transmit
+ a single notification, containing a single verification event,
+ as defined in <specref ref="VerificationEvent"/>, from the event
+ source to the event sink using the delivery method and format in
+ effect for this subscription. Any filters in effect for the
+ subscription MUST NOT be applied to this notification.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+
+ <p>
+ Other components of the outline above are not further constrained by
+ this specification.
</p>
<p>
@@ -1604,22 +1638,47 @@
<wse:GrantedExpires ...>
(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)
</wse:GrantedExpires> ?
+ <VerificationInitiated ...>
+ <emph>xs:any</emph>*
+ </VerificationInitiated> ?
<emph>xs:any</emph>*
</wse:GetStatusResponse></eg>
</example>
<p>
- Components of the outline listed above are constrained as for
- a response to a renew request (see <specref ref="Renew"/>).
- Other components of the outline above are not further
- constrained by this specification.
+ The following describes additional, normative constraints on
+ the outline listed above:
</p>
+ <glist>
+ <gitem>
+ <label> <kw>[Body]</kw>/wse:GetStatusResponse/wse:VerificationInitiated </label>
+ <def>
+ <p>
+ The presence of this OPTIONAL element in the GetStatusResponse
+ indicates that the subscription manager has honored the
+ verification request. This element MUST NOT appear in the
+ GetStatusResponse unless the corresponding GetStatus request
+ contained the wse:Verify element. The absence of this element in
+ a GetStatusResponse indicates that a verification was not initiated.
+ </p>
+
+ <p>
+ Note, the relative timing of the verification and the
+ GetStatusResponse message is unconstrained by this specification.
+ The presence of the wse:VerificationInitiated element in a
+ GetStatusResponse message does not indicate the success of the
+ verification.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+
<p>
- This operation is safe; it will not result in any side effect
- imputable to the requester. This means that in case of an underlying
- protocol error that might get unnoticed, resending the same request
- can be done automatically.
+ Components of the outline listed above are additionaly constrained as for
+ a response to a renew request (see <specref ref="Renew"/>).
+ Other components of the outline above are not further
+ constrained by this specification.
</p>
<p>
@@ -3544,6 +3603,82 @@
</div1>
+ <div1 id="VerificationEvent">
+ <head>Verification Event</head>
+
+ <p>
+ As described in <specref ref="GetStatus"/>, a verification request
+ tests the ability of the event source to successfully transmit a
+ notification to the event sink. A notification of the 'verification event'
+ is used in this test.
+ </p>
+
+ <div2>
+ <head>EventDescription for the Verification Event</head>
+
+ <p>
+ The verification event is described by the following EventDescription.
+ </p>
+
+ <example>
+ <eg><wsevd:EventDescriptions
+ xmlns:wsevd='http://www.w3.org/2002/ws/ra/edcopies/ws-evd'
+ targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'
+ xmlns:xs='http://www.w3.org/2001/XMLSchema'
+ xmlns:wse='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+
+ <wsevd:types>
+ <xs:schema targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+ <xs:include schemaLocation='http://www.w3.org/.../eventing.xsd'/>
+ <xs:element name='Verification' type='wse:VerificationEventType'/>
+ </xs:schema>
+ </wsevd:types>
+
+ <wsevd:eventType name='VerificationEvent'
+ element='wse:Verification'
+ actionURI='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/Verfication'/>
+</wsevd:EventDescriptions></eg>
+ </example>
+ </div2>
+
+ <div2>
+ <head>Notification WSDL for the Verification Event</head>
+
+ <p>
+ The verification event is described by the following Notification WSDL.
+ </p>
+
+ <example>
+ <eg><wsdl:definitions
+ xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
+ targetNamespace='http://www.w3.org/&wsevt.nsprefix;/ws-evt'
+ xmlns:xs='http://www.w3.org/2001/XMLSchema'
+ xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
+ xmlns:tns='http://www.w3.org/&wsevt.nsprefix;/ws-evt'>
+
+ <wsdl:types>
+ <xs:schema targetNamespace='http://www.w3.org/&wsevt.nsprefix;/ws-evt'>
+ <xs:include schemaLocation='http://www.w3.org/&wsevt.nsprefix;/ws-evt/eventing.xsd'/>
+
+ <xs:element name='Verification' type='wse:VerificationEventType'/>
+ </xs:schema>
+ </wsdl:types>
+
+ <wsdl:message name='VerificationMsg'>
+ <wsdl:part name='part1' element='wse:Verification'>
+ </wsdl:message>
+
+ <wsdl:portType name='VerificationPortType'>
+ <wsdl:operation name='VerificationOp'>
+ <wsdl:input message='tns:VerificationMsg'
+ wsam:Action='http://www.w3.org/&wsevt.nsprefix;/ws-evt/Verification'/>
+ </wsdl:operation>
+ </wsdl:portType>
+</wsdl:definitions></eg>
+ </example>
+ </div2>
+ </div1>
+
<div1 id="Schema">
<head>XML Schema</head>
@@ -3732,6 +3867,15 @@
<xs:element name='GetStatus'>
<xs:complexType>
<xs:sequence>
+ <xs:element name='Verify' minOccurs='0'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax'
+ maxOccurs='unbounded'/>
+ </xs:sequence>
+ <xs:anyAttribute namespace='##other' processContents='lax' />
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -3745,6 +3889,15 @@
<xs:sequence>
<xs:element name='GrantedExpires' type='tns:MiniExpirationType'
minOccurs='0' />
+ <xs:element name='VerificationInitiated' minOccurs='0'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax'
+ maxOccurs='unbounded'/>
+ </xs:sequence>
+ <xs:anyAttribute namespace='##other' processContents='lax' />
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -4196,6 +4349,8 @@
</td>
<td valign="top" nowrap='true'><code>
Send GetStatusResponse<phrase/>
+ If (Verify requested)<phrase/>
+ Initiate verification test<phrase/>
{<specref ref="GetStatus" show="num"/>}</code>
</td>
<td valign="top" nowrap='true'><code>
@@ -5108,6 +5263,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702">9702</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/13 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: xmlspec.dtd
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/xmlspec.dtd,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- xmlspec.dtd 6 Feb 2010 13:03:36 -0000 1.3
+++ xmlspec.dtd 13 May 2010 22:39:18 -0000 1.4
@@ -272,7 +272,7 @@
<!ENTITY % local.eg.pcd.mix " "> <!-- compensate for IE bug; suggested by ht -->
<!ENTITY % eg.pcd.mix
"#PCDATA|%annot.class;|%emph.class;|%loc.class;|%tech.class;
- |%ednote.class;|constraint %local.eg.pcd.mix;">
+ |%ref.class;|%ednote.class;|constraint %local.eg.pcd.mix;">
<!ENTITY % local.termdef.pcd.mix " "> <!-- compensate for IE bug; suggested by ht -->
<!ENTITY % termdef.pcd.mix
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.200
retrieving revision 1.201
diff -u -d -r1.200 -r1.201
--- wseventing.html 13 May 2010 21:33:10 -0000 1.200
+++ wseventing.html 13 May 2010 22:39:18 -0000 1.201
@@ -73,31 +73,34 @@
6.11 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
6.12 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
- 7.1 <a href="#iddiv2_1_2126">Notifications</a><br/>
- 7.2 <a href="#iddiv2_1_2135">Subscriptions</a><br/>
- 7.3 <a href="#iddiv2_1_2140">Endpoint Verification</a><br/>
+ 7.1 <a href="#iddiv2_1_2159">Notifications</a><br/>
+ 7.2 <a href="#iddiv2_1_2168">Subscriptions</a><br/>
+ 7.3 <a href="#iddiv2_1_2173">Endpoint Verification</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2166">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2293">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2199">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2326">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2359">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2506">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2392">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2539">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/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2708">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2745">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2750">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2771">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2741">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2778">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2783">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2804">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2798">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/>
-E <a href="#actiontables">Action Tables</a><br/>
-F <a href="#changelog">Change Log</a><br/>
+ A.2.1 <a href="#iddiv3_1_2831">Retrieving Notification WSDLs</a><br/>
+B <a href="#VerificationEvent">Verification Event</a><br/>
+ B.1 <a href="#iddiv2_1_2848">EventDescription for the Verification Event</a><br/>
+ B.2 <a href="#iddiv2_1_2857">Notification WSDL for the Verification Event</a><br/>
+C <a href="#Schema">XML Schema</a><br/>
+D <a href="#WSDL">WSDL</a><br/>
+E <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
+F <a href="#actiontables">Action Tables</a><br/>
+G <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
@@ -976,10 +979,31 @@
<b>[Body]</b>
<wse:GetStatus ...>
+ <wse:Verify ...>
+ <em>xs:any</em>*
+ </wse:Verify> ?
<em>xs:any</em>*
</wse:GetStatus></pre></div></div><p>
- Components of the outline listed above are not further constrained
- by this specification.
+ The following describes additional, normative constraints on
+ the outline listed above:
+ </p><dl><dt class="label"><b>[Body]</b>/wse:GetStatus/wse:Verify </dt><dd><p>
+ This OPTIONAL element can be used by the subscriber in its
+ GetStatus request to ask the subscription manager to verify that
+ notifications can be transmitted from the event source to the
+ event sink. Conformant subscription managers MAY elect not to
+ perform the requested verification.
+ </p><p>
+ If the subscription manager opts to support the wse:Verify request,
+ it MUST include a wse:VerificationInitiated element in its
+ GetStatus response, and it MUST cause the event source to transmit
+ a single notification, containing a single verification event,
+ as defined in <a href="#VerificationEvent"><b>B Verification Event</b></a>, from the event
+ source to the event sink using the delivery method and format in
+ effect for this subscription. Any filters in effect for the
+ subscription MUST NOT be applied to this notification.
+ </p></dd></dl><p>
+ Other components of the outline above are not further constrained by
+ this specification.
</p><p>
If the subscription is active, the
subscription manager MUST reply with a response of the following
@@ -992,17 +1016,31 @@
<wse:GrantedExpires ...>
(<em>xs:dateTime</em> | <em>xs:duration</em>)
</wse:GrantedExpires> ?
+ <VerificationInitiated ...>
+ <em>xs:any</em>*
+ </VerificationInitiated> ?
<em>xs:any</em>*
</wse:GetStatusResponse></pre></div></div><p>
- Components of the outline listed above are constrained as for
+ The following describes additional, normative constraints on
+ the outline listed above:
+ </p><dl><dt class="label"><b>[Body]</b>/wse:GetStatusResponse/wse:VerificationInitiated </dt><dd><p>
+ The presence of this OPTIONAL element in the GetStatusResponse
+ indicates that the subscription manager has honored the
+ verification request. This element MUST NOT appear in the
+ GetStatusResponse unless the corresponding GetStatus request
+ contained the wse:Verify element. The absence of this element in
+ a GetStatusResponse indicates that a verification was not initiated.
+ </p><p>
+ Note, the relative timing of the verification and the
+ GetStatusResponse message is unconstrained by this specification.
+ The presence of the wse:VerificationInitiated element in a
+ GetStatusResponse message does not indicate the success of the
+ verification.
+ </p></dd></dl><p>
+ Components of the outline listed above are additionaly constrained as for
a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
Other components of the outline above are not further
constrained by this specification.
- </p><p>
- This operation is safe; it will not result in any side effect
- imputable to the requester. This means that in case of an underlying
- protocol error that might get unnoticed, resending the same request
- can be done automatically.
</p><p><a href="#Table8">Example 4-5</a> lists a hypothetical request to get the
status of the subscription created in <a href="#Table5">Example 4-2</a>.
</p><div class="exampleOuter">
@@ -1417,7 +1455,7 @@
urged to perform a security analysis to determine their particular
threat profile and the appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2_1_2126" id="iddiv2_1_2126"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2_1_2159" id="iddiv2_1_2159"/>7.1 Notifications</h3><p>
The information contained in Notifications might be sensitive. In
such cases it is advisable to authenticate and authorize subscribers
as part of the processing of the Subscribe request. Note that an
@@ -1438,7 +1476,7 @@
and trace the origin of such attempts. Additionally, the
authorization of Subscribers reduces the pool of potential attackers.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_2135" id="iddiv2_1_2135"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2_1_2168" id="iddiv2_1_2168"/>7.2 Subscriptions</h3><p>
Once created, subscriptions ought to be treated as protected
resources. Renew, GetStatus, and Unsubscribe requests ought to be
authenticated and authorized (for example, the identity of the
@@ -1453,7 +1491,7 @@
the identities of these entities are discovered and verified)
are particular to individual deployments.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_2140" id="iddiv2_1_2140"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2_1_2173" id="iddiv2_1_2173"/>7.3 Endpoint Verification</h3><p>
Implementations that perform validity checks on the EPRs used in
WS-Eventing (wse:NotifyTo, wse:EndTo) are advised that such checks
can be misused to obtain information about a target network. For
@@ -1504,7 +1542,7 @@
that 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_2166" id="iddiv2_1_2166"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2199" id="iddiv2_1_2199"/>9.1 EventSource Assertion</h3><p>
Services indicate support for the WS-Eventing's definition
of an event source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1618,7 +1656,7 @@
(10) - (12) contains the EventDescription data that describes the
syntax of the events that this event source might send.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_2293" id="iddiv2_1_2293"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2326" id="iddiv2_1_2326"/>9.2 SubscriptionManager Assertion</h3><p>
Services indicate support for the
WS-Eventing's definition of a subscription manager
through the use of the Web Services
@@ -1691,7 +1729,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2359" id="iddiv2_1_2359"/>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_2392" id="iddiv2_1_2392"/>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.
@@ -1748,7 +1786,7 @@
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2506" id="iddiv2_1_2506"/>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_2539" id="iddiv2_1_2539"/>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>
@@ -1852,7 +1890,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2698" id="idexample_1_2698"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2731" id="idexample_1_2731"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1872,7 +1910,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_2708" id="iddiv3_1_2708"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2741" id="iddiv3_1_2741"/>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>.
@@ -1910,7 +1948,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_2745" id="iddiv3_1_2745"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2778" id="iddiv3_1_2778"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST be possible to determine how a
given wsevd:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1922,7 +1960,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_2750" id="iddiv4_1_2750"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2783" id="iddiv4_1_2783"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
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>
@@ -1937,7 +1975,7 @@
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_2771" id="iddiv4_1_2771"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2804" id="iddiv4_1_2804"/>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>
@@ -1963,7 +2001,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_2792" id="idexample_1_2792"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2825" id="idexample_1_2825"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <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/"
@@ -1998,14 +2036,67 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2798" id="iddiv3_1_2798"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2831" id="iddiv3_1_2831"/>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>.
In particular, if an event source has Notification WSDL then it
SHOULD be referenced from the wse:EventSource policy assertion.
</p></div></div></div><div class="div1">
-<h2><a name="Schema" id="Schema"/>B XML Schema</h2><p>
+<h2><a name="VerificationEvent" id="VerificationEvent"/>B Verification Event</h2><p>
+ As described in <a href="#GetStatus"><b>4.3 GetStatus</b></a>, a verification request
+ tests the ability of the event source to successfully transmit a
+ notification to the event sink. A notification of the 'verification event'
+ is used in this test.
+ </p><div class="div2">
+<h3><a name="iddiv2_1_2848" id="iddiv2_1_2848"/>B.1 EventDescription for the Verification Event</h3><p>
+ The verification event is described by the following EventDescription.
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wsevd:EventDescriptions
+ xmlns:wsevd='http://www.w3.org/2002/ws/ra/edcopies/ws-evd'
+ targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'
+ xmlns:xs='http://www.w3.org/2001/XMLSchema'
+ xmlns:wse='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+
+ <wsevd:types>
+ <xs:schema targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+ <xs:include schemaLocation='http://www.w3.org/.../eventing.xsd'/>
+ <xs:element name='Verification' type='wse:VerificationEventType'/>
+ </xs:schema>
+ </wsevd:types>
+
+ <wsevd:eventType name='VerificationEvent'
+ element='wse:Verification'
+ actionURI='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/Verfication'/>
+</wsevd:EventDescriptions></pre></div></div></div><div class="div2">
+<h3><a name="iddiv2_1_2857" id="iddiv2_1_2857"/>B.2 Notification WSDL for the Verification Event</h3><p>
+ The verification event is described by the following Notification WSDL.
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
+ xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
+ targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'
+ xmlns:xs='http://www.w3.org/2001/XMLSchema'
+ xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
+ xmlns:tns='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+
+ <wsdl:types>
+ <xs:schema targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-evt'>
+ <xs:include schemaLocation='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/eventing.xsd'/>
+
+ <xs:element name='Verification' type='wse:VerificationEventType'/>
+ </xs:schema>
+ </wsdl:types>
+
+ <wsdl:message name='VerificationMsg'>
+ <wsdl:part name='part1' element='wse:Verification'>
+ </wsdl:message>
+
+ <wsdl:portType name='VerificationPortType'>
+ <wsdl:operation name='VerificationOp'>
+ <wsdl:input message='tns:VerificationMsg'
+ wsam:Action='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/Verification'/>
+ </wsdl:operation>
+ </wsdl:portType>
+</wsdl:definitions></pre></div></div></div></div><div class="div1">
+<h2><a name="Schema" id="Schema"/>C XML Schema</h2><p>
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
@@ -2181,6 +2272,15 @@
<xs:element name='GetStatus'>
<xs:complexType>
<xs:sequence>
+ <xs:element name='Verify' minOccurs='0'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax'
+ maxOccurs='unbounded'/>
+ </xs:sequence>
+ <xs:anyAttribute namespace='##other' processContents='lax' />
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -2194,6 +2294,15 @@
<xs:sequence>
<xs:element name='GrantedExpires' type='tns:MiniExpirationType'
minOccurs='0' />
+ <xs:element name='VerificationInitiated' minOccurs='0'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax'
+ maxOccurs='unbounded'/>
+ </xs:sequence>
+ <xs:anyAttribute namespace='##other' processContents='lax' />
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -2347,7 +2456,7 @@
</xs:complexType>
</xs:element>
</xs:schema></pre></div></div></div><div class="div1">
-<h2><a name="WSDL" id="WSDL"/>C WSDL</h2><p>
+<h2><a name="WSDL" id="WSDL"/>D WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a>
description can be retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/eventing.wsdl">http://www.w3.org/2002/ws/ra/edcopies/ws-evt/eventing.wsdl</a></pre></div></div><p>
@@ -2459,7 +2568,7 @@
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
-<h2><a name="wrappedWSDL" id="wrappedWSDL"/>D WSDL for Standard Wrapped Delivery</h2><p>
+<h2><a name="wrappedWSDL" id="wrappedWSDL"/>E WSDL for Standard Wrapped Delivery</h2><p>
If an event subscriber specifies the wrapped event delivery format
http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Wrap
in the Subscribe request message, then the event sink MUST implement
@@ -2501,7 +2610,7 @@
</operation>
</portType>
</definitions></pre></div></div></div><div class="div1">
-<h2><a name="actiontables" id="actiontables"/>E Action Tables</h2><p>
+<h2><a name="actiontables" id="actiontables"/>F Action Tables</h2><p>
The purpose of the action tables is to illustrate, via a separate means
from the normative text, the allowable order and interactions of various
messages and activities. The action tables are not intended to constrain
@@ -2527,7 +2636,7 @@
</p></li><li><p>
Empty box indicates that the spec is silent for the specified
trigger/action pair.
- </p></li></ul><table border="1"><caption>Table E-1: Event Source Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td colspan="3" align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
+ </p></li></ul><table border="1"><caption>Table F-1: Event Source Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td colspan="3" align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
Subscribe Request <br/>
[msg] </code></td><td valign="top"><code>
Create subscription<br/>
@@ -2537,7 +2646,7 @@
Event<br/>
[app] </code></td><td valign="top"><code>
Send notification to all pertinent subscriptions<br/>
- {<a href="#Notifications"><b>5</b></a>}</code></td></tr></tbody></table><p/><table border="1"><caption>Table E-2: Subscription Manager Action Table</caption><tbody><tr><td rowspan="2" valign="bottom"><b>Trigger</b></td><td colspan="2" align="center"><b>Action</b></td></tr><tr><td><b>Trigger refers to a valid subscription</b></td><td><b>Trigger refers to an invalid subscription</b></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#Notifications"><b>5</b></a>}</code></td></tr></tbody></table><p/><table border="1"><caption>Table F-2: Subscription Manager Action Table</caption><tbody><tr><td rowspan="2" valign="bottom"><b>Trigger</b></td><td colspan="2" align="center"><b>Action</b></td></tr><tr><td><b>Trigger refers to a valid subscription</b></td><td><b>Trigger refers to an invalid subscription</b></td></tr><tr><td valign="top" nowrap="true"><code>
Renew Request<br/>
[msg] </code></td><td valign="top" nowrap="true"><code>
Update expiration timer<br/>
@@ -2548,6 +2657,8 @@
GetStatus Request<br/>
[msg] </code></td><td valign="top" nowrap="true"><code>
Send GetStatusResponse<br/>
+ If (Verify requested)<br/>
+ Initiate verification test<br/>
{<a href="#GetStatus"><b>4.3</b></a>}</code></td><td valign="top" nowrap="true"><code>
Generate UnknownSubscription Fault<br/>
{<a href="#GetStatus"><b>4.3</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
@@ -2568,7 +2679,7 @@
If (EndTo engaged)<br/>
Send SubscriptionEnd<br/>
Invalidate subscription<br/>
- {<a href="#Subscribe"><b>4.1</b></a>}</code></td><td valign="top" nowrap="true"><code/></td></tr></tbody></table><p/><table border="1"><caption>Table E-3: Event Sink Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#Subscribe"><b>4.1</b></a>}</code></td><td valign="top" nowrap="true"><code/></td></tr></tbody></table><p/><table border="1"><caption>Table F-3: Event Sink Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
Expiration<br/>
[timer] </code></td><td valign="top" nowrap="true"><code>
Invalidate subscription<br/>
@@ -2577,7 +2688,7 @@
[msg]</code></td><td valign="top" nowrap="true"><code>
Invalidate subscription<br/>
{<a href="#SubscriptionEnd"><b>4.5</b></a>}</code></td></tr></tbody></table></div><div class="div1">
-<h2><a name="changelog" id="changelog"/>F Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
+<h2><a name="changelog" id="changelog"/>G Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
@@ -2697,4 +2808,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9675">9675</a></td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</a></td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9701">9701</a></td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702">9702</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=9702">9702</a></td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Thursday, 13 May 2010 22:39:23 UTC