A number of OASIS technical committees have been very busy over the past few months, with the result that OASIS has just announced the release of a number of updated standards:
Specification Title: Web Services MakeConnection 1.1
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00006.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1638
Specification Title: Web Services ReliableMessaging Policy 1.2
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00007.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1639
Specification Title: Web Services ReliableMessaging 1.2
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00008.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1640
Specification Title: WS-SecurityPolicy 1.3
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00000.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1632
Specification Title: WS-SecureConversation 1.4
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00001.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1633
Specification Title: WS-Trust 1.4
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00002.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1634
Specification Title: WS-BusinessActivity v1.2
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00003.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1635
Specification Title: WS-AtomicTransaction v1.2
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00004.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1636
Specification Title: WS-Coordination v1.2
Submission Notification: http://lists.oasis-open.org/archives/tc-announce/200901/msg00005.html
Ballot: http://www.oasis-open.org/committees/ballot.php?id=1637
We've spoken about a number of these standards in the past, most notably when we spoke with Eric Newcomer on the importance of transactions and Web Services, where he had this to say on WS-BA:
We are seeing new requirements for combining reusable services as the trend toward SOA grows. Web services allow you to abstract any type of software system behind a service description — synchronous RPC, asynchronous messaging, database management, or packaged application. Each of these may have a different transactional style or model that may also need to be abstracted in order to obtain reusability for transactional services. Current transactional models tend toward synchronous, and we are seeing a trend in SOA and elsewhere toward an emphasis on asynchronous (e.g. loosely coupled) processing. We are also seeing a trend toward including services "on the Web" into enterprise applications, and these services are not deployed within a company’s controlled environment. So for a lot of reasons, and due to a number of significant new pressures that are creating different relationships among application components, and creating new types of abstractions, I think we will see the emergence of new transactional models. One example is compensation, which is starting to gain more adoption than in the past.
No doubt we'll see them adopted in subsequent releases of Web Services stacks from vendors and open source projects.
