see:


"3.5.2 Semantics of the Architectural Models

The different models in the architecture focus on different aspects of the interoperability issues between Web service agents. The Message Oriented Model focuses on how Web service agents (requester and provider agents) may interact with each other using a message oriented communication model. The format of messages as XML infosets and the structuring of messages in terms of envelopes, headers and bodies, as described in that model, acts to lay a foundation for the standard comprehension of messages exchanged between Web service agents."


Cheers


Steve T


On 31 Jul 2006, at 13:52, Ashley at Metamaxim wrote:


Frank wrote:
 
> In the sense that an orchestration describes what happen at a single partner side, the processes I sketched are
> in fact orchestrations.
Then I am confused. The definition of orchestration that Steve R-T gave earlier in this thread was:
 
> orchestration
>
An orchestration defines the sequence and conditions in which one Web service invokes other Web
> services in order to realize some useful function. (i.e., an orchestration is an executable description of
> the pattern of interactions and the conditions that must exist for those interactions to take place that
> are both internally and externally observable that a Web service agent must follow in order to achieve
> its goal.)
But the examples you gave to describe mismatches, there was simply a description of the pattern of messages expected by the two parties. There was no indication that I could see that one Web service was invoking other Web services, as required by the above definition.
 
(Mind you, the part of this definition in parentheses is not very clear. What is a "Web service agent"?)
 
Can you unconfuse me, please!
 
Rgds
Ashley


__._,_.___


SPONSORED LINKS
Computer software Computer security software Computer software program
Computer fax software Computer virus software


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to