Dear all,

as just discussed pls. find below the summary of the new proposed issue we have just talked about:

TARGET: WS-HumanTask

DESCRIPTION: Task list clients often deal with many human tasks, performing the same action on them at the same time, e.g., when a user operates on a selection of several tasks in a UI application. Today in WS-HT this is accomplished by invoking a particular operation for each single human task of such list. When dealing with larger numbers of human tasks this involves a lot of communication between client and server and thus should be optimized. For example instead of a claim operation that takes a single task id as an input we may want to offer a batch claim operation that processes a set of task ids in a single operation.

PROPOSAL / THOUGHTS: Analyse the operations in chapter "6.1 Operations for Client Applications", and particularly "6.1.1 Participant Operations", and define which operations are likely to be called for a set of human tasks and deserve optimization by offering a corresponding batch operation. Specify these batch operations (input / output / fault messages). Agree on a naming scheme for batch operations that makes clear which original operation the are derived from. .

Best regards,

Gerhard

Gerhard Pfau

IBM Senior Technical Staff Member

Lead Architect, Human Task Manager

Member, IBM Academy of Technology Member, Technical Expert Council CR

phone: fax: mobile: +49-(0)7031-16-4899 +49-(0)7031-16-4890 +49-(0)160-533-6578

"Make everything as simple as possible, but not simpler." - Albert Einstein

Legal Information: IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Martin Jetter; Geschäftsführung: Erich Baier Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294