Committee Specifications for ebXML Messaging Service (ebMS) Version 2.0

New Committee Specifications from the ebXML Implementation, Interoperability and Conformance (IIC) Technical Committee

Billerica, MA, USA. May 13, 2003.

In April 2003, the ebXML Implementation, Interoperability and Conformance (IIC) Technical Committee (TC), under the Organization for the Advancement of Structured Information Standards (OASIS), has approved the following committee specifications for the ebXML Messaging Service (ebMS) version 2.0:

ebXML Test Framework Document, Version 1.0
ebXML Messaging 2.0 Basic Interoperability Profile (BIP) Test Suite, version 1.0
ebXML Deployment Guide Template for ebXML Messaging 2.0, Version 1.0
EAN.UCC (European Article Numbering / Uniform Code Council) Deployment Guide 1.0, an instance of the ebXML Messaging Deployment Template 1.0 for ebXML Messaging Service Specification 2.0

The initial ebXML IIC efforts have focused on providing a computable and extensible test framework with ebMS as the first edition of the suite of test specifications. Plans are under consideration for CPP/A (Collaboration Protocol Profile and Agreement), Business Process Specification Schema (BPSS) and Registry/Repository (Reg/Rep).

The Test Framework can be used to support conformance testing and interoperability testing in different configurations, from point-to-point testing between business partners, to centralized configurations involving a test center. eBusiness partners can download necessary components. Tests can be driven either by one of the partners, or by a test center, which can be viewed as a service. Or, for interoperability tests, a test center can be used as a hub, providing monitoring and routing functions, while tests are driven from an end-point. In both cases, the test will be executed in an automated fashion. Test traces and results are generated for a collection of test (test suites) for later review.

Key technical features of the Test Framework are:

Tests against profile requirements.
Uses an open XML test scripting language.
Supports construction and examination of MIME (Multi-purpose Internet Mail Extensions), SOAP (Simple Object Access Protocol), and ebXML message content.
Uses a persistent message store for query of synchronously and asynchronously received messages.
Generates XML test reports that trace to test requirements and reference specification.

The first interoperability test suite from the IIC, the Basic Interoperability Profile test suite for ebMS, has been designed after a careful analysis of the requirements and constraints of the current users communities in US, Asia and Europe. The test suite has been, engineered to support various types of test environments that a test center will host, including full matrix, interim, on-demand, and/or content validation testing.

The Deployment Guide Template can help foster interoperability among industry organizations and other trading communities. For example, EAN.UCC (European Article Numbering/Uniform Code Council) is using the template to produce Deployment Guides that reflect specific deployment requirements of their users.

These efforts are also effectively laying the groundwork for cohesive testing opportunities between web services and business service integration. In addition, ebXML IIC is actively working with eBES Interoperability Pilot, Asia Interoperability Task Group through ebXML Asia Committee, KorBIT (Korea), and the B2B Interoperability Testbed (OAG-NIST sponsorship).

The committee specifications can be found at: http://www.oasis-open.org/committees/documents.php?wg_abbrev=ebxml-iic. Parties interested in the IIC work, particularly those who wish to develop a reference implementation or to define a deployment template instance, should contact the ebXML IIC team.

Acknowledgements

ebXML IIC team, with Jacques Durand, TC Lead
Michael Kass, Serm Kulvantunyou, and Nenad Ivezic, NIST
Pete Wenzel, SeeBeyond, Deployment Guide Template
Steven Yung, Sun Microsystems, ebXML BIP

Source: Monica J. Martin; email monica.martin@sun.com

Prepared by Robin Cover for The XML Cover Pages archive. See additional details in the news story "OASIS TC Approves Test Framework Documents for ebXML Messaging Service (ebMS) Version 2.0." General references in "Electronic Business XML Initiative (ebXML)."

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	Committee Specifications for ebXML Messaging Service (ebMS) Version 2.0 New Committee Specifications from the ebXML Implementation, Interoperability and Conformance (IIC) Technical Committee Billerica, MA, USA. May 13, 2003. In April 2003, the ebXML Implementation, Interoperability and Conformance (IIC) Technical Committee (TC), under the Organization for the Advancement of Structured Information Standards (OASIS), has approved the following committee specifications for the ebXML Messaging Service (ebMS) version 2.0: ebXML Test Framework Document, Version 1.0 ebXML Messaging 2.0 Basic Interoperability Profile (BIP) Test Suite, version 1.0 ebXML Deployment Guide Template for ebXML Messaging 2.0, Version 1.0 EAN.UCC (European Article Numbering / Uniform Code Council) Deployment Guide 1.0, an instance of the ebXML Messaging Deployment Template 1.0 for ebXML Messaging Service Specification 2.0 The initial ebXML IIC efforts have focused on providing a computable and extensible test framework with ebMS as the first edition of the suite of test specifications. Plans are under consideration for CPP/A (Collaboration Protocol Profile and Agreement), Business Process Specification Schema (BPSS) and Registry/Repository (Reg/Rep). The Test Framework can be used to support conformance testing and interoperability testing in different configurations, from point-to-point testing between business partners, to centralized configurations involving a test center. eBusiness partners can download necessary components. Tests can be driven either by one of the partners, or by a test center, which can be viewed as a service. Or, for interoperability tests, a test center can be used as a hub, providing monitoring and routing functions, while tests are driven from an end-point. In both cases, the test will be executed in an automated fashion. Test traces and results are generated for a collection of test (test suites) for later review. Key technical features of the Test Framework are: Tests against profile requirements. Uses an open XML test scripting language. Supports construction and examination of MIME (Multi-purpose Internet Mail Extensions), SOAP (Simple Object Access Protocol), and ebXML message content. Uses a persistent message store for query of synchronously and asynchronously received messages. Generates XML test reports that trace to test requirements and reference specification. The first interoperability test suite from the IIC, the Basic Interoperability Profile test suite for ebMS, has been designed after a careful analysis of the requirements and constraints of the current users communities in US, Asia and Europe. The test suite has been, engineered to support various types of test environments that a test center will host, including full matrix, interim, on-demand, and/or content validation testing. The Deployment Guide Template can help foster interoperability among industry organizations and other trading communities. For example, EAN.UCC (European Article Numbering/Uniform Code Council) is using the template to produce Deployment Guides that reflect specific deployment requirements of their users. These efforts are also effectively laying the groundwork for cohesive testing opportunities between web services and business service integration. In addition, ebXML IIC is actively working with eBES Interoperability Pilot, Asia Interoperability Task Group through ebXML Asia Committee, KorBIT (Korea), and the B2B Interoperability Testbed (OAG-NIST sponsorship). The committee specifications can be found at: http://www.oasis-open.org/committees/documents.php?wg_abbrev=ebxml-iic. Parties interested in the IIC work, particularly those who wish to develop a reference implementation or to define a deployment template instance, should contact the ebXML IIC team. Acknowledgements ebXML IIC team, with Jacques Durand, TC Lead Michael Kass, Serm Kulvantunyou, and Nenad Ivezic, NIST Pete Wenzel, SeeBeyond, Deployment Guide Template Steven Yung, Sun Microsystems, ebXML BIP Source: Monica J. Martin; email monica.martin@sun.com Prepared by Robin Cover for The XML Cover Pages archive. See additional details in the news story "OASIS TC Approves Test Framework Documents for ebXML Messaging Service (ebMS) Version 2.0." General references in "Electronic Business XML Initiative (ebXML)."