ebxml-coord message

OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: Re: Core Comp. one pager

        ebXML Core Components

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

Scope/Key Issues

Whereas the Business Process Model defines processes down to the message level,
Core Components work within the message content.  As such Core Components
definitions are required for ebXML Messages (Transport, Packaging and Routing),
Registries, Repositories and Business Process Models.

The scope of the ebXML Core Components Project Team is to:

a. Define a library of “Smart” Core Components
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.


The world does not need another P.O.!
- Industry Specific approach did not work
- Leads to proliferation of single use messages
- Restricts interoperability
Tried “Generic” all encompassing approach
- Resulted in proliferation of Implementations
- Restricts interoperability

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:
. be syntactically neutral,
. aonform to ISO11179,
. align with the Unified Modeling Methodology and
. provide a mechanization for developing Core Components

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 describe 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.
. Business sub-process
. Industry
. Region/Geography
. Product
. Legislative

The above classifications are referred to as the 'core' contexts.

Work Plan

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


+ Syntax-neutral content descriptions (draft)
+ Sample XML instantiation of content sets
+ Methodology for reusing components & modifying/extending business documents
    - "Methodology for describing Core Components - Analysis and Proposal
(currently at Draft-Rev.04)"
+ Statement to EDI community regarding utilization of ebXML results
+ Mechanism/categorization of "methods" (sub-processes) and "context"/"state" as it
affects component use

tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142

tel;pager:australia 016 631 632
tel;cell:041 381 6846
fn:tim mcgrath

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC