-------------- Message Model ------------------

This file contains notes of things that I found problematic in
compiling the OWL version of the WSA specs.

1. Hyperlink of message transport does not work.

2. 2.3.1.2.2 Delivery policy constrains message transport but "A   
   Message Transport is a mechanism that may be used by agents to
   deliver messages." (2.3.1.13.1) A Message Transport cannot be
   contained in a policy, rather it should be specified by the policy
   (in any case, the policy should specify which message transport to
   use).

3. 2.3.1.2.2 Delivery policy may be expressed in a policy description
   language  
   The Policy model does not a concept for "Policy Description
   Language", but it has a concept for "machine processable form" (A
   policy may be described in a machine processable form. 2.3.4.8.2).
   What is the difference?

4. 2.3.1.2.2 Delivery policy may express the quality of service
   associated with delivering a message by a message transport
   mechanism
  
   What does this mean?  A transport mechanism has an intrinsic qof.
   What should the policy specify?  Is the minimum quality of service?


5. 2.3.1.7.2 "a message exchange pattern is a template."  It suggests
   that there should be a language to express the template in.  So for
   uniformity with other definitions it should be that a MEP is
   expressed in a "machine processable form" as policies are
   (2.3.4.8.2).

6. typo: a message exchange pattern may realize A message correlation
   (missing A)


7. Typo: 2.3.1.9.2 a message sender may be an intermediary,  it should
         be a message RECEIVER may be an intermediary

------------------------------------------------

Service Model

8. 2.3.2.5.2 typo... repeated specification that a service has service
		     semantics
   a service has service semantics 
     ...
   a service has a service semantics 


9. 2.3.2.6.2 it is quite confusing to assert:

a service description is a description of the service's interface
a service description is a description of the service's semantics 
a service description contains a description of the messages that are exchanged by the service 

  a. is this one description or multiple descriptions? ie the
description of the interface may not be the same as the description of
the semantics.

  b. what is the difference between the description of the interface
and the description of the "mesages that are exchanged by the
service?"


10. 2.3.2.8.2: a provider agent is a Web service software agent 
    There is a problem here between the provider being the Web service
    or an agent.  Services are realized by agents (2.3.2.5.2), so how can the
    can the provider be both the Web service and the agent?

---------------------------------------------


11. In Message model (2.3.1.3.2) a message has one or more message
recipients I assume that that "Message Recipient"is the same of
"Message Reciver"


12. Similarly, in (2.3.1.3.2) A message is delivered by a message
transport system. I assume that "transport system" is actually
Message_Transport


13. Service Description Language is underfined: there are assertions
such as 2.3.1.3.2 "a message may be described using a service description
language", but the concept of Service Description Language is never defined.


14. Service invocation is undefined: 2.3.1.7.2 "a message exchange
pattern may describe a service invocation"


15. The concept of state is undefined in (2.3.4.8.2): "A policy is a
constraint on the states achieved by agent (interpreted as: a policy
constraints the states achieved by an agent)".  Similarly, the concept
of "goal state" is undefined in (2.3.2.12.2) a service task is
associated with one or more intended goal states.


16. The concept of contract is undefined in (2.3.4.7.2): "A person or
organization may agree to a legally binding contract."


17. The concept of policy guard owner is undefined in (2.3.4.9.2): "A
policy guard has an owner responsible for establishing the guard."


18. The concept "Physical Address" is undefined in (2.3.4.7.2): "A
person or organization has a physical address."


19. The concept "URI" is undefined in (2.3.3.3.2): "An identifier may
be realized as a URI"


20 Service semantics virutally impossible to represent