W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2001

Re: Toss section 5 (create SOAP-lite)

From: Gaertner, Dr., Dietmar <Dietmar.Gaertner@softwareag.com>
Date: Tue, 31 Jul 2001 13:48:58 +0200
Message-ID: <DFF2AC9E3583D511A21F0008C7E62106188E06@softwareag.com>
To: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
The SOAP 1.1 spec as well as the SOAP 1.2 working draft section 5
"SOAP encoding" defines simple and compound types and "spells out
some (type) concepts" in more detail.

The SOAP simple type system based on 
"Element declarations corresponding to each of the simple types
in the XML Schemas Specification"
may be be redundant.

Describing the encoding and usage of some of the datatypes for
which the schema spec leaves too much room for interpretation
is important, and, IMHO *belongs* in a spec like SOAP whose
main goal is interoperability.

Finally, preciseley describing the encoding of structured data
(which also map well on structures found in popular programming
languages) also *belongs* into the SOAP spec otherwise you end
end up with many different interpretations and implementations.
One can like or not like the SOAP Arrays, but they are clearly
defined. XML schema provides many ways to encode arrays.
Also, precisely defining how RPCs have to be encoded is essential.

Thus my conclusion is: Simplicity is important, but it comes
after completeness and soundness. Overly simplistic approaches
don't help.

Regards, Dietmar
Software AG  
Received on Tuesday, 31 July 2001 07:49:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:03 GMT