[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-dev] ebXML vocabulary
As Martin Sachs articulated earlier in the week, ebXML does not
have a standard set of documents similar to xCBL. The ebXML suite of
technical specifications can be broken down into two separate areas -
architecture and content. Most of the ebXML architecture specs
(Messaging, CPP, Registry) are under the purview of OASIS. The ebXML
content specifications (Business Process and Core Components) are under the
purview of UN/CEFACT. However, these UN/CEFACT content
pieces are syntax neutral solutions that are devoid of XML.
The leading activity in developing XML within the ebXML framework
is the OASIS Universal Business Language Technical Committee headed by Jon
Bosak. UBL is decomposing the xCBL 3.0 suite of transactions
to identify ebXML Core Component and Business Information Entities.
Those BIE's are then being constructed into standard XML schema's using a
set of carefully crafted XML design rules. The design rule work, under the
leadership of Eve Mailer, is focused on XSD as the UBL canonical form, and
is determining the best fit features and uses of XSD in
promoting UN/CEFACT Core Components into full fledged international
business standards that supports both the ebXML concept of context and extension
methodology.
You can read more about UBL at http://www.oasis-open.org/committees/ubl/. A white
paper, UBL: The Next Step for Global E-Commerce, is available at:
http://oasis-open.org/committees/ubl/msc/200204/ubl.pdf. A position paper setting forth the UBL value
proposition for industry XML initiatives is available at http://oasis-open.org/committees/ubl/lsc/200204/industry.pdf
Mark
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC