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

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

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Thu, 27 Jun 2002 08:17:11 -0700
Message-ID: <3D1B2C77.F6556613@webmethods.com>
To: www-ws-desc@w3.org

The spec says the "namespace" AII is associated with "operation name"
which is the top-level wrapper in the body. Text from the spec:

"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."

Regards, Prasad

-------- Original Message --------
Subject: Issue 4: Use of namespace attribute on soap:body
Resent-Date: Tue, 25 Jun 2002 08:42:18 -0400 (EDT)
Resent-From: www-ws-desc@w3.org
Date: Tue, 25 Jun 2002 05:41:42 -0700
From: "Martin Gudgin" <mgudgin@microsoft.com>
To: <www-ws-desc@w3.org>

I took an AI at the last telcon to write up Issue 4. Here is that write

The issue is about interaction between the namespace attribute on
soap:body and the targetNamespace of global element declarations in a

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.

Received on Thursday, 27 June 2002 11:16:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:24 UTC