This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 869 - There is no explicit mechanism for defining a repeating set of activities.
Summary: There is no explicit mechanism for defining a repeating set of activities.
Status: RESOLVED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Structural (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: WS Choreography mailing-list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-07 11:13 UTC by Steve Ross-Talbot
Modified: 2004-09-29 20:20 UTC (History)
1 user (show)

See Also:

Attachments

Description Steve Ross-Talbot 2004-09-07 11:13:47 UTC 
There is no explicit mechanism for defining a repeating set of activities, that would also enable a non-
observable condition to be represented. Currently the only mechanism that supports repetition is where 
a workunit is defined with a 'repetition' attribute that represents a predicate that must be true for the 
workunit to be performed again (i.e. a do-while loop). This is counter-intuitive and runs against one of 
our CSF of simplicity.

What is needed is some construct in which a repetition can be defined that is explicit and can stand on 
it's own rather than being embedded into some other construct, such that repetitions can be defined 
that have observable and non-observable conditions governing their termination.
Comment 1 Martin Chapman 2004-09-09 19:57:26 UTC 
proposal being worked on
Comment 2 Greg Ritzinger 2004-09-29 20:20:10 UTC 
Can be supported by use of a variable and this variable can be set by the
private implementation (behavior)

Sept 04 F2F