- From: Liu, Kevin <kevin.liu@sap.com>
- Date: Sat, 7 May 2005 01:33:02 +0200
- To: "Amelia A Lewis" <alewis@tibco.com>, <www-ws-desc@w3.org>
Hi Amy, To me, the template itself fits better in the part 2. If you also have an exmample of applying the template, we can certainly include it in the Primer. Make sense? Best Regards, Kevin > -----Original Message----- > From: www-ws-desc-request@w3.org > [mailto:www-ws-desc-request@w3.org] On Behalf Of Amelia A Lewis > Sent: Thursday, May 05, 2005 11:19 AM > To: www-ws-desc@w3.org > Subject: MEP template > > > Heylas, > > At some point, there was a comment asking for a template for Message > Exchange Patterns. I'm working on the sample additional patterns for > the primer, and noticed the lack of guidance myself (although > it's easy > enough to capture the pattern). So, here's proposed text for a > template. This could be included in: a) Adjuncts, as part of the > description of extensibility, or b) the primer, in section 5.4.4, as > additional guidance. > > Pattern Name > > This pattern consists of [number] message[s, in order] as follows: > > [enumeration, specifying, for each message] A[n optional] message: > > * indicated by a Message Label component whose {message label} is > '[label]' and direction is '[direction]' > > * [received from|sent to] ['some' if first mention] node [node > identifier] > > This pattern uses the rule [fault ruleset reference]. > > An operation using this message exchange pattern has a {pattern} > property with the value '[pattern URI]'. > > Note: the "received from" and "sent to" are always from the point of > view of the service, and participating nodes other than the > service are > implicitly identified as the originators of or destinations for > messages in the exchange. > > Amy! > -- > Amelia A. Lewis > Senior Architect > TIBCO/Extensibility, Inc. > alewis@tibco.com > >
Received on Friday, 6 May 2005 23:34:37 UTC