Re: Partial executability/ determinism of a Chor description language

Burdett, David wrote:

> <DB>I think it more likely that the policies will most often apply to 
> services rather than choreographies. For example the "no international 
> orders" policy could apply to *all* orders. The actual choreography 
> used to place the order is irrelevant.</DB>
>
That's precisely my point. I want to find specific services based on the 
policy. For example, if the policy says "no international order" and 
some service says "I use this policy" and "My country != US", then I 
would not bother using that service.

> <DB>Yes there is. But it is only really relevant to your internal 
> business process (or orchestration) rather than to the choreography 
> because ultimately only the sender of the order and nobody but the 
> sender of the order can decide whether or not to send the order - it's 
> a private process.</DB>
>
Let's say that I find a service. I find a policy. There is no 
association between the policy and the choreography. Finding the policy 
is as useful as knowing that the service definition was created on a 
Sunday afternoon.

But if there is some way for me to determine that the service would 
apply the policy as part of the chorography, then MY implementation can 
do a lot of interesting things, like favoring or avoiding that 
particular service. Of course it's only relevant to my internal 
implementation, and if my internal implementation never evaluates the 
policy it would still be acting based on the choreography. Which is 
something I don't belive we've refuted so far.

But if the policy cannot reference the choreography then it becomes a 
useless policy. In case of doubt, I am not saying that the choreography 
should reference the policy, but that the policy should reference the 
choreography.

arkin

> arkin
>

Received on Friday, 30 May 2003 17:19:55 UTC