While IBM has proposed a similar spec this month, WS-Notification, devs should not feel the specs will compete or confuse the issue, Ronald Schmelzer, a web services analyst with Zapthink told IDN.

“WS-Eventing is important is because different systems have their own proprietary ways of defining events and sending notifications. WS-Eventing standardizes both,” Ronald Schmelzer, analyst with Zapthink, told IDN. “This would allow a TIBCO system to send notifications to a .NET system, for example. So, somewhat straightforward, but still nonetheless incredibly important for the new class of standards-based, asynchronous, loosely-coupled integration that Web Services and SOAs represent.”

“IBM found that their priorities were for allowing brokers to be present between the event publisher and subscriber, and in addition to support management of the notifications and end points, Zapthink’s Schmelzer told IDN. “Also, IBM wanted to support their Grid initiatives that required notifications to make it work In the long term, companies won’t be faced with having to implement both WS-Eventing and WS-Notifications to make their cross-industry pub/sub work.”

Read more at: Integration Developer News