Comments on BP Tech Spec Draft V1.0

[Bob Haugen <linkage@interaccess.com>]

Line 93: (the overview diagram): Should the Business Entity 
class be the superclass of several additional classes in the metamodel, 
e.g. Party and Economic Resource (and maybe more)?  (This would
be in addition to its current subclasses.)  In other words, why should
EconomicResourceType be a Business Entity but not Party or
Economic Resource or maybe some other classes?

Line 204:  there is no definition of Business Entity.  (More precise
definition of its purpose might help to clarify the preceding issue.)

Lines 710-740: the collaboration diagrams were mapped to the metamodel
classes as of the end of Brussels.  The metamodel classes changed
in V1.0 and so the collaboration diagram mappings need to be updated
correspondingly.  

Lines 765-785: Some of the Metamodel Design Issues no longer apply
due to metamodel class changes; some need to be applied to document
line numbers.

Line 772: Issue 1.1 Recursive relationship from [Business Process Definition] to nested [Business Process Definition] no longer applies and can be deleted.

Lines 775-777: The Auto Procurement Example requires two different 
recursive relationships between [Economic Resource Types] 
* higher and lower levels of abstraction (e.g. Component Family and Component Master);
* subcomponents (e.g. bills of materials and tools).
This issue applies to the diagram on line 138.

Lines 778-785:  These issues can be generalized to two, both of which apply
to the diagram on Line 93:

* The metamodel does not specify relationships between Information Entities 
and Fundamental Information Entities and any of the other classes
in the metamodel.   Information about metamodel classes will be
sent in Business Documents, but the metamodel does not specify
how this will happen.

* Several of the metamodel classes will have complex implementations,
that is, be composite objects with many parts.  Should this decomposition
happen in Core Components, or should at least part be done in the
metamodel?

Respectfully,
Bob Haugen

=======================================================================
= This is ebxml-bp, the general mailing list for the ebXML            =
= Business Process project team. The owner of this list is            =
= owner-ebxml-bp@oasis-open.org                                       =
=                                                                     =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org 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 myname@company.com                        =
=======================================================================