david, thanks for that, i can do with all the help i can get. incidently, i solved the question later on in the day, but still, thanks, i hope your goodies provide further insight into the topic. i am sure they will. dean hemopo auckland, new zealand -----Original Message----- From: David RR Webber [mailto:david@drrw.info] Sent: Friday, 18 June 2004 2:49 p.m. To: Monica J. Martin; ebXML BP; jdeanh@ihug.co.nz Subject: Re: [ebxml-bp] [Fwd: On Page 18 of the ebXML Business Process Specification Schema it gives an example of a notification transaction] Dean, Go to http://drrw.net/visualscripts/#ebxml and look at the JPG of the interaction and activity diagram - and then check the link to the resulting XML - and see how each piece gets output from the model into the BPSS instance. I think this will help you. Also there is the tutorial PPT there. If you also download the model and install the editor - you will be able to pick the various transaction models and see how the <DocumentEnvelope> options are configured from the Exchange Profile settings and selections - depending on the transaction type you pick from the BT drop-down list.. I believe this all makes sense - I did not find any conflicts as I was building this out. Thanks, DW ----- Original Message ----- From: "Monica J. Martin" <Monica.Martin@Sun.COM> To: "ebXML BP" <ebxml-bp@lists.oasis-open.org>; <jdeanh@ihug.co.nz> Sent: Thursday, June 17, 2004 7:00 PM Subject: [ebxml-bp] [Fwd: On Page 18 of the ebXML Business Process Specification Schema it gives an example of a notification transaction] > Unfortunately, I failed to send this to the list to get Dean's question > answered. The notification pattern does have a receipt acknowledgement, > as this a formal information exchange business transaction with > non-repudiation requirements (see UMM, R10, Chapter 9 on patterns). If > others would like to add comments to ansewr Dean's questions, please > speak up. > > Thanks. > > J. Dean E. P. Hemopo wrote: > > > On Page 18 of the ebXML Business Process Specification Schema it gives > > an example of a notification transaction. I notice that in this > > depiction with one document flow, lines numbered 699 to 700 that there > > is Responding business element named RespondingBusinessActivity with > > attribute “name”= to “”. Prior to this there was a > > RequestingBusinessActivity element mentioned. I understand this, what > > escapes me is the fact that both exist within the BusinessTransaction > > element declaration as child elements (see line 694 paired with 701). > > A further example of this, on page 22 of the same specification > > document there is an example that shows a business transaction with > > one request and two possible responses, a success and failure. Now > > once again, there is the RequestingBusinessActivity and > > RespondingBusinessActivity elements declared as children of > > BusinessTransaction (line 819 and line 844). > > > > Now I assume that there is some time saving going on by depicting both > > sides of the BusinessTransaction, requesting and responding roles. So, > > in effect, I could (from the RequestingBusinessActivity side) have as > > my notification transaction as thus: > > > > <BusinessTransaction name="Notify of advanceshipment"> > > > > <RequestingBusinessActivity name=""> > > > > <DocumentEnvelope > > > > BusinessDocument name="ASN"/> > > > > </RequestingBusinessActivity> > > > > < /BusinessTransaction> > > > > example taken from page 18. > > > > Or, is the RespondingBusinessActivity component a “mapping” of the > > Responding business activity’s response format, as required AND > > specified by the Requesting side of the transaction. In this example, > > no response is required. > > > > I ask the same of the subsequent example on page 22, lines numbered > > 819 through to and including 844. I thought the BusinessTransaction > > Element would finish its declaration after line 834, from the > > RequestingBusiness perspective, or, as I summise, and as is > > illustrated on page 18, another specification of the *format for > > responding* to this BusinessTransaction declared from line 835 to 843 > > inclusive. > > > > Or is it simply a way of saving time, by OASIS, to chuck both the > > Request and Response in the same declaration. > > > > Thank you for your help. > > > > Dean Hemopo. > > > > > > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/>
<<attachment: winmail.dat>>