Policy: Web Services Interoperability
Purpose
The purpose of the policy is to increase the likelihood that myGrid services will interoperate with each other and with independently-developed web services.
Background
Web Services are a relatively new family of techniques, technologies and toolkits for loosely-coupled distributed systems. Various groups are attempting to standardize the necessary protocols, principally:
However, the technologies are immature and many necessary standards are either missing, in draft form only, ambiguous or incomplete. Thus different toolkits implement their own, sometimes clashing, understandings of the existing standards.
To address the problem, The
Web Services Interoperability Organzation (WS-I) has attempted to identify a well-defined core of the most important standards and to define a single interpretation for aspects that are incomplete or ambiguous. It is intended that adoption of these proposals by different providers of toolkits, services and client applications will improve the likelihood that they will interoperate, and thus encourage and accelerate Web Services adoption and deployment adoption.
Policy
Web Services and Web Servce clients developed by the myGrid project shall conform to the following WS-I profiles and the standards identified within them, insofar as such conformance is supported by myGrid's chosen Web Service toolkits:
Particular consequences
The following consequences of this policy are within the control of the project:
| Ref. | Description |
| 1 | All myGrid service implementations shall provide a specification of their port types via a WSDL document containing no bindings. |
| 2 | All myGrid service implementations shall provide a method of obtaining a WSDL document for the service instance, containing the binding(s) for the service instance. |
| 3 | All myGrid services shall support a SOAP binding for each WSDL port type [R2401]. They may support aditional bindings, such as MIME |
| 4 | All SOAP bindings shall use rpc-literal or document-literal style; SOAP binding body, header, envelope and fault elements shall contain a "use" attribute with the value "literal" and must not contain an "encodingStyle" attribute. |
Implementing the Policy
To be supplied
--
NickSharman - 29 Sep 2003