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

Re: [soapbuilders] SOAP Encoding

From: <Noah_Mendelsohn@lotus.com>
Date: Fri, 20 Apr 2001 10:33:31 -0400
To: soapbuilders@yahoogroups.com
Cc: xml-dist-app@w3.org
Message-ID: <OF9FE81C17.5DDB83F5-ON85256A34.004F8B91@lotus.com>

Darshana writes:

>> Hi,
>>
>> I have some doughts on the encoding method defined in the SOAP
>> specifiation, can some one help me on that.
>>
>>      1.  In the SOAP Envelope, should there be the ecodingStyle
>>         attribute all the time?
>>      2.  Should every Service(Method) deployed be affiliated
>>         with a namespace holding the schema definig the elements
>>         & their types? If so where it is held ?
>>      3.  If answer for the second is yes ,does the receiver of
>>         the message have to go thorugh the schema in order to
>>         parse it?
>>
>> thanx,
>>

According to [1]:

"The SOAP encodingStyle global attribute can be used to indicate the
serialization rules used in a SOAP message. This attribute MAY appear on
any element, and is scoped to that element's contents and all child
elements not themselves containing such an attribute, much as an XML
namespace declaration is scoped. There is no default encoding defined for a
SOAP message."

...and by the way...

"A value of the zero-length URI ("") explicitly indicates that no claims
are made for the encoding style of contained elements. This can be used to
turn off any claims from containing elements."

I think that's pretty clear.  You can put it on envelope if you want, but
the significance is to establish a default encoding for the entire envelope
(which you can override or turn off in a nested scope if you like).  On the
other hand, as new intermediary services are defined, I think it's
increasingly unlikely that a single encoding will apply to an entire
envelope.

Now what I think is an interesting question, is whether you can have
multiref relationships across two or more headers which are separately
labeled with the same encoding?  Given that multirefs can be shared across
headers at all (I believe they can), I think the answer must be "yes".
Otherwise, you could do this for at most one encoding (I.e. one identified
on the envelope, which is why this relates to your original question.)

I'm cc:'ing dist-app (with apologies for cross-posting) as I think this
should turn into an issue for clarification in future versions of the
specification.

[1] http://www.w3.org/TR/SOAP/#_Toc478383495

------------------------------------------------------------------------
Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------------
Received on Friday, 20 April 2001 10:36:12 GMT

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