Re: [bpel4people] New Issue: Relationship between composite taskand routing pattern syntax

[Ravi Rangaswamy <ravi.rangaswamy@oracle.com>]

Didn't notice that Luc had already added this as section 3.4, so we 
don't need this issue anymore.

Thanks,
Ravi

Ravi Rangaswamy wrote:
> Target: WS-HumanTask
>
> Description: There is no section detailing relationship between 
> composite task and routing pattern syntax
>
> Proposal:
>
> Introduce new section as below. This section will capture resolution 
> in BP-92 and BP-108.
>
> 4.8 Composite Tasks and Routing Patterns
>
> Composite task syntax describes what different subtasks are executed 
> in a complex task scenario. Routing patterns syntax describes who 
> participates in such complex task scenario.
>
> A composite task, including subtasks of different task types, can be 
> described only using the composite task syntax. A routing task 
> containing a dynamic number of subtasks derived from the cardinality 
> of the set of assigned people can be described only using the routing 
> task syntax.
>
> Both syntax flavors MAY also be used in combination, which means that 
> a composite task MAY include a complex people assignment and that any 
> task defining a complex people assignment MAY become a composite task 
> at runtime when adhoc subtasks are created. The runtime instantiation 
> model and observable behavior for task instances MUST be identical 
> when using composite task or routing pattern syntax.
>   When composition is defined on a task, the composition MUST be 
> applied for each of the potential owners defined in the task's people 
> assignment.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php