| The ebXML standard, like other standards, is really all about making sure that everyone does things in the same way; thus, there is a need to lay down the law in terms of what it means to be ebXML compliant. Conformance to ebXML is defined in terms of conformance to the ebXML infrastructure and the technical specifications. The idea is that, if everyone is doing ebXML in the same way, they can exchange information and processes without having to do much extra work. Thus, conformance is defined as conformance to an ebXML system that is comprised of all architectural components of the ebXML infrastructure satisfying the minimum conformance requirements.[2] This includes functional and interface requirements in the specification, in particular: [2] ebXML Technical Architecture Specification, 2001; www.ebXML.org.
You shall support all of the functional and interface requirements. You shall not specify any requirements that would contradict or cause nonconformance. You may contain a conformance clause that adds requirements that are more specific. You shall only contain requirements that are testable.[3] [3] Ibid.
ebXML and UDDI The relationship between ebXML and UDDI shows how ebXML joins the fast-moving world of Web services. UDDI is a lot like ebXML's Repository, with the fundamental difference being that UDDI aims to create a standard registry for enterprises that seek to leverage common reusable Web services, while ebXML looks to standardize how XML is used in general-purpose process-based B2B integration. The essence of the UDDI model therefore focuses on middleware connectivity using Web services, and using XML only to describe the systems that are available for access using a Web services interface. UDDI does this by maintaining information about the remote services, including profiles and capabilities. This is put into a shared directory that is globally accessible. There are three types of information that are tracked by UDDI: white, yellow, and green pages. The white pages directory allows enterprises to register their names and key services they expose, and whether they will allow other entities to locate and access these services. The yellow pages component of the directory categorizes companies by codes (NAICS, United Nation/SPSC codes, and location). The green pages contain information about how companies interface with other companies in the registry using XML. Early on, those creating the ebXML standard and UDDI standard began to make each standard interoperable, integrating ebXML to UDDI. Considering that there is much overlap in the capabilities of each, some are confused as to why two standards must exist. Clearly, they will morph together over time. Indeed, over the next few years, UDDI aims to expand its number of categories and add more complete features to assist in the searching of services within its repository. |
|
