[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW Issues from F2F
The following new issues were agreed to be raised and opened
at the F2F: New Issue: Complete HT section 3.3, Routing Pattern intro New Issue: HT section 3.4.5 Review for correctness the
default sub-task assignments (an example is the default initiator assignment
for sub-tasks activated automatically). New issue: HT section 3 need new text defining the
relationship between composite tasks and patterns (Issue-85 is a sub issue of
this) and validate the design principle of patterns being able to be built on
top of composite tasks- this is issue XXX New issue: HT section 3.2.1 change activation pattern to
creation pattern New Issue: HT Section 3.2.1 review the correctness of
sub-task creation time (e.g. is it currently too prescriptive) [probable link
to 3.4.5 issue above] New Issue: HT section 3.6.5. Review 1st paragraph and either
make more specific and/or more generic e.g. do we need new apis. New Issue: HT section 3.6.5 2nd paragraph move to routing
patterns section 3.3 New Issue: HT 4.5 Is Multi-instance on composite sub-task
necessary? link to XXX New Issue: HT 4.5 sharing of comments need to be addressed New Issue: HT 4.6.1.1. Review the collaborate attribute and
its definition (e.g. is it too broad a control), and possible remove task
output text New issue: HT 4.6.1.2 Need to define completion behaviour
for sequential New Issue: HT 4.7.1 Need to specify when completion criteria
has to be evaluated New Issue: HT 4.7.1 simplification of critereon syntax (e.g.
removal of 'and' operator) New Issue: HT 4.7.1. Should we allow the attachment of
completion criteria to a task element (with or without sub-tasks). If the
answer is yes we need to define what happens after the completion condition evaluates
to true for both automatic and manual. New issue: HT 4.8 Clarify Escalation behaviour New Issue: HT 4.9.8 review whole section regarding parent
and subtask operation propagation e.g. if a subtask faults must the parent task fault or is
this configurable. We may need to refactor all of 4.9. issue YYY New Issue: HT 4.9.4 add a normative statement that resume on
sub-task is not allowed when parent is suspended link to YYY New Issue: HT 6.1.1 clarify complete operation w.r.t the
sequential pattern. dependant on issue-85
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]