Tom Glover is providing a nearly real time exposition of the work going on in the Web Services Interoperability Organization this week in Salt Lake City, Utah. One of the big topic is RAMP, or the Reliable Asynchronous Messaging Protocol work that Tom and I blogged about a few weeks ago. I recommedn you take a look at these recent posts of Tom's to come up to speed on this important development:
- Next Steps for WS-I: Interoperable Reliable Asynchronous Messaging
- WS-I ponders asynchrony and reliability
- WS-I ponders asynchrony and reliability (end of day 1)
We'll know tomorrow if we have the board super-majority (nine of ten) support necessary to accomplish the re-charter and to create the new working group.Will it happen? Will someone try to block this? Will it be unanimous? Check back tomorrow.
Meanwhile, both Tom and I are quoted in this story by CNET's Martin LaMonica: "Group eyes standard Web services messaging". (One slight correction: I said I was surprised in 1999 that so many industry standards organizations spent so much time on low level messaging work rather than on high level, industry-specific formats.)
ZapThink's Ron Schmelzer raised the very important transparency issue:
He recommended that members of the WS-I act very transparently in how they arrive at the profile, which will be useful to customers.
"I don't think people care as much about the profile as they care about the process of how they got to the profile," Schmelzer said. "As a customer, I can make decisions based on what they're doing, and I can see the direction they're going in."