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: E: One potential XML mapping for ebXML Core Components


There is another eBTWG project proposal: Business Process Information Model
Exchange Schema (attached) that addresses "XML-ization of the UML
information model."  I have forwarded T1M1/2001-100R4 and 132R1 to Jim
Clark, the initiator of this project proposal.

(See attached file: RDF-Project Proposal.html)

                    sprint.com                    To:     plevine@telcordia.com                           
                                                  cc:     bhandspicker@foliage.com,                       
                    09/14/01 12:21 PM             ebtwg-ccs@lists.ebtwg.org, ebxml-dev@lists.ebxml.org,   
                                                  ed.white@wcom.com, jdc-icot@lcc.net, knaujok@home.com,  
                                                  lraman@teraburst.com, mfargan@qwest.com,                
                                                  t1m1dslsp@t1.org, t1m1xml@t1.org,                       
                                                  umauom@lists.atis.org, (bcc: Paul R. Levine/Telcordia)  
                                                  Subject:     RE: E: One potential XML mapping for ebXML 
                                                  Core Components                                         


Is there anything in the deliverables for the BIO project that includes
(XML-based) IT-enablement of the BIO library (which is to be modeled
using UML -UMM-)?

Shouldn't we address the XML-ization of the UML information model?
(After all, what are the last three letter in ebXML for?) In that case
we might need a consistent mechanism for doing the "Mappings from UML
(model management and static view) to XML Schemas." We should choose to
have such a consistent mapping mechanism across
standard-making-organizations and forums. I believe a great level of
synergies could be leveraged by having ebXML folks look into the
T1M1/ITU-T proposed "mappings"... We would not want this to be a one man
(organization) show. I know many folks in the ebXML community can very
well help us with inputs to optimize and refine our (T1M1/2001-100R4 &
132R1) proposed draft standards.



-----Original Message-----
From: plevine [mailto:plevine@telcordia.com]
Sent: Friday, September 14, 2001 10:42 AM
To: raymond.e.reeves
Cc: bhandspicker; ebtwg-ccs; ebxml-dev; knaujok; raymond.e.reeves;
t1m1dslsp; t1m1xml; umauom; jdc-icot; plevine
Subject: Re: [T1M1 XML] RE: One potential XML mapping for ebXML Core

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


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


                    sprint.com                    To:

ebtwg-ccs@lists.ebtwg.org, ebxml-dev@lists.ebxml.org
                    09/14/01 10:29 AM             cc:

raymond.e.reeves@mail.sprint.com, t1m1dslsp@t1.org,
umauom@lists.atis.org, (bcc: Paul R.

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

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 Process Information Model Exchange Schema

1. Objectives

1.1 Purpose

The purpose of the project is to define a Business Process Information Model Exchange Schema. This schema will define the storage and exchange format for ebXML Business Process and Information Models developed in compliance to UN/CEFACT UMM N090R10.

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:

  • Provide for a common exchange format for ebXML Business Process Models.
  • Provide for a common exchange format for ebXML Business Information Models.
  • Provide for production rules that map the models into Business Process Specification Schema.
  • Provide for production rules that map the Business Process Work Sheets  into ebXML Business Process Information Models.

1.2 Scope

The project relates to the eBTWG key deliverable Business Process and Information Models storage and exchange format as identified in its mandate.

2. Deliverables

The deliverables by the project are:

  • UMM (CEFACT/TMWG/N090) Resource Definition Framework (RDF) Schema Specification
  • ebXML Business Process Worksheets to UMM (CEFACT/TMWG/N090) RDF
  • UMM (CEFACT/TMWG/N090) RDF to BPSS productions Rules

3. Functional Expertise of Membership

The project team is a group of experts with broad knowledge in the area of  the UMM(CEFACT/TMWG/N090) and Resource Definition Framework (RDF). 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/CEFACT Modeling Methodology (CEFACT/TMWG/N090)
  • Resource Description Framework (RDF) Model and Syntax Specification (REC-rdf-syntax-19990222)
  • ISO Open-edi (ISO/IEC JTC 1/SC 32/WG1 N181 - FDIS 15944-1)
  • TMWG-UMM RDF Profile v0.8
  • 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