What's the relationship between universal Web Service standards (such as SOAP, WSDL, UDDI) and e-business initiatives like ebXML, RosettaNet, and cXML? Is this something companies have to consider when planning a Web Services strategy?
They are very different, albeit important standards. Web service standards, which I covered in detail in this article defines a standard infrastructure for locating and invoking remote application services, within and between organizations. This is a primitive set of standards, really an approach to application development, similar to older standards such as distributed objects and component-based programming, but easier to understand and deploy. This site is the best place to find out all there is to know about Web services.
The ebXML, RosettaNet and to a lesser extent cXML standards, generally speaking, relate to, how information moves between companies, including format and process.
The ebXML standard is an XML-based "collaboration" standard, defining how to map and invoke processes as well as how information moves under the covers. Most B2B application integration solutions will leverage ebXML. EbXML is a joint venture between the United Nations body for Trade Facilitation and Electronic Business, and OASIS (Organization for the Advancement of Structured Information Standards), developing a framework for using XML to exchange business data with visibility into common processes. You can get more information at www.ebxml.org.
RosettaNet is a set of standard mechanisms, processes really, that allows companies to come to an agreement on the processing of standard business transactions. Since RosettaNet is about processes rather than data, the most important aspect of RosettaNet is the development of common Partner Interface Processes (PIPs) and common dictionaries. RosettaNet provides a master dictionary to define properties for products, partners, and business transactions. This master dictionary, coupled with an established implementation framework, can be used to support the B2B application integration dialog (PIPs). PIPs provide alignment within the overall supply-chain process, allowing businesses to interact at a number of levels to support the processes of common trading communities.
cXML provides an infrastructure that will streamline the process of digitally exchanging catalog content and transactions in a secure manner. cXML supports all supplier content and catalog models, including buyer-managed, supplier-managed, content management services, electronic marketplaces, and web-based sourcing organizations. Moreover, cXML defines a request/response process for the exchange of transaction information.
Dig Deeper on Topics Archive
Related Q&A from David Linthicum
David Linthicum explains what advanced business application programming (ABAP)/4 means. Continue Reading
David Linthicum defines Service Component Architecture (SCA) and Service Data Objects (SDO) and explains how to best build these components to enable... Continue Reading
David Linthicum explains how it is possible that Apache Tomcat is both a Web server and an application server. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.