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 916 - If a "free" variable in an enclosed choreography is not BOUND then what is the variable's status?
Summary: If a "free" variable in an enclosed choreography is not BOUND then what is th...
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: Martin Chapman
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-12 18:36 UTC by Greg Ritzinger
Modified: 2004-12-01 16:28 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2004-10-12 18:36:31 UTC
If a "free" variable in an enclosed choreography is not BOUND then what 
is the variables status? Does it have a value or is it said to be 
undefined? My concern is if any conditional logic is based on the value 
of a free variable that is UNBOUND it may have unexpected consequences.

One possible solution is to add a default value to the definition of 
the variable within the choreography in which it is defined. The 
semantics would be such that free variables that are not bound take on 
the default value. The absence of a default value for a free variable 
that is UNBOUND would result in a type error or a warning being 
generated on parsing the CDL file(s) in which it is defined.

At alternative would be to have no default value and simply add the 
necessary text (above) so that it is made clear how to parse a CDL 
document and what to report as an error or warning.