|
| This group is
involved in defining a set of re-usable ebXML components which can
be applied in a standard way irrespective of the constraints imposed upon business
data. These constraints may occur due to business sector, business processes and
other contextual influences. These core components will not constrain functionality but be accompanied by a methodology for extensibility. This will enable users to define the data that is meaningful to their business and process whilst still ensuring maximum interoperability. |
| a. Define a library of The ebXML Core Components project team will identify and define those items considered common across business data exchanges. Common items are semantic units at any level that stay consistent across contexts, and therefore are reusable both within and between business exchange messages. |
|
| b. Establish Classifications of Context Business process models will help define common items and provide their context.This context will in turn define the precise use of common items in messages exchanged among parties. The team will describe these items in terms independent of implementation syntax, and thus should apply equally to XML (or SGML) documents, as well as EDI transactions. |
|
| c. Define and document an Extension Methodology
The team will adopt -- or if needed, develop -- a methodology to consistently
build or derive core components, including methods to encourage reuse and provide for extensions.
In concert with the Business Process Project Team, this group will identify element names that can apply across business processes and contexts,
yet still allow for translation into leading spoken languages.
The work will generate the content of core components independent of
implementation syntax, but with references to data structures in XML messages and EDI
transactions. The team will identify attributes that describe the context of the
components also in terms independent of syntax. Team participants will produce
samples of core components and describe their representation in XML messages and
EDI transactions. |
Requirement
|
The world does not need another P.O.!
|
|
|
A new approach is to develop a methodology for analysis of the existing data models currently used in e-business. The methodology is intended to:
|
|
|
The proposed methodology proposed separates 'components' (objects) from their 'context' (how it is used). Context is defined as factors (or attributes that influences rules and escribe variation in the data structures providing semantic refinement of a core component. Contexts are to be expressed as hierarchical classifications drawn from various standards, e.g.
|
| The above classifications are referred to as the 'core' contexts. |
| May 26 - Submit first draft of Methodology for Describing Core Components to full ebXML for review and comment | |
| June 30 - distribute draft version 2 to full ebXML for review. | |
| July 14 - Close of second comment period of Methodology for describing core components |
|
Deliverables
|
Please address questions or comments regarding this site to webmaster@ebxml.org
