RE: updated service description

[michael.poulin@uk.fid-intl.com]

Hi Ken,
 I have two notes to the update (actually, to the doc as it is with the update):

1)	There is an entity in the Service Description diagram named "Interaction Policies & Contracts". I think that Contract belongs to another area than service description because it is 'personalized' based on consumer/provider agreement. Yes, logically, a Contract is a special type of description but it would be more comprehensive if we put it into Interacting with Services Model  section. 

2)	You have mentioned <A discussion of how version designation/value should be impacted by change of version of any of its components (or any descriptions?) still needs to be discussed.> To me, a version of the service is one of very important characteristics of the service description (and, respectively, of the service contract). I would propose placing version as an entity in the Service Description diagram either under Identity or at the level of Service Description entity because version affects Service Reachability, Service Functionality, Interaction Policies, and Service Interface entities. I have published a few thoughts about SOA service versioning in SOA-WebServices Journal (http://java.sys-con.com/read/250503.htm ).

- Michael