BPEL4People - 1/28 Task Routing Working Session - Minutes

[Dave Ings <ings@ca.ibm.com>]

Here are the minutes for the 1/28 task routing working session. As these are informal working sessions, neither "issues" nor action items will be entered in Kavi, but only noted below.

Present:

Alireza, Dieter, Frank, Hannah, Phil, Ralf, Gerhrard, Dave, Matthias, Oliver

The next working session is Wed 2/11 11 AM ET.

Summary of action items:

1. Oliver will prepare use cases for composite routing patterns for the next meeting.
2. Oracle/Ralf to develop proposal to address the previous (see transcript) issue.
3. Phil will prepare his lean task proposal for the next meeting

Chatroom Transcript:

anonymous morphed into Dave Ings
Dave Ings: The emeeting URL is https://apps.lotuslive.com/meetings/join?id=241-366
Dave Ings: AI: Oliver will prepare use cases for composite routing patterns for the next meeting (in two weeks time).
Dave Ings: Agreement: The order of from clauses in the HT spec determines the order of the subtasks instances when executing the routing pattern.
Dave Ings: Agreement: The order of users in a literal assignment determines the order in subtask execution.
anonymous1 morphed into Alireza
Dave Ings: Issue: What's the instantiation model for a routing pattern and what's the observable behavior.
Dave Ings: AI: Oracle/Ralf to develop proposal to address the previous issue.
Dave Ings: Attendance: Alireza, Dieter, Frank, Hannah, Phil, Ralf, Gerhrard, Dave, Matthias, Oliver
Dave Ings: Matthias notes we have general agreement on proposal except for the open issue of the instantiation model
Dave Ings: (general agreemnt applies to the non-composite patterns)
Dave Ings: Oliver begins to review composite patterns slides
Dieter Koenig: Issue (page 29 - input mapping): need to discuss "custom properties" (not defined so far) - does this map to attachments/comments?
Phil Allen: localSubTask element has a multiinstance property with values of parallel|sequential.  Perhaps we should remove this attribute and instead rely on peopleAssignments descendant of the localSubTask to contain a routing pattern (if necessary) to handle those subTasks that are operated on by multi-users.  It also gains the benefit of single-all distinguishment.
Dieter Koenig: Issue (page 31) - default assignment of business stakeholder - decide whether this is need or standard business stakeholder assignment is sufficient
Dieter Koenig: Issue (page 31 - last bullet) - need general rule for automatic assignments of "task initiator" or "business stakeholder" for subtasks (not just for "ad hoc" subtasks)
Dave Ings: AI: Phil will prepare his lean task proposal for the next meeting (in two weeks time)
Dave Ings: Meeting adjourned

Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings