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 666 - Why specify a message type in the interaction?
Summary: Why specify a message type in the interaction?
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: Greg Ritzinger
QA Contact:
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-13 10:35 UTC by Greg Ritzinger
Modified: 2004-09-07 17:25 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2004-04-13 10:35:47 UTC 
Why specify a message type in the interaction? Why not in the associated
WSDL? Could they be different? How do you guaranty that they cannot be
different if specified in two different places?
Comment 1 Martin Chapman 2004-05-18 16:16:57 UTC 
think that there is no type in interact but needs tobe verified
Comment 2 Martin Chapman 2004-08-12 15:16:34 UTC 
resolved at aug f2f, with a choice of message type or channel.
reassigned to editorial
Comment 3 Greg Ritzinger 2004-09-07 17:25:02 UTC 
Fixed in spec draft 2004-09-07