W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2002

Re: Issue 4: Use of namespace attribute on soap:body

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Thu, 04 Jul 2002 18:12:29 -0700
Message-ID: <3D24F27D.A2EE2AC3@webmethods.com>
To: Jacek Kopecky <jacek@systinet.com>
CC: Martin Gudgin <mgudgin@microsoft.com>, www-ws-desc@w3.org
I agree with Jacek. The spec as confusing it might be, seems specific on this:

"If the operation style is rpc each part is a parameter or a return value and
appears inside a wrapper element within the body (following Section 7.1 of the
SOAP specification). The wrapper element is named identically to the operation
name and its namespace is the value of the namespace attribute."

"If use is encoded, then each message part references an abstract type using
the type attribute. These abstract types are used to produce a concrete message
by applying an encoding specified by the encodingStyle attribute. The part
names, types and value of the namespace attribute are all inputs to the
encoding, although the namespace attribute only applies to content not
explicitly defined by the abstract types."

So, only for doc/literal (style/use) combination namespace attribute value has
no applicability to the soap:body.

Jacek: Minor amendment to the the you supplied below. If we are being very
clear, I would suggest accounting for the "although the namespace attribute
only applies to content not explicitly defined by the abstract types" text in
the encoded case..

Or we could leave at the level Gudge proposed (reproduced below) but say 'if
use=literal and style=document" only namespace attribute has no applicability
to the soap:body'

 Gudge>We might want to clarify that if use='literal' then the namespace
attribute on soap:body
 Gudge> is not applicable.

Regards, Prasad

Jacek Kopecky wrote:

>  Gudge,
>  when use='encoded', the namespace attribute is a parameter to
> the encoding used (indicated by encodingStyle). When style='rpc',
> the namespace attribute is the namespace of the rpc wrapper
> element.
>  Therefore the namespace attribute is significant when
> use='encoded' OR style='rpc'. It's only insignificant when
> both use='literal' AND style='document'.
>  So the clarification sought could be:
>
>  The use='literal' means the elements in schema will be in the
> target namespace of that schema; use='encoded' means the encoding
> governs the namespace, usually taking the value of the namespace
> attribute.
>  Analogically, style='document' means the elements in Body will
> be in the target namespace of the appropriate schema; style='rpc'
> means the (wrapper) element in Body will be in the namespace
> indicated by the namespace attribute.
>
>                    Jacek Kopecky
>
>                    Senior Architect, Systinet Corporation
>                   http://www.systinet.com/
>
> On Tue, 25 Jun 2002, Martin Gudgin wrote:
>
>  >
>  > I took an AI at the last telcon to write up Issue 4. Here is that write
>  > up.
>  >
>  > The issue is about interaction between the namespace attribute on
>  > soap:body and the targetNamespace of global element declarations in a
>  > schema.
>  >
>  > The namespace attribute on the soap:body binding extension element is
>  > only applicable when use='encoded' where it defines the namespace
>  > qualification of the 'wrapper' element for the RPC parameters. The local
>  > name of the wrapper element is defined by the name property of the input
>  > / output pieces of a portType operation. When use='encoded' the parts
>  > attribute of soap:body refers to parts defined using type='' rather than
>  > element=''. Therefore the interaction does not exist.
>  >
>  > Spo I'm not sure there is much of an issue here. We might want to
>  > clarify that if use='literal' then the namespace attribute on soap:body
>  > is not applicable.
>  >
>  > Gudge
>  >
Received on Thursday, 4 July 2002 21:11:25 GMT

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