The only caveat I'd make here is related to the earlier discussion about visibility. In a B2B scenario, I may not want to publish to all participants a definition that includes "all the behaviors of all the roles". --Jon Assaf Arkin wrote: > > Burdett, David wrote: > >> So how about as a requirement ... >> >> "The choreography specification must provide a method of defining the >> rules and sequence for exchanging messages between two or more roles >> (e.g. buyer, seller, etc) that: >> >> a) Provides a single choreography definition that covers all the >> behaviors of all of the roles >> b) Treats each role equally >> c) Specifies messages in an abstract way, i.e. independent of the >> precise data structures and transport binding." >> >> David >> > Of course I would say +1 to this, since it defines the problem we're > trying to solve and provides a good pattern for any solution. > > arkin > > > >Received on Tuesday, 13 May 2003 12:45:23 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:17 GMT