[bpel4people] F2F Raw notes from chat Thu 22 Jan

[Ralf Mueller <ralf.mueller@oracle.com>]

Not sure someone saved the scribe, maybe the last two minutes from  
todays meeting are missing.

Regards,
   Ralf



[9:08] Dave Ings: Thursday 1/22 - 9 AM - 12:30 PM

Meeting will adjourn at 12:30, lunch will be served for those still  
present.

1. Final issue proposal discussions - up to 30 minutes

Dieter - http://www.osoa.org/jira/browse/BP-63
Michael - http://www.osoa.org/jira/browse/BP-44

2. Constellation 4 Interoperability - Further Discussion - Alex & Phil  
- up to 30 minutes

3. Working session on task routing proposal(s) - up to 3 hours

4. Final remarks / discussion of place and timing of next F2F - Chair


[9:38] Gerhard Pfau: Scribe: Gerhard

9:40] Gerhard Pfau: Dieter presents proposed resolution of BP-63


[9:47] anonymous morphed into Hannah Petereit


[9:51] Gerhard Pfau: Dave assigns BP-63 (previously unassigned) to  
Dieter

[9:59] Gerhard Pfau: Michael presents proposed resolution for BP-44

[10:00] Dave Ings: Revised proposal email link: http://www.oasis-open.org/apps/org/workgroup/bpel4people/email/archives/200901/msg00041.html


[10:02] Gerhard Pfau: Michael moves o resolve BP-44, Dieter seconds

[10:03] Gerhard Pfau: Motion unanimously carried

[10:05] Gerhard Pfau: Alex presents thoughts on lean tasks,  
deployment, etc.

[10:35] Gerhard Pfau: Group discussion around how to create / start /  
delete lean task

[10:38] Gerhard Pfau: Discussion about extending people activity to  
invoke lean task in a new way (not via remote task)

[10:42] Gerhard Pfau: Discussion if lean tasks should have a rendering

[10:45] Gerhard Pfau: There is consensus in the room that lean tasks  
optionally can define a rendering

[10:47] Gerhard Pfau: Next steps: Alex and Phil to work with SAP to  
iterate the BP-44 proposal

[10:48] Gerhard Pfau: Goal is to present another iteration at the next  
TC meeting

[10:49] Gerhard Pfau: Coffee break until 10:55

[11:01] Gerhard Pfau: Meeting continues

[11:01] Gerhard Pfau: Alex is presenting motivational scenario for  
routing patterns

[11:02] Gerhard Pfau: .. using Sharepoint as an example

[11:03] Gerhard Pfau: Example scenario: Purchase Order Approval

[11:04] Gerhard Pfau: Supports adding tasks to a chain of tasks

[11:11] Gerhard Pfau: Currently don't use output. Instead uses  
comments and (the aggregate of) "approve" / "disapprove"

[11:13] Gerhard Pfau: Ralf presenting the Oracle routing pattern  
scenarios

[11:15] Gerhard Pfau: Oeacle uses task payload, not input / output  
when modeling a human task

[11:15] Gerhard Pfau: Task have a predefined (extensible) set of task  
outcomes

[11:16] Gerhard Pfau: Assignment and routing policies are assigned to  
a task: Single, Sequential, Parallel

[11:18] Gerhard Pfau: "Application roles" are used similar to LPGs.  
Alternatively people / groups / roles are used when defining the  
single / sequential / parallel

[11:19] Gerhard Pfau: Routing patterns can be nested

[11:21] Gerhard Pfau: Default outcome used when people do not respond  
in the expected amount of time

[11:24] Gerhard Pfau: Observation: HR people have the most complex  
routing requirements

[11:26] Gerhard Pfau: In collaboration mode in parallel the data is  
copied

[11:26] Gerhard Pfau: result aggregation: pick one

[11:28] Gerhard Pfau: From the process perspective a human task  
(routing task) is considered a black box

[11:43] Gerhard Pfau: Discussion about Oracle requiring ad-hoc  
subtasks in their scenario

[11:44] Gerhard Pfau: According to Ralf currently not required. The  
original task is temporarily transferred / shared.

[11:52] Gerhard Pfau: Oliver: HR scenario similar to BPMN subflow

[12:00] Gerhard Pfau: Alireza: Seems that the scenarios presented by  
both Oracle and Microsoft seem to be similar.

[12:12] Gerhard Pfau: Discussion: How to structure work on routing  
patterns / subtasks

[12:14] Gerhard Pfau: Proposal: Every 2nd week during the usual TC
meeting have a meeting that brings people together working on routing
patterns / subtasks

[12:16] Gerhard Pfau: Correction: Proposal: Every 2nd week during the  
usual TC meeting time slot have a meeting that brings people together  
working on routing patterns / subtasks.

[12:17] Gerhard Pfau: These meetings are informal.

[12:18] Gerhard Pfau: IBM is going to set up the first meeting  
(January 2.

[12:19] Gerhard Pfau: ... January 2

[12:19] Gerhard Pfau: January 28 )

[12:20] Gerhard Pfau: Dave discusses next steps

[12:21] Gerhard Pfau: Agreement that at least one more technical f2f  
is required

[12:22] Gerhard Pfau: Proposal to have next f2f sometime in May

[12:25] Gerhard Pfau: Proposal: Week of May 11: Start Tuesday 9am,  
end: Thursday noon

[12:26] Gerhard Pfau: Tentative location: US east coast