RE: Partial executability/ determinism of a Chor description language

David, embedded ...

Why human and not machine-processable? Let's assume we have the
>technology to evaluate some of these policies automatically. Why not use it?
><DB2>Having the technology is easy. The hard part is the standardization 
>and implemenation required before the technology can work. For example, 
>for this simple problem to work you need generally agreed definitions how 
>"I do not accept international orders" is described as well as have a 
>registry containing this information that is trusted - UDDI completely 
>fails on the trust issue.</DB2>

if (qname:internationalOrder)
         then send reject message
         else send accept message

"qname:internationalOrder" is binded 
to:  XPATH("/PO/DeliveryAddress/Country") != $MyCountry

Rgds, Ricky