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 693 - Variable combinations (Issue TVT-02)
Summary: Variable combinations (Issue TVT-02)
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Variables (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-04-26 12:55 UTC by Greg Ritzinger
Modified: 2004-12-01 16:51 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2004-04-26 12:55:00 UTC
Monica: Variable combinations (Issue TVT-02: Complex evaluation 
conditions could be made available (for algorithmic purposes) outside 
of the choreography as it is not a core function. That allows the capability 
to further modularize the language, as mathematical algorithms may have
broader utility that only within the choreography.

David: Agreed. At a minimum, an evaluation condition is given a name. 
When the choreography is performed, each name has to be
mapped to a condition or expression consisting of multiple conditions 
that can actually be evaluated. By "allowing" complex evaluation
conditions in the choreography, then the choreography designer can 
express the complex condition if he wants to or let it be evaluated 
later.

Monica: My point was to say that the complex conditions may not be held 
in the choreography, but be imported for use or referenced. If agreed 
upon, and the issue TVT-02 handled, this should be revised.
Comment 1 Martin Chapman 2004-08-12 16:15:37 UTC
there are a number of ways callout functions are supported e.g. through the 
query language/xpath, an explict interaction with a web service.