W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Re: using xsi:type with the SOAP encoding rules

From: <noah_mendelsohn@us.ibm.com>
Date: Thu, 28 Feb 2002 20:43:54 -0500
To: <tjewald@develop.com>
Cc: "'XMLDISTAPP'" <xml-dist-app@w3.org>
Message-ID: <OFE5E8BC5C.A31076CA-ON85256B6E.00586561@lotus.com>
Stay tuned.  Gudge and I have an action item to write this up.  Short 
answer:  validation is not requried.  When you're not validating, you'll 
know the name of the type, but not even whether it is simple or complex. 
If you choose to validate, then the type must match the element.   So, if 
your element is a struct, it should be complex. 

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







"Tim Ewald" <tjewald@develop.com>
Sent by: xml-dist-app-request@w3.org
02/23/2002 01:57 PM
Please respond to tjewald

 
        To:     "'XMLDISTAPP'" <xml-dist-app@w3.org>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        using xsi:type with the SOAP encoding rules


What happens if a SOAP encoded message uses xsi:type to describe an
element's content in terms of a XSD complexType? Is this explicilty
allowed or disallowed under the SOAP encoding rules, or is it simply not
addressed?

Thanks,
Tim-
Received on Thursday, 28 February 2002 20:59:26 GMT

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