Issue 1.7 in BaseN

[David Hull <dmh@tibco.com>]

The issue is (broadly) a slight bias toward direct and brokered realizations at the expense of other possibilities.  I propose rewording the paragraphs toward the end of the introduction to read:

This specification defines a role called the NotificationProducer. A NotificationProducer accepts incoming Subscribe requests.  Each subscribe request identifies one or more Topics of interest and a reference to a NotificationConsumer. The NotificationProducer ensures that notifications will be delivered to the NotificationConsumer as requested in the Subscribe request, or returns a fault if the subscription cannot be handled.

The distribution of notifications may be realized in a number of ways.  One particular configuration, in which the NotificationProducer redistributes notifications produced by other entities, is described in the [WS-Brokered Notification] specification.

The old text had read:

This specification defines a role called the NotificationProducer. A NotificationProducer accepts incoming Subscribe requests, each subscribe request identifies one or more Topics of interest and a reference to a NotificationConsumer. The NotificationProducer maintains a list of subscriptions (each subscription entry contains the Topic(s), a reference to the NotificationConsumer and possibly additional information). When it has a notification to distribute, the NotificationProducer matches the notification against the interest registered in each Subscription known to it. If it identifies a match it issues the Notification to the NotificationConsumer associated with that Subscription.

[...]

The configuration where a NotificationConsumer is subscribed directly to the NotificationProducer is referred to as the “direct” or “point-to-point” notification pattern. There are other variations of the Notification pattern, where the NotificationConsumer is subscribed to an intermediary NotificationBroker service. These are covered by the [WS-Brokered Notification] specification.