[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [BP] specification relationship issues 2
Scott, Thanks for the close look. Please see in-line. > -----Original Message----- > From: Scott Hinkelman [SMTP:srh@us.ibm.com] > Sent: Thursday, January 04, 2001 12:47 PM > To: Cory Casanave; ebxml-bp@lists.ebxml.org; ebxml-core@lists.ebxml.org > Subject: RE: [BP] specification relationship issues 2 > > Cory, > I am copying this to the listers in spirit of open discussion. > > I see 'AuthorizingRole' in the UML but I can't find 'authorizingRole' in > the 91 dtd. [CBC] In the interests of syntactic minimalism these are part of the binary collaboration which has attributes for the requesting and responding names. So a binary-collaboration tag will create the BinaryCollaboration and two AuthorizingRoles. The same is done for business-transaction which will create the requesting and responding activities (since these are all 1-1 relations). > Firstly do you believe that a <binary-collaboration> should only exist > under a <package>? [CBC] Interesting you should bring this up. In the OMG-EDOC-CCA model things like collaborations, business transactions and muli-party-collaborations (by other names) are also namespaces and can include the definition of other elements inside them (like documents and sub collaborations), so they inherit from "package" . This came out of some discussion about model management. I think it would be a good idea for the EB model to do the same, but I didn't see it as sufficiently important to bring up now. > Seperate issue: > 091.xml: I assume both the <transistion>'s 'from' attribute and the > <start>'s 'to' attribute both refer to > a <business-transaction-activity>'s 'name' attribute within the same > <binary-collaboration>. [CBC] Yes > If so, > I suggest changing the slightly misleading dtd comment: > " <!-- the "OrderCollaboration" specifies that it will start with > an "OrderBT" > business transaction from the buy role. If the order is > confirmed it will... " > to: > " <!-- the "OrderCollaboration" specifies that it will start with > an "OrderBT" > business-transaction-activity which indicates from the buy > role. If the order is confirmed it will..." [CBC] Ok > This leads to a question, on: > If a <binary-collaboration> specifies an 'initiator' and 'responder' via > attributes, what exactly does this > mean if its contained <business-transaction-activity>s can define the > direction via 'from' and 'to'? [CBC] After the initial activity then either role may initiate an activity forming a 2-way conversation. > Is the intention that the first <business-transaction-activity> must have > the > initiator value specified within > it's from attribute? [CBC] Yes, this should be specified - I will put it in the DTD table. > Scott Hinkelman, Senior Software Engineer > XML Industry Enablement > IBM e-business Standards Strategy > 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) > srh@us.ibm.com, Fax: 512-838-1074 > > > > Cory Casanave <cory-c@dataaccess.com> on 01/04/2001 10:32:01 AM > > To: Scott Hinkelman/Austin/IBM@IBMUS > cc: > Subject: RE: [BP] specification relationship issues 2 > > > > Scott, > I don't know how to say this in DTD without imposing strict ordering > constraints on the model elements (which I don't think we want). We can > change the cardinality in the model (from authorizingRole to Requesting > Activity) to 1..n. The start state may have to be a documentation > constraint. > Cory > > > -----Original Message----- > > From: Scott Hinkelman [SMTP:srh@us.ibm.com] > > Sent: Wednesday, January 03, 2001 4:37 PM > > To: ebxml-bp@lists.ebxml.org; ebxml-core@lists.ebxml.org > > Subject: [BP] specification relationship issues 2 > > > > The following validates under 090 dtd. > > -> We should insist that a binary-collaboration contains at least 1 > > business-transaction-activity, > > and at least 1 start. > > > > <?xml version="1.0" encoding="UTF-8"?> > > <!DOCTYPE EbXmlProcessSpecification SYSTEM > > "file://localhost/C:/ebXML/BP/ebXmlSpecificationDTD090.dtd" > > > <EbXmlProcessSpecification> > > <package name="mypackage"/> > > <package name="mysecondpackage"/> > > <business-transaction name="mybusinesstransaction"> > > <request type="myrequesttype"/> > > </business-transaction> > > <binary-collaboration initiator="theinitiator" name="thename" > responder > > ="theresponder"/> > > </EbXmlProcessSpecification> > > > > Scott Hinkelman, Senior Software Engineer > > XML Industry Enablement > > IBM e-business Standards Strategy > > 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) > > srh@us.ibm.com, Fax: 512-838-1074 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC