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 683 - Clarify that the reference with support from tokens, token types, etc.
Summary: Clarify that the reference with support from tokens, token types, etc.
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Editorial (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact:
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-19 15:57 UTC by Greg Ritzinger
Modified: 2005-01-04 20:42 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2004-04-19 15:57:15 UTC
Section 2.3.4
Clarify that the reference with support from tokens, token types, etc. 
are statically defined but dynamically bound. This is clear from the 
confusion in WS-BPEL, and we should be clear of the functions we 
describe and use.
Comment 1 Martin Chapman 2004-05-20 13:45:30 UTC
assign to editors
Comment 2 Greg Ritzinger 2004-09-07 17:31:29 UTC
Not editorial.  Please provide a proposal.
Comment 3 Greg Ritzinger 2004-10-11 18:58:35 UTC
Clarification from Monica: 

This is actually Section 2.3.4 (not 2.4.3) as stated in the call; 
however it relates to 2.4.3.

In Section 2.3.4: ...."The element reference is used for describing the 
reference type of a party, being the target of an Interaction, which is 
then used for dynamically determining where and how to send/receive 
information to/into the party.".....

As Nick indicated (in Section 2.4.3), the specification indicates that 
the tokens (aliases) are defined ahead of time. They are then 
dynamically bound - i.e. used as specified above in Section 2.3.4. Since 
the Token's description in Section 2.3.4 occurs after the description of 
the use of tokens (section 2.4.3), it could be confused. I still think 
this is pretty much editorial.