RE: Comments on Editor Notes In Section 4.1

[Danny Thornton <danny.thornton@scalablearchitectures.com>]

In reply to Michael's comments, the mechanisms to enforce policies and
contracts are likely to be identical at the IT level. This is a core
principle of the Policies and Contract section. In the interest of
parsimony, derivations into the many types of policies and contracts are
not discussed in the policies and contract section. Those derivations
could be discussed in other sections where appropriate, in the Service
Description section for example.


In response to:

M.P. This note is very much Web Services centric. We, probably, have to
stay away from promoting particular technology.

About the following comment:

Comment: A message can be an xml document with no associated protocols
for delivery. The endpoint defines the protocol, for example soap or
sockets or whatever you like. One way to characterize this would be to
make the relationship between Message and Action dependent on Endpoint
and then associate protocols with the Endpoint. 

The OASIS SOA Reference Architecture uses messages as a means of
interactions between services. An xml document is an example of one
type of message, it could be a string or many other data types. After 
marshalling and before unmarshalling, all messages are a bunch of bits
and at that point the bits are dissassociated from the protocol. It is
the protocol that is used to deliver the bits of information. So the
messages themselves and the protocols to deliver the message are
separated at the transport layer no matter what type of distributed
computing you use. It is the endpoint, NOT THE MESSAGE, that defines
the protocol the message is delivered with. The diagram depicts the
message associated with the protocol but does not associate the protocol
with the endpoint. This is also the point that is being made in the
editor note, it is just not reflected in the diagram.

Danny