Well, yes and no. If we are talking about business functionality and RWE, the, of cause, it is the application level semantics. If we are talking about operation name meaning (yes, implicitly affect by the application level semantics, I hope) and, especially, message content (like XML tag semantics in the document style WS), the influence of application level semantics is not so obvious here. The mismatch between message semantics and application semantics has to be resolved, i.e. we have to have a dedicated mechanism in place for this job.
Ideally, all decisions and knowledge about a service have to be obtained from the Service Description document, which is supposed to be consistent (operation semantics matches application semantics). However, there is and will be a transition period to this ideal state; operation semantics is important during this period, I think. - Michael ----- Original Message ---- From: Ashley at Metamaxim <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, August 30, 2008 10:53:47 PM Subject: Re: [service-orientated-architecture] Distinction between "Choreography" and "Orchestration" > WS and REST are just the mechanisms, its the application level > semantics that are important so both REST and WS can do this, but you > have to define the work at the next level up. > Steve Thanks. I think that is what Anne was saying too. I agree. Rgds Ashley___
