BP DTD first draft and comments

[LONJON Antoine <ALonjon@MEGA.com>]

Dear team members,

This is only a preliminary draft of the BP DTD. It only covers the BOV as it
contains the main data we want to store in an ebXML repository.
More can come if necessary. Especially, we are waiting the definition
of BusinessDocument from the CC/BP team.

Several comments on the current model:
1. The XML definition must be as simple as possible: corresponding documents
will be interpreted by software.
2. Inheritance of association is a difficult to interpret and should be
avoided as far as possible.
3. I have an issue with BusinessPartner and Functional role:
If we want to define CommercialTransactions as independant elements,
roles are then composite of CommercialTransactions.
So, in the version, I did not take the Party element into account.
4. When you read the DTD, it apperas that the OjectflowState step to get to
the document
is unnecessary. It is only the consequence of using the ActivityDiagram
metamodel.

An example of overusing inheritance:
CommercialTransactionActivity is a subtype of ActionState and
BusinessCollaborationProtol is a subtype of ActivityGraph.
What should we be using from the ActivityGraph to choreograph the
CommercialTransactions in a BusinessCollaborationProtocol:
SimpleTransition/Condition/fork/Branch, .....
The inheritance relationship does not state anything about this. We do not
want the DTD to cover all the ActivityGraph.

I've made two proposals, one for the CommercialTransaction
(CommercialTran.png) and the other one for BusinessCollaborationProtocol
(BusinessCollProt.png) that express the BOV mapping into XML.
The UML model shall be readden as follow:
Each composition association leads to an ELEMENT in XML
The other associations lead to ID/IDREF pairs.

I will provide shortly an XSD version of the DTD.

Antoine LONJON
Chief Architect
33 1 42 75 40 30
alonjon@mega.com

BusinessCollProt.PNG

CommercialTran.PNG

BPDtd_Draft2.dtd