Regardless of who devises the framework, such standards usually include business document formats, messaging protocols, and process workflows that must be adhered to in order to participate in the framework. As such, frameworks are closed systems. Occasionally you will find a vendor offering limited interoperability between frameworks, but this is the exception. In embracing a framework, you are supposedly gaining ease of implementation and interoperability in exchange for closing yourself off from customers and partners who do not embrace the framework. The problem with frameworks is that no one framework ever sweeps aside its competitors.
Any successful framework is the best fit for some customer.
If you want the broadest possible access to your potential market, you cannot close yourself off from other frameworks. Regardless of the technology decisions you make, you will need to deal with alternative technologies. The marketplace is too large and too fluid for agreement to be reached on a single technology at any layer. Your e-business system must be capable of handling translations between data formats, communications protocols, and security mechanisms on an ad hoc basis. Similarly, if any of your partners settle on a standard at the process layer, you must be capable of interoperating with them.