RE: diagram elucidating some core WSA concepts and relationships

Here are two diagrams that I hope will shed light on some of the core
concepts and relationships.
 I've tried to make them consistent to the extent possible with Frank's
diagram. Though this was not totally accomplished, I think the two diagrams
could serve as another good pivotal point for discussion.

The first diagram depicts the concepts of service, agent, description, URI,
legal entity etc. I hope it is self explanatory. I have depicted in the
diagram the specification of the  service and also the execution of a
service. I think depicting and talking about the specification, but also the
execution of service in the wsa document will facilitate our discussion of
qualities, such as management.
In particular, a service consists of one or more ports, a protocol handler
(those two comprise a service's interface) and of an agent, the part of the
service that performs the service task. Somewhere on the Web, there is a
service description, identified by a URI. The service description mainly
describes the task, the protocol and the ports of the service (the
description could have additional properties but these are the main ones).

The second diagram depicts interactions through message exchages of a
service provider and a service requestor. Notice, the interaction involves
only execution of the requesting and providing. It presupposes that
discovery, interpretation of a service description etc have already been
accomplished. It also takes the "symmetrical" position on provider and
requestor that many of you supported in the telecon and recent message
exchanges. 

 Cheers, 
 --Katia