ebBP 5/30/2005: Manual Requests (wd-2-0-1-01)

[Monica J Martin <Monica.Martin@Sun.COM>]

Also in Tuesday's call, we discussed Novelli scenario for manual 
requests.  We had already done one change to make this more explicit in 
the specification.
I've made an additional change given the team resolution to put an 
example in an appendix.

This is an update to technical specification change to Section 3.4.9.1 
sent 23 May 2005: 
http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200505/msg00020.html):

1. Take additional descriptive text shown in changes for Section 3.4.9.1 
(above) and put in a technical specification appendix, Appendix F.
2. Make the following change specified below. 

Change from:
    * If the Request is implicit (i.e. the Response is based on previous 
Commercial Transaction), the Notification pattern could be used.
      The Request may be implicit and the Response indicative of the 
intent of the parties.

Change to:
    * If the Request is implicit (i.e. the Response is based on previous
      Commercial Transaction), the Notification pattern could be used.
      In this case, the Requesting Business Activity is a Response,
      i.e. the result of an action within the notifying entity.
      The actual Request may be implicit and the Response indicative of the
      intent of the parties. The visible state transitions available
      are modeled, in order to manage the transactions that occur.
      For example, a fork may be used between the two types of transactions
      (manual and automated), in order to make the visible state
      available for monitoring. 

3. At end of Section 3.4.9.1:
Change from:
Additional operational semantics may exist in the patterns matrices 
rather than being held in the ebBP schema. In future versions, more 
semantics may be defined and included in the ebBP technical 
specification and/or schema as business requirements are identified or 
user community feedback received.

Change to:
Additional operational semantics may exist in the patterns matrices 
rather than being held in the ebBP schema.
For example, manual or implicit actions by an involved party may be 
relevant in the ebBP process definition,
particularly to provide state transition information in the 
collaboration for monitoring. In Appendix F,
a brief description is provided about how the patterns may be used when 
manual or implicit actions exist. 
In future versions, more semantics may be defined and included in the 
ebBP technical specification and/or schema
as business requirements are identified or user community feedback received.