| From | Sent On | Attachments |
|---|---|---|
| Monica J. Martin | Jun 14, 2004 10:50 pm | |
| David RR Webber | Jun 15, 2004 7:26 am | |
| Monica J. Martin | Jun 15, 2004 8:05 am | |
| mart...@bt.com | Jun 15, 2004 8:31 am | |
| Jean-Jacques Dubray | Jun 15, 2004 8:38 am | |
| Yunker, John | Jun 15, 2004 9:06 am | |
| Jean-Jacques Dubray | Jun 15, 2004 10:00 am | |
| David RR Webber | Jun 15, 2004 10:07 am | |
| David RR Webber | Jun 15, 2004 10:10 am | |
| Yunker, John | Jun 15, 2004 10:11 am | |
| Yunker, John | Jun 15, 2004 10:18 am | |
| David RR Webber | Jun 15, 2004 10:19 am | |
| David RR Webber | Jun 15, 2004 10:24 am | |
| Monica J. Martin | Jun 15, 2004 10:30 am | |
| Monica J. Martin | Jun 15, 2004 10:33 am | |
| David RR Webber | Jun 15, 2004 10:55 am | |
| Jean-Jacques Dubray | Jun 15, 2004 11:16 am | |
| Hima...@sybase.com | Jun 15, 2004 11:20 am | |
| Jean-Jacques Dubray | Jun 15, 2004 11:38 am | |
| Jean-Jacques Dubray | Jun 15, 2004 11:51 am | |
| Yunker, John | Jun 15, 2004 11:51 am | |
| Yunker, John | Jun 15, 2004 11:54 am | |
| Yunker, John | Jun 15, 2004 11:59 am | |
| David RR Webber | Jun 15, 2004 12:34 pm | |
| David RR Webber | Jun 15, 2004 12:43 pm | |
| David RR Webber | Jun 15, 2004 12:43 pm | |
| David RR Webber | Jun 15, 2004 1:01 pm | |
| Hima...@sybase.com | Jun 15, 2004 1:50 pm | |
| David RR Webber | Jun 15, 2004 6:17 pm | |
| Monica J. Martin | Jun 16, 2004 7:51 am |
| Subject: | Re: [ebxml-bp] [ebBP] Tell 6/14/2004: Business Contract Requirements for State Alignment | |
|---|---|---|
| From: | David RR Webber (dav...@drrw.info) | |
| Date: | Jun 15, 2004 7:26:31 am | |
| List: | org.oasis-open.lists.ebxml-bp | |
Monica,
Not wanting to preempt discussion on Friday - but just wanting to throw out some technical ideas.
What if we linked the signals to the begins/endsWhen conditionals on a BT?
Just like with my proposal around linkage to context statements using a nameRefID - we could easily point to a named signal (it has that attribute already) and it would be either then boolean true or false. eg: beginsWhen="#mysignal-Is-On"
This still leaves how the signal itself gets set of course! Seems like Dales post earlier may fit / hint into that category...since the only attribute in the signal right now is the URI - how does one actually turn a signal on?!
If we can crack that "glue" then I believe we can provide what we need here.
Am I also right in thinking that essentially used in this way the signals actually constitute the equivalent of an immediate "break" command so familiar in procedural languages to escape into/out of the current logical block. In our case that is of course a BT.
DW
----- Original Message ----- From: "Monica J. Martin" <Moni...@Sun.COM> To: "Anders W. Tell" <ande...@toolsmiths.se>; "Yunker, John" <yun...@amazon.com>; "Kenji Nagahashi" <naga...@fla.fujitsu.com>; "Jean-Jacques Dubray" <jean...@Attachmate.com> Cc: "ebXML BP" <ebxm...@lists.oasis-open.org> Sent: Tuesday, June 15, 2004 1:53 AM Subject: [ebxml-bp] [ebBP] Tell 6/14/2004: Business Contract Requirements for State Alignment
Today's ebBP call surrounded how we ensure (as much as practical) state alignment. Kenji Nagahashi proposed we provide additional constraints on web services (top-down approach - business process to web services). We would like to more fully discuss the business contract requirements related to: State alignment and business signals. Here are some of the questions that arose (from John Yunker particularly):
* How do signals give you state alignment? How do we get certainty from a business perspective? * How does the contract layer use the state alignment will help us relate the special business timeouts to the technical signal receipt.BPSS provides a semantic to the contract layer. The business level timeouts in addition to the protocol level have to be recognized. * How does the contract layer use the state alignment. This will help us relate the special business timeouts to the technical signal receipt. [1]
The bullets above can form the agenda (subject to team input). Any member is welcomed to attend. Those expressing an interest today were: Yunker, Dubray, Nagahashi and Moberg (and myself).
You have indicated you would be available Friday and Monday (6/21). Let's try, as discussed:
* 877 330 9868, international 909 472 3386, when prompted hit **, then passcode 09868. * Time: 9 a.m. PDT, 6 p.m. CET, 18 June 2004. * Agenda above.
Thanks. [1] Steve Capell, RedWahoo question.





