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 692 - Types, variables and tokens: Dual variable objects are for different purposes in the abstract and portable context.
Summary: Types, variables and tokens: Dual variable objects are for different purposes...
Status: RESOLVED WONTFIX
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 11:55 UTC by Greg Ritzinger
Modified: 2004-08-12 20:09 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2004-04-26 11:55:12 UTC 
Monica: Types, variables and tokens: Dual variable objects are for 
different purposes in the abstract and portable context, correct? 
Either specify or delete redundant object.

David: I don't think I completely understand the point you are trying 
to make.

Monica: These are defined at the choreography definition and at the 
interaction level. This creates a conundrum because what is the 
master, is override allowed, and should the description and the 
technical contract exist in the same specification. This is one of my 
more general points.
Comment 1 Martin Chapman 2004-08-12 16:09:35 UTC 
we do not have  abstract portable concrete levels anymore. so closed.