[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

new SOAP Encoding spec issue

• From: Jacek Kopecky <jacek@i...>
• To: xml-dev@l...
• Date: Mon, 15 Oct 2001 15:49:01 +0200 (CEST)

 Hi all. 8-)
 I've this issue with the current specification of the SOAP
Encoding: it does not define strictly the mapping of the encoding
to XML Schema. This has caused, for example, a very weird way of
specifying the array information attributes in WSDL [1]:

<complexType name="ArrayOfFloat">
  <complexContent>
    <restriction base="soapenc:Array">
      <attribute ref="soapenc:arrayType"
          wsdl:arrayType="xsd:float[]"/>
    </restriction>
  </complexContent>
</complexType>

I think that specifying an array's type should be possible
without resorting to extensions from a different namespace, but
even if this is necessary, in my opinion the namespace should be
soap-encoding, not of the particular language that needs to say
"the message contains an array of floats".

So I think we should add some wording to say how exactly types
are described in XML Schema and what to do with schemas that
don't map back to our encoding (for example complex types
containing application-defined attributes.)


                            Jacek Kopecky

                            Idoox
                            http://www.idoox.com/

• Follow-Ups:
  • Re: new SOAP Encoding spec issue
    • From: Jacek Kopecky <jacek@i...>

• Prev by Date: Re: Comment on W3C Patent Policy WG Response
• Next by Date: RE: Cutting special deals for open source developers -- noway!
• Previous by thread: XML Data from ASP cached/erroneous
• Next by thread: Re: new SOAP Encoding spec issue
• Index(es):
  • Date
  • Thread