WSN - Summary of changes since last Public Review

 

May 31st, 2006

Table of Contents

Introduction

Issue WSN2.64: Action URI for raw notifications

Issue WSN2.65: Removal of compulsion surrounding DestroyPullPoint

Issue WSN2.66: Inconsistent requirement to support WSRF-ResourceLifetime immediate termination

Issue WSN2.67: Pull-style notification faults

Issue WSN3.30: Inconsistent lifetime-related Resource Property declarations

Issue WSN3.31: Mutability of PublisherRegistration properties

Issue WSN4.29: Number of times an ExtensionTopic should appear in a Topic Set

Miscellaneous WS-BaseNotification changes

Miscellaneous WS-BrokeredNotification changes

Introduction

This document summarizes the significant changes made to the WS-Notification draft specifications since their last Public Review (in the case of WS-BaseNotification and WS-BrokeredNotification this means since the second Public Review, in the case of WS-Topics it means since the first Public Review). It does not list editorial changes or corrections.

Issue WSN2.64: Action URI for raw notifications

Text relating to raw notifications has been clarified to indicate that the NotificationProducer SHOULD utilise the Action URI defined for the Notify operation except in situations where the NotificationProducer has knowledge which would cause it to use some alternative URI.

Specifications

        WS-BaseNotification

Issue WSN2.65: Removal of compulsion surrounding DestroyPullPoint

The sentences requiring clients to use DestroyPullPoint have been removed. Clients are free to choose to use either DestroyPullPoint or the WSRF-RL immediate termination message exchange.

Specifications

        WS-BaseNotification

        WS-BrokeredNotification

Issue WSN2.66: Inconsistent requirement to support WSRF-ResourceLifetime immediate termination

SubscriptionManagers that expose subscriptions as WS-Resources are now required to support the WSRF-RL immediate termination message exchange. This brings Subscriptions into line with PullPoints and PublicationRegistrations.

Specifications

        WS-BaseNotification

Issue WSN2.67: Pull-style notification faults

The faults defined for the message exchanges associated with Pull Points have been updated to make them consistent with Subscriptions.

a)      Text has been added to state that GetMessages should only return the ResourceUnknownFault in cases where the PullPoint is a WS-Resource

b)      Added a generic UnableToGetMessagesFault for use by GetMessages in other failure cases

c)      Added ResourceUnknownFault to the list of faults returned by DestroyPullPoint (if the PullPoint is a WS-Resource)

Specifications

        WS-BaseNotification

 

Issue WSN3.30: Inconsistent lifetime-related Resource Property declarations

The BrokeredNotification schema for PR2 contained some incorrect ResourceProperties declarations

<!-- From WS-ResourceLifetime ScheduledResourceTermination -->

940 <xsd:element ref="wsn-b:CurrentTime"

941 minOccurs="0" maxOccurs="1" />

942 <xsd:element ref="wsn-b:TerminationTime"

943 minOccurs="1" maxOccurs="1" />

These have been deleted from the Schema. Implementations that wish to include CurrentTime and TerminationTime ResourceProperties should use the elements declared by WSRF-ResourceLifetime.

Specifications

        WS-BrokeredNotification

Issue WSN3.31: Mutability of PublisherRegistration properties

Made it clearer that a NotificationBroker is not obliged to let users modify the Topic and Demand PublisherRegistration Resource Properties.

Specifications

        WS-BrokeredNotification

 

Issue WSN4.29: Number of times an ExtensionTopic should appear in a Topic Set

Public Review Draft 1 required an extension Topic to appear at least twice in a TopicSet document once as an immediate child of the TopicSet root element, and once as a child of its immediate parent (and additional times if it was the descendent of another extension topic). This has been changed, so that nowt an Extension Topic (or child of an Extension Topic) can only be referenced by using path expressions that include the parent of the Extension Topic. If the dialect permits them, wild card characters can be used so that the Parent Topic name does not need to be included explicitly. As a consequence, Extension Topics can no longer be referenced using Simple Topic Expressions.

        WS-Topics

Miscellaneous WS-BaseNotification changes

The References section has been updated, and a number of corrections have been made to bring the pseudo-schemas and real schema into step with each other:

Miscellaneous WS-BrokeredNotification changes

The References section has been updated, and a number of corrections have been made to bring the pseudo-schemas and real schema into step with each other: