Revision to Scenarios document

["Paul R. Levine" <plevine@telcordia.com>]

Business Process Team:

Please replace the earlier version of bpModelScenarios.doc with this later
version from Karsten Riemer.  My earlier attempt to transmit this update failed.
Hopefully this will work better.  Based on today's call the Scenarios document
will follow the Class Definitions section of the FYI document, shown as follows:

The ebXML Business Process Model Example
Four Model Sub-groupings
Descriptions of the Four Model Sub-groupings
Illustrations of the Four Model Sub-groupings
Class Definitions
Scenarios for the use of the ebXML Business Process Metamodel
Automobile Component Procurement Example
Issues

Paul Levine
---------------------- Forwarded by Paul R. Levine/Telcordia on 05/01/2000 01:06
PM ---------------------------


Karsten Riemer <Karsten.Riemer@East.Sun.COM> on 05/01/2000 08:23:43 AM

Please respond to Karsten Riemer <Karsten.Riemer@East.Sun.COM>

To:   ebXML-BP@lists.oasis-open.org
cc:    (bcc: Paul R. Levine/Telcordia)
Subject:  Revision to Scenarios document




Hi,

based on comments from Bob Haugen I have clarified the relationship between
the 'layers' in the scenarios, and the packages in the metamodel:



Note: There
is an alignment of these layers to the packages of the meta model.

(We should
work to make this alignment even clearer). The alignment for now

is:

·     The
market layer uses the 'Markets and Communities' package and the

resource part of
the 

ôResources and Contracts

ö package. ·      The Business Process

layer uses
the 

ôProcess and Rules

ö package and the contract part of the



ôResources and
Contracts

ö package. ·    The

ôInformation Exchange

ö layer uses the



ôInformation
Flow and Communication

ö package. · The

ôBusiness Document

ö layer

uses the
business document and information entity part of the 

ôInformation

Flow and
Communication

ö package.



Based on comments from Chris Ferris of the transport
group I made changes to

the discovery and adaptation section (see document) and
also to the conversion

section. Main point for conversion is that we do not
expect that all the

existing document definitions, as in RosettaNet, OAG,
EDIFACT, etc. must be

converted with respect to content or structure, just that
they have to fit

with the very flexible (and not yet final) business
document/information

entity part of the metamodel.



I received one more comment
which had to do with commodity codes. For now I

have not included anything on
this. I believe it would be a core components

type issue.



Paul/Marcia, this new
version of the scenarios document should be part of the

package that gets made
available today.



thanks,

-karsten

Mac Word 3.0

Business Process Team:

Attached is the draft of "Scenarios for the use of the ebXML Business Process
Metamodel" as provided last week by Karsten Riemer.  As we discussed on our
conference call last week, this document will be added to the "FYI" document to
be sent to the ebXML steering committee for distribution to the various ebXML
project teams prior to the Brussels meeting.  So the list of FYI sections
provided yesterday by Marcia McLure will now be:

The ebXML Business Process Model Example
Four Model Sub-groupings
Descriptions of the Four Model Sub-groupings
Illustrations of the Four Model Sub-groupings
Class Definitions
Automobile Component Procurement Example
Issues
Scenarios for the use of the ebXML Business Process Metamodel

Please review the Scenarios document along with the other sections and bring
your comments and recommendations to our scheduled
teleconference meeting on today at 12:00 p.m. EDT.  As soon as coments from the
call are incorporated I will send this FYI document to the ebXML steering
committee.

Best regards,

Paul Levine