How does this work compare with related efforts at other standards organizations?

This work presumes that exchanges of business information in business collaborations will tend to be conducted in relatively static modes, with slowly changing configurations. Options and functionality will be deliberately changed, rather than dynamically reconfigured on a message-by-message basis. It also presumes that many businesses will be interested in monitoring the "messaging communications channel" parameters to see that agreed-upon levels of compliance and performance are maintained. It is also problematic how enthusiastically extremely dynamic modes of configuration (spontaneous collaboration) will be embraced by those interested in verification of agreed upon-behavior in business collaboration. Finally, the Negotiation protocol is to provide a highly automatic way to set up agreements for collaboration protocols, largely realizing the business advantages (lower management costs) promised by highly dynamic ("spontaneous") collaboration technologies.

In addition, many businesses tend to confine the supported technical interactions to the smallest number of profiles permitting secure and reliable connectivity. Security, reliability, diagnostic visibility, and change management are core concerns for business collaboration protocols, but are either neglected or specialized topics in basic technology or general purpose web services standards organizations. Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I