- From: Amelia A. Lewis <alewis@tibco.com>
- Date: Tue, 4 Mar 2003 15:16:44 -0500
- To: www-ws-desc@w3.org
Hey, folks, Following up from the action item at the face to face, I would like to solicit text for motivations/use cases for participants in the MEP beauty contest. Contestants should provide text suitable for inclusion in the MEP descriptions, which will go into a subsection called "motivation" or possibly "usage". A preliminary (quickly-written) sample is provided below; other formats will be accepted. The editors will not be guaranteeing that the pristine purity and clarity of submitted text will be reflected into the document in CVS as written (translation: editors will use the submitted text as a foundation, but may change things out of all recognition). Submissions should use the current abstract numbering to identify the MEP. MEP7: This Message Exchange Pattern is commonly encountered in messaging systems, where it might be referred to as "multicast solicit/response". The classic multicast discovery mechanism is an example: the service broadcasts or multicasts a message to all listeners, asking who provides capability X; each listener may respond (in which case the service may detect and return a fault), return a fault, or do nothing. The content model shorthand is OUT, IN*, with the proviso that any message may trigger a fault. Amy!
Received on Tuesday, 4 March 2003 15:17:28 UTC