Overheard at the lair of one familias. You see Jimmy, it's like dis. We had to bring the two families together. It was bad for business. So we arranged two marriages. Of course, it's the modern day so everybody wanted to keep their names. Names have a certain gravitas. When the Eventing family took over I mean married the Notification family, naturally they both changed their names to WS-EventingNotification. Or was it WS-NotificationEventing?
Anyways, that's not important. Another blood line was united when the Resources and Transfers got together. They are called WS-ResourceTransfer. We had wanted State in there, for WS-REsourceStateTransfer, but they didn't want to change the polygamy rules.
This is part of a long term plan. We have a few more blood lines to unite. The Security and Conversation families have already been united in WS-SecureConversation, but they have to join with Reliability for WS-ReliableSecureConversation. We also need MetadataExchange and Policy to join, as well as WS-TransactionEnumeration.
Then, in about two WS-years, the WS-KwisatchHadarach will be born! He will be known as
WS-ReliableSecureConversationEventingNotificationMetadataExchangePolicy ResourceTransferTransactionEnumeration.
You will know him because he will have drunk the water of life and will control all transactions in the galaxy.
