WS-Eventing Optionality Analysis
Version
1.1 -
Optionality: required for event sources
Sub-Elements/Features:
wse:EndTo
optional for subscribers, optional for event sources
potentially at-risk
wse:Delivery
required for subscribers, required for event sources
wse:NotifyTo
optional for subscribers, required for event sources
wse:Format
optional for subscribers, optional for event sources
implied value is "http://www.w3.org/2010/08/ws-evt/DeliveryFormats/Unwrap"
potentially at-risk
wse:Expires
optional for subscribers, optional for event sources
potentially at-risk
The linkage of this element with the same sub-element of the wse:Renew message is unclear. Common sense would seem to dictate that, if an event source supports the use of this element, the subscription manager referenced by wse:SubscribeResponse/wse:SubscriptionManager must support wse:Renew/wse:Expires – but the WS-Eventing specification is silent on this matter.
xs:duration
optional for subscribers, required for event sources
xs:dateTime
optional for subscribers, optional for event sources
@BestEffort
optional for subscribers, required for event sources
wse:Filter
optional for subscribers, optional for event sources
potentially at-risk
@Dialect
optional for subscribers (default/implied value is "http://www.w3.org/2010/08/ws-evt/Dialects/XPath10"), event sources are not required to support any particular value – including the default
Optionality: linked to the use of wse:Subscribe
Sub-Elements/Features:
wse:SubscriptionManager
required for event sources, required for subscribers
wse:GrantedExpires
linked to the use of wse:Subscribe/wse:Expires
Optionality: required for subscription managers.
Note that support for this operation is required even in cases where the event source/subscription manager doesn't support any notion of subscription expiration; the Renew operation is effectively a no-op for such implementations.
Sub-Elements/Features:
wse:Expires
optional for subscribers, optional for subscription managers
potentially at-risk
The linkage of this element with the same sub-element of the wse:Subscribe message is unclear. Common sense would seem to dictate that, if a subscription manager supports the use of this element, the event source to which the original Subscribe request was targeted must support wse:Subscribe/wse:Expires – but the WS-Eventing specification is silent on this matter.
xs:duration
optional for subscribers, required for subscription managers
xs:dateTime
optional for subscribers, optional for subscription managers
@BestEffort
optional for subscribers, required for subscription managers
Optionality: linked to the use of wse:Renew
Optionality: required for subscription managers
Optionality: linked to the use of wse:GetStatus
Sub-Elements/Features:
wse:GrantedExpires
linked to the use of wse:Subscribe/wse:Expires and wse:Renew/wse:Expires
Optionality: required for subscription managers
Optionality: linked to the use of UnsubscribeResponse
Optionality: optional for subscribers, optional for subscription managers
linked to the use of/support for wse:Subscribe/wse:EndTo
potentially at-risk
Sub-Elements/Features:
wse:Status
required for subscription managers
wse:Reason
optional for subscription managers, optional for subscribers
potentially at-riskona