ETF: Issue 48 Discussion

During the last ETF call we discussed issue 48. To summarise the results 
of our discussion:

(i) We agreed that an implementation of SOAP could be conformant without 
supporting the SOAP encoding. i.e. Support of the SOAP encoding is 
optional in implementations.
(ii) We noted that the SOAP encoding is dependent on the SOAP data model 
and that the RPC convention is dependent on the SOAP data model and the 
SOAP encoding.
(iii) Tests would be provided for implementations claiming conformance 
with the SOAP encoding.

To resolve issue 48 we proposed the following two actions:

(a) Instructing the editors to clarify the optional nature of the SOAP 
encoding in the specification and to clearly describe the dependencies 
between SOAP, the SOAP data model, SOAP encoding and RPC convention.
(b) Instructing the conformance subgroup to include tests for SOAP 
encoding conformance, but to note the optional nature of the SOAP 
encoding in the test suite. i.e. SOAP implementations may choose not to 
implement the SOAP encoding, but if they claim conformance with the SOAP 
encoding they must pass the SOAP encoding conformance tests.

Regards,
Marc.

-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.

Received on Monday, 22 October 2001 06:53:16 UTC