Comparison of EBXML, UDDI and XML / EDI
(Red) Chainive Road (Fennive@uddi-china.org) Chief System Architect introduced the application tool for developing open shared interactive e-commerce in the past nearby The development of technical specifications is very rapid, and the prospect is also quite broad. This work is completely technical based on the XML specification of W3C and related standard Internet technology. In this regard, EBXML's aim is to develop an infrastructure based on open XML standard-based e-commerce. With the extensive application of EBXML, it has expanded a unified global electronic trading market, so that each Members join the EBXML system can achieve global general e-commerce information interactions in a safe and standardized coordinated environment. The primary purpose of EBXML is to try to eliminate the obstacles encountered on the road to e-commerce, so that they have been trade with each other, so they have received high concerns from small and medium-sized enterprises and developing countries. EBXML is initiated by UN / CEFACT, OASIS, which is developed by an open community with thousands of supporters and participants, of course, including UN / CEFACT and OASIS. Unified description, discovery, discovery, discovery and integration, uddi, is a program launched by IBM, ARIBA, and Microsoft to facilitate interoperability of commercial web services 10 months ago, in accordance with UDDI specifications The UDDI Registry of the Architecture will serve as a distributed place for business information in the Internet in Internet, and he provides business information registration with three levels of service registration for Yellow Pages / White / Green. UDDi's core competitiveness is to provide better means of managing their supply and marketing business networks for all sizes, especially large institutions, and more channels to contact potential business partners. The problem facing UDDI is how to cause merchants to take the initiative to enter the UDDI registration center and publish their own information, and how to make the service information released by the user can be upgraded, and can include the release of the implementation details. In contrast to the previous two specification-based specifications, XML / EDI. XML / EDI has been developed three years ago, which is a technology growth point that is initiated from the private and promoting XML in e-commerce. XML / EDI itself fuses five concepts: XML, EDI, Repository, Template and Agent, which also creates common cornerstone of next-generation e-commerce. EBXML and UDDI also reflect the viewpoint of XML / EDI, because they are the norms and techniques that emerged for the development of next-generation e-commerce, they are the same as XML / EDI purposes. In the following we have a comparison of the three, we will see how they achieve the commitment of XML and e-commerce. Ebxml In order to understand the technical system of EBXML, it is essential to understand the concept of ideological concepts of its connotation at the beginning. From the beginning, the design of the technical architecture is based on the real business processes, from various business processes to make universal commercial objects such as: address, groups, and venues. The appearance of XML makes it possible to use XML elements / attributes that can be very easy to define and identify these objects, and can perform free operations for these objects. A basic goal of the EBXML program is to make the company that uses EBXML companies to create a uniform uniform business interaction standard by using these predefined business objects. Currently, EBXML architecture mode uses two views to describe all business interactions, which produces early work: OPENEDI.
The first is a business operation view (Bov, Business Operational View), which is directed for the semantics of business data transactions, and the relevant data exchange, the business transaction system includes processing including operational agreements, protocols, and mutual need to bear the obligations and requirements. The actual use of these specific business specifications requires the same support or trade assistant using EBXML. UDDI has previously announced the unified description, discovery and integration, discovery and integration, and uddi. In addition to the above three founding companies, many other companies have signed an agreement to join the UDDI to formulate a working group, and pay attention to the development of such a norm that focuses on directory services and enterprise systems. Interestingly, these companies, such as IBM, Sun, and other companies that participate in UDDI programs, in the early morning, I have agreed to support EBXML and prepare for EBXML solutions to customers, they are in EBXML solutions, with many standardized organizations such as Oasis. Cefact and W3C have this close cooperation. So, what is the difference between UDDI and EBXML? They seem to be global technical specifications in the B2B field? In fact, UDDL and EBXML's most basic difference is that UDDI is for the establishment of a standard registry (Registry) to accelerate the integration of enterprise-level application systems under the electronic trading market at the network environment, while EBXML goals Mainly, how to standardize how XML is applied to a general enterprise inheritance of the company (B2B) system. That is to say, in a sense, UDDI mainly facing the standard of the infrastructure, and EBXML is mainly for the standards for information interaction. The core of the UDDI model is more concerned about the middleware connection, while using XML to describe the system interface that interacts with other companies used by the company. UDDI uses a shared directory to store the enterprise interface description and corresponding service functions that are integrated with each other, and all access interfaces are described by XML. In XML, EBXML defines the XML description format of business processes and business objects, while UDDI mainly pays attention to the XML description of the service interface. From this point, we can think that UDDI should be under EBXML in the system architecture. Ebxml and UDDI understand and compare the technical level of EBXML and UDDI and each other, and we believe that you have already understood that in the B2B e-commerce field, both are absolutely in different technical levels. Only if only two, the UDDI is the underlying information registration framework, and EBXML is a technical specification used in the information registration framework. That is to say, UDDI defines the information description framework of B2B technology, and EBXML specifies a B2B technical specification. The traditional EDI of XML / EDI has proven that he has considerable feasibility and effectiveness in handling e-commerce, but his limitations are also obvious. For small business partners, they are required to bear expensive integration costs and Deployment cost is almost impossible. Therefore, the goal of XML / EDI is to make these companies to build a fast, cheap, maintainable business system-oriented business system. XML / EDI allows other trading partners to not only use traditional EDI data, but also better handle control templates and business rules through new value-added services, and ultimately complete the needs of each other's system transaction synchronization. Conclusion After comparing UDDI, EBXML and XML / EDI, we are not difficult to see, although everyone has registry / repository, but their use goals are different, although they all use XML format as a means of information, But the levels of the information they describe are also different.
