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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: [T1M1 XML] RE: One potential XML mapping for ebXML Core Components

A project proposal has been submitted to the eBTWG to create a library of
Business Information Objects (attached).  One source of input to this
project will be UML models of information extracted from X12 and UN/EDIFACT
data dictionaries.  Other sources are indicated in the attached project


Paul Levine
(See attached file: BIO-Project Proposal.html)

                    sprint.com                    To:     bhandspicker@foliage.com,                       
                                                  ebtwg-ccs@lists.ebtwg.org, ebxml-dev@lists.ebxml.org    
                    09/14/01 10:29 AM             cc:     knaujok@home.com,                               
                                                  raymond.e.reeves@mail.sprint.com, t1m1dslsp@t1.org,     
                                                  t1m1xml@t1.org, umauom@lists.atis.org, (bcc: Paul R.    
                                                  Subject:     [T1M1 XML] RE: One potential XML mapping   
                                                  for ebXML Core Components                               

Hi all,

At the time, there is an effort within T1M1 to develop a
standard "Mapping of UML notation to XML Schemas (and vice versa)." This
is documented in T1M1/2001-100 and T1M1/2001-132R1.

These documents purport to define a mechanism for mapping UML model
management and static view to XML Schemas. In order to take advantage of
a critical set of features existing in XML Schemas (e.g. attributes,
elementGroup, etc.), these documents (implicitly) define a "UML profile
for XML Schemas".

These two documents are under review and may be merged together so that
there will be a section describing the UML profile for XML Schemas, a
set of mapping rules from UML notation to XML Schemas and an addendum
for describing additional extensions to support (initially) "Data
Dictionary" like capabilities (now rudimentary in 132) with profile
extensions to support the DD definition and mapping.

I believe the Core Components Data Dictionary could be modeled using UML
(and better yet, we could analyze the attributes used in it to make them
part of the DD profile properties -tagged values-) and use "UML profile
for Data Dictionary Definitions" stereotypes, properties (tag values),
etc. to model all what ebCC has defined. I believe we at T1M1 would
benefit from learning about ebXML's approach to define what a "Data
Dictionary" (or simply Data Dictionary Entry) looks like to them and
leverage on it.

It would be of great value to us all if a consistent "mapping mechanism"
is defined. As of now, there are several efforts within T1M1 (e.g., TA,
UOM, DSLsp, CLDR) where this mapping is crucial. Furthermore, ITU-T SG4
WP4 Question 9 has a work item for defining a "Mapping of UML to XML
Schemas" and T1M1/2001-100 (and its revisions) is the proposed standard
coming from T1M1.

Please consider these documents and provide comments, suggestions as
appropriate on style, approach, etc. It is important to us to have a
broad set of eyes to look into this effort on which many others are


Raymond Reeves
Member of T1M1 tML/DSLsp/UOM AHG/WGs

   -----Original Message-----
   From: bhandspicker [mailto:bhandspicker@foliage.com]
   Sent: Wednesday, September 12, 2001 4:14 PM
   To: ebtwg-ccs; ebxml-dev
   Cc: bhandspicker; knaujok
   Subject: One potential XML mapping for ebXML Core Components

   ebXML Community,

   For one of our clients we developed XML Schemas for business
   documents based on the ebXML Core Components.  Of course, this
   required us to create a mapping of the Core Components Data
   Dictionary into a Core Components XML Schema.  With the encouragement
   of our client (who enthusiastically supports public standards
   efforts), we are contributing both "attribute rich" and "attribute
   free" variants of these Core Components XML Schemas for consideration
   by the ebXML and ebTWG community.

   We are looking forward to suggestions for improvements, debate over
   style of mapping, comments on our embedded comments, etc.

   Brian Handspicker

   N.B.  To satisfy UN/CEFACT's goal of openness, Foliage agrees to
   remove any IPR
   constraints or restrictions associated with this contribution.
   Foliage offers this contribution for evaluation and standards
   development purposes only, with no implied or explicit warrantee.

   Brian D. Handspicker
   Engineering Director
   Foliage Software Systems, Inc.


Title: Project Proposal - e-Business Transition Ad-hoc Working Group (eBTWG)

eBTWG Project Proposal

Business Information Object Reference Library

1. Objectives

1.1 Purpose

The purpose of the project is to to create and populate the eBTWG reference library with an initial set of Business Information Objects (BIO)  that were created from various business process modeling efforts. The project will help identify BIOs during Business Process and Information Modeling efforts. The project will define the process and provide guidance in the selection and normalization of base elements that would be suitable for the population of a lexicon. As BIO's are produced any linkage between UN/EDIFACT business concepts will be identified and maintained through the modeling process.

This project proposes to bring together several key artifacts of work from the ebXML project, and jointly continue their development work. Building on current ebXML work, three (3) essential themes will come together in this proposed project:

  • Developing Business Information Objects and models according to the UN/CEFACT UMM N090R10.
  • Normalized business concepts .
  • Lexicon and Business Reference Library. 

1.2 Scope

The project relates to the eBTWG key deliverable Business Process and Information Models and Lexicon of Core Components as identified in its mandate. 

2. Deliverables

The deliverables by the project are:

  • Business Information Objects Reference Library
  • New base elements as discovered in the analysis modeling phase.
  • Procedures for the submission and maintenance of Business Information Objects.
  • Documented revisions to the UMM (CEFACT/TMWG/N090) Information Modeling Patterns. 

3. Functional Expertise of Membership

The project team is a group of experts with broad knowledge in the area of Business Process and Information Modeling as outlined in the UMM (CEFACT/TMWG/N090). Each UN/CEFACT head of delegation may designate one or more experts to the project team. In doing so, they may delegate this task to one or more organizations, which may be national, regional or international. Experts are expected to contribute to the work based solely on their expertise.

4. Geographical Focus

The focus is global.

5. Initial Contributions

The following contributions are submitted as part of this proposal. It is understood that these are only for consideration by the project team and that other participants may submit their own contributions in order to ensure the gathering of as much information as possible from those with expertise and a material interest in the project but at the same time allow diverse voices to comment on the details of the projects and ensures that no single organization can dominate the process.:

  • TMWG UN Modeling Methodology (CEFACT/TMWG/N090)
  • ISO Open-edi (ISO/IEC JTC 1/SC 32/WG1 N181 - FDIS 15944-1)
  • ebXML Technical Report - Business Process Analysis Worksheets & Guidelines v1.0
  • ebXML Technical Report - Catalog of Common Business Processes v1.0
  • ebXML Technical Report - Core Component Overview v1.05
  • ebXML Technical Report - Business Process and Business Information Analysis Overview v1.0
  • ebXML Technical Report - Context and Re-Usability of Core Components v1.04 

Statement of resource requirements

Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UN/ECE secretariat.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC