Network Deployment (Distributed operating systems), v8.0 > Reference > Developer best practices
WS-Notification terminology
There is terminology that be aware of when working with WS-Notification. Most of this terminology is defined by the WS-Notification standards, and a few terms are defined to describe this implementation of WS-Notification for WAS.
This topic and its subtopics describe the terminology that be aware of when working with WS-Notification in WAS:
- Terminology from the WS-Notification standards describes terms that are defined by the WS-Notification standards, and relates to the standardized concepts used by WS-Notification.
- WAS-specific WS-Notification terminology describes terms and concepts that have been defined to describe this implementation of WS-Notification for WAS.
The WS-Notification standards define a TopicNamespace as a grouping of topic trees for administrative purposes. Service integration technologies defines a similar term topic space as a destination used for publish and subscribe messaging. Although these concepts are similar, they are not identical. For example it is possible for there to be a 1-1 relationship between a WS-Notification topic namespace and a service integration bus topic space, but in many situations this is not the case. See Options for associating a permanent topic namespace with a bus topic space.
- Terminology from the WS-Notification standards
The terminology defined in this topic is defined by the WS-Notification specifications and is common to any vendor implementation of these specifications.
- WAS-specific WS-Notification terminology
This terminology is implementation-specific, over and above the terminology defined in the WS-Notification standards, and applies to the WS-Notification implementation in WAS.
WS-Notification
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Related
WS-Notification troubleshooting tips