By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
The RosettaNet focus is to standardize business processes in specific areas of business (industry verticals) like the semiconductors business, electronic components business etc. When RosettaNet was first formed in 1998, it needed a whole bunch of infrastructure pieces to deliver on its vision of standardized e-business processes. While these infrastructure pieces (like the messaging packaging and routing framework, and the business process modeling language) were necessary at the time, as RosettaNet was a pioneer in e-business processes, they are not part of the strategic vision of RosettaNet.
As other e-business standards emerged, RosettaNet has remained flexible and seeked convergence where possible. It is because of this flexibility that overlapping efforts like ebXML, that could have been potentially adversarial, are instead seen as a boost to RosettaNet. RosettaNet is currently in the process of adopting the ebXML Registry and Repository specifications, the ebXML BPSS (business process specification schema), the ebMS (messaging services), and the CPPs (the partner profiles).
In the future, it is not entirely inconceivable that RosettaNet could converge with other e-business standards as well.
RosettaNet's maturity comes from billion of dollars worth of real e-business being conducted by business partners using RosettaNet specifications. While ebXML and Web services are relatively new and have few implementations to boast of, RosettaNet has remained focused on standardizing e-business processes and enabling business partners to conduct them. This has lead to further RosettaNet adoption in Europe, and Asia.
RosettaNet is not in competition with the horizontal e-business standards like ebXML or Web services. Actually, RosettaNet benefits from the horizontal standards, as they enable RosettaNet to concentrate its efforts on standardizing e-business processes, by no longer having to develop and maintain infrastructure pieces that can be adopted from horizontal standards like ebXML.
Dig Deeper on Business process modeling and design
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.