|
| |
Home page >
About ebXML> The ebXML project
ebXML
electronic business eXtensible Markup Language
Members of UN/CEFACT and
OASIS coordinate the work on ebXML.
Ongoing
development and maintenance of ebXML infrastructure (messaging,
registry/repository, security and collaborative partners work) is conducted
within the OASIS technical process, due to the Consortium's expertise in XML
standards development. Organisations or individuals
interested in the ebXML infrastructure may participate by joining OASIS.
Ongoing development and maintenance of
ebXML business content (core components and business process models) is
conducted within UN/CEFACT due to its vast experience in UN/EDIFACT
EDI standards. Organisations
or individuals interested in the ebXML business content may participate by
becoming a member of UN/CEFACT.
Strong liaison relationships between the
technical committees and working groups are maintained and face-to-face meetings
of all ebXML teams are held on a regular basis.
ebXML has two Committees dedicated
for the management and the promotion of the project.
This working organisation adopted
for the ebXML project is illustrated by the following diagram.
ebXML Diagram
Committees
JCC Joint Coordination Committee
The
ebXML JCC is the management body
responsible for overall supervision of ebXML development, adoption and
implementation. While ebXML specifications are advanced by specific OASIS
technical committees and UN/CEFACT project teams, both standards organizations
remain committed to jointly managing ebXML strategic vision, technical
architecture, and education.
The
ebXML JCC hosts joint meetings, where OASIS technical committees and UN/CEFACT
project teams interface on related issues. The JCC also sponsors educational
events.
Members of the ebXML JCC offer a balanced perspective, representing major Web
services vendors, standards bodies, and government agencies. The committee is
made up of five representatives from each of the sponsoring organizations UN/CEFACT
and OASIS.
JMT Joint Marketing
Team
The ebXML JMT is promoting, communicating and championing ebXML-based solutions
for mission-critical, eBusiness Web services.
OASIS
and UN/CEFACT have formed a Joint Marketing Team (JMT) for ebXML. The JMT
Steering Committee will advance a three-phase marketing plan -- an initial phase
to raise short-term awareness, a mid-term component to bring implementation
knowledge and experience to the marketplace and then a sustaining phase to build
up and maintain an extended ebXML family of users.
This
effort combines resources from OASIS and UN/CEFACT members to provide the
capability to deliver the message across a broad scan of channels. The work is a
large, cooperative member-driven effort through targeted plans in key market
niches.
Projects
Collaborative
Partner
-
Development of ebXML on Collaboration Protocol Profiles (CPPs) and
Collaboration Protocol Agreements (CPAs). A CPP defines one business partner's
technical capabilities to engage in electronic business collaborations with
other partners by exchanging electronic messages. A CPA documents the
technical agreement between two (or more) partners to engage in electronic
business collaboration.
-
Technical specifications: Collaboration-Protocol Profile and Agreement
Specification. This specification contains the detailed definitions of the
Collaboration-Protocol Profile (CPP) and the Collaboration-Protocol Agreement
(CPA).
-
Developed by OASIS ebXML
CPPA Technical Committee,
Implementation
-
Providing a means for software vendors to create infrastructure and
applications which adhere to the ebXML specifications and are able to
interoperate.
-
Technical specifications: Conformance plan, set of reference implementation
guidelines, set of base line interoperability tests, guidelines and direction
for third-party creation of conformance laboratories.
-
Developed by OASIS
ebXML Implementation, Interoperability and Conformance
Technical Committee.
Messaging Services
-
Development and recommendation of technology for the transport, routing and
packaging of business transactions using standard Internet technologies. This
work will foster consistency across specifications developed in other forums
and carry forward the work started in the ebXML Transport, Routing and
Packaging project team.
-
Technical specifications: Message Service Specification. This specification
defines the ebXML Message Service Protocol enabling the secure and reliable
exchange of messages between two parties.
-
Developed by OASIS
ebXML Messaging Services Technical Committee.
Registry
-
Development of specifications to achieve interoperable registries and
repositories, with an interface that enables submission, query and retrieval
on the contents of the registry and repository. Further, the Registry TC seeks
to develop specifications that serve a wide range of uses, covering the
spectrum from general purpose document registries to real-time
business-to-business registries. Additionally, as part of its specification
development work, this TC explores and promotes various emerging models for
distributed and cooperating registries.
-
Technical specifications: OASIS/ebXML Registry Information Model, this
specification defines the information model for the ebXML Registry (what
information is in the Registry and how that information is organized); OASIS/ebXML
Registry Services Specification, this specification defines the interface to
the ebXML Registry Services as well as interaction protocols, message
definitions and XML schema.
-
Developed by OASIS
ebXML Registry Technical Committee.
Technical
Architecture
-
Developed by ebXML Technical Architecture Project Team, this team does not
exist anymore. UN/CEFACT launched a new project dedicated to e-business
architecture. This project should provide input for future revisions of the
existing ebXML Technical Architecture Specification.
-
Technical specifications: ebXML Technical Architecture Specification. This
specification describes the underlying architecture for ebXML. It provides a
high level overview of ebXML and describes the relationships, interactions,
and basic functionality of ebXML. It should be used as a roadmap to learn: (1)
what ebXML is, (2) what problems ebXML solves and (3) core ebXML functionality
and architecture.
Business
process
-
Development of a methodology and set of worksheets and guidelines for creating
models defining interoperable business documents that allow business partners
to collaborate. A business library (catalog) of business process and
information models promotes business efficiency by encouraging reuse of
business processes or parts of predefined business processes.
-
Technical specifications: Business Process Specification Schema. This
specification provides for the nominal set of specification elements necessary
to specify a collaboration between business partners, and to provide
configuration parameters for the partners’ runtime systems in order to execute
that collaboration between a set of e-business software components.
-
Developed by UN/CEFACT Techniques and Methodologies Group, more details can be
found in
http://www.unece.org/cefact/index.htm.
Core Components
-
Development of a common set of semantic building blocks that represent the
general types of business data in use today and provides for the creation of
new business vocabularies and restructuring of existing business vocabularies.
As well as business processes, ebXML relies on core components to provide
interoperability among industries and business functions, but core components
work at the individual data-element level. Core components identify the data
items that businesses use most often and across industries, assigning them
neutral names and unique identifiers.
-
Technical specifications: ebXML Core Components Technical Specification. This
specification presents a methodology for developing a common set of semantic
building blocks that represent the general types of business data in use today
and provides for the creation of new business vocabularies and restructuring
of existing business vocabularies.
-
Developed by UN/CEFACT Techniques and Methodologies Group, more details can be
found in
http://www.unece.org/cefact/index.htm.
Further
information could be found in the ebXML web site:
|
