[interop] Starting point & testing scenario

["Murray, Bryan P." <bryan.murray@hp.com>]

Using WS-ResourceProperties has the interesting side-effect of making
the WSDL document alone potentially insufficient to communicate with
resources supported by the Web service.

There are 2 cases where the WSDL document may be sufficient:
1) An operation in the WSDL that returns an EndpointReference might
offer a mechanism to locate already existing resources or to create new
resources.
2) There is only 1 resource supported by the Web service and no SOAP
header(s) are required to identify that resource. Unfortunately, WSDL
does not require that all SOAP headers be listed and so it may be
necessary to send a message to test this case.

In the case of our WSDM interop example (WeatherStationManageability
service), we do not have an operation that returns an EndpointReference,
and it is not defined as to whether a SOAP header is required to
identify the resource. In WSDM we also are not creating resources, but
instead refer to fixed resources that already exist.

For these reasons, I think it may be necessary for managers to have an
EndpointReference as a starting point.

Another thought: I think our goals are more around testing the
interoperable exchange of messages and access to manageability
information rather than the successful  runtime digestion of
manageability WSDL. Our testing would be a little simpler if we all
write manageability endpoints that match exactly the same manageability
WSDL (except for the endpoint address) and managers start with only the
EndpointReference. In this way the manager already knows what operations
and properties are supported and can concentrate on sending requests and
processing responses.

Comments?

Bryan