RE: [ebxml-bp] Transaction Option

[<martin.me.roberts@bt.com>]

Dear all,
	Here is my view of a CommercialTransaction class

Martin Roberts 
xml designer, 
BT Exact
e-mail: martin.me.roberts@bt.com 
tel: +44(0) 1473 609785  clickdial
fax: +44(0) 1473 609834
Intranet Site :http://twiki.btlabs.bt.co.uk/twiki



-----Original Message-----
From: martin.me.roberts@bt.com [mailto:martin.me.roberts@bt.com] 
Sent: 13 February 2004 13:55
To: Monica.Martin@Sun.COM; ebxml-bp@lists.oasis-open.org
Subject: [ebxml-bp] Transaction Option


Dear all, 
	attached is a diagram showing how I propose to us ethe Patterns
within the new Schema.

	The key here is the attribute settings of the
RequestingBusinessActivity.  These are shown.

	The RequestingBusinessActivity shown is derived by restriction
which means that no new attributes would be allowed.

	We have two options.  

	1) set them to values as described by the document that
explained the patterns (as shown) Note: use of prohibit for attributes
that do not apply to the pattern - no overide possible.

	2) do a similar defintion as shown except use default values to
show what should be used but allow for overiding.  This would mean that
it would be possible to insist on Non-Repudiation with an
InformationDistribution.


	As the link between the BusinessTransactionAcitivity and the
BusinessTransaction is a IDREF (GUIDREF) there is no change to the
BusinessTransactionActivity for this change.

Martin Roberts 
xml designer, 
BT Exact
e-mail: martin.me.roberts@bt.com 
tel: +44(0) 1473 609785  clickdial
fax: +44(0) 1473 609834
Intranet Site :http://twiki.btlabs.bt.co.uk/twiki

CommercialTransaction.png