I'm in favor of Bob's suggest approach in addition to having diagrams by
package.
Brian
> -----Original Message-----
> From: Bob Haugen [mailto:[email protected]]
> Sent: Wednesday, June 28, 2000 9:34 AM
> To: 'William J. Kammerer'; '[email protected]'
> Subject: RE: Suggestion for ebXML Knowledge Dissemination
>
>...
> Here is a suggestion:
> Break the diagram up into sections, not according to the
> current packages, but according to a narrative flow.
>
> For example, maybe:
> * A Party plays PartnerRoles in BusinessTransactions.
> BusinessTransactions consist of InformationExchanges which
> exchange BusinessMessages.
> * BusinessTransactions may be grouped as StepDefinitions
> in BusinessProcessDefinitions.
> * BusinessTransactions may result in BusinessEvents which
> affect BusinessEntitys.
> * SomeBusinessEvents are EconomicEvents which transfer
> ownership of EconomicResources.
> * BusinessEntities may be Agreements, EconomicResources,
> or EconomicResourceTypes.
> * Some Agreements are Contracts. Contracts make Commitments
> about future EconomicEvents.
>
=======================================================================
= This is ebxml-bp, the general mailing list for the ebXML =
= Business Process project team. The owner of this list is =
= [email protected] =
= =
= To unsubscribe, send mail to [email protected] with =
= the following in the body of the message: =
= unsubscribe ebxml-bp =
= If you are subscribed using a different email address, put the =
= address you subscribed with at the end of the line; e.g. =
= unsubscribe ebxml-bp [email protected] =
=======================================================================
