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 281 - MEP as a simple choreography
Summary: MEP as a simple choreography
Status: RESOLVED WONTFIX
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Steve Ross-Talbot
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 276
Blocks:
  Show dependency tree / graph
 
Reported: 2003-07-29 14:37 UTC by Greg Ritzinger
Modified: 2004-03-24 22:22 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2003-07-29 14:37:41 UTC 
Define MEP as a choreography then use (compose) this with others to form a 
higher-level choreography.  Alternatively we could just view an MEP as a 
pattern that a Web Service will do.

A possible definition of an MEP might include binding to Web Services, whereas 
Choreography is above that and does not include an explicit binding except for 
a binding to MEPs.  It was suggested that may be at this stage we needed to 
have some creative ambiguity in this area until WSDL 1.2 is fixed.
Comment 1 Martin Chapman 2004-03-24 17:22:21 UTC 
an MEP is not a choreography as a choreography contains more than than just 
message exchanges (such as guards, composition)