Return-Path: 
 <axis-user-return-18149-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 6644 invoked from network); 2 Sep 2003 20:13:39 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 2 Sep 2003 20:13:39 -0000
Received: (qmail 52700 invoked by uid 500); 2 Sep 2003 20:11:41 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 52632 invoked by uid 500); 2 Sep 2003 20:11:40 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 52559 invoked from network); 2 Sep 2003 20:11:39 -0000
Message-Id: <5.2.1.1.0.20030902153509.02f43b70@localhost>
X-Sender: annethomas/pop.earthlink.net@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 02 Sep 2003 16:11:20 -0400
To: axis-user@ws.apache.org
From: Anne Thomas Manes <anne@manes.net>
Subject: Re: xmlns=" " in the doc\literal SOAP message
In-Reply-To: <0e5e01c37177$48d40fd0$ae00a8c0@jmg>
References: <3F2E62790250AF4485864348F7E9F6B0D77013@stingray.tnow.net>
 <5.2.1.1.0.20030902123722.00b2ca40@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Okay, Jeff -- you caught me. So let's clarify the question once and for all 
with a complete answer. Keep in mind that there are about 20 ways to 
describe our simple element foo, and I will not review all of them in this 
note.

Here's Krzysztof's original question:

Just for completeness, what schema would make the
following xml valid:

<tns:foo xmlns:tns="http://www.foo.com">
           <tns:bar>cory</tns:bar>
           <tns:baz>anne</tns:baz>
</tns:foo>

To clarify: how do you make bar and baz part of the http://www.bar.com 
namespace?

First some definitions:
Global element = an element definition that is a direct child of the 
<schema> element.
Local element = an element definition that is not a direct child of the 
<schema> element (e.g., it is a child/descendant of a <complexType> definition)

The elementFormDefault and attributeFormDefault attributes are specified on 
the <schema> element to indicate what the default behavior should be in 
regards to whether local element and attribute definitions should be 
included in the targetNamespace. elementFormDefault="unqualified" is the 
default value, and it indicates that local elements should not be included 
in the targetNamespace.
elementFormDefault="qualified" puts all local elements into the 
targetNamespace.

You can override the default behavior on an element-by-element basis using 
the form attribute.

So...

If you do not specify elementFormDefault="qualified", (in other words -- if 
you take the default value), then only global elements are part of the 
targetNamespace. In this situation, you would have to define bar and baz as 
global elements to make them part of the namespace. Such as something like 
this:

<schema targetName="http://www.foo.com"
         xmlns:tns="http://www.foo.com"/>
         <element name="foo">
             <complexType>
                   <sequence>
                           <element ref="tns:bar" />
                           <element ref="tns:baz" />
                   </sequence>
             <complexType>
        </element>
        <element name="bar" type="xsd:string"/>
        <element name="baz" type="xsd:string"/>
  </schema>

Alternatively, you can specify that all local elements should be part of 
the targetNamespace by specifying elementFormDefault="qualified". Such as:

<schema targetName="http://www.foo.com"
      elementFormDefault="qualified"/>
      <element name="foo">
         <complexType>
            <sequence>
              <element name=bar" type="xsd:string"/>
              <element name="baz" type="xsd:string" />
             </sequence>
          </complexType>
      </element>
</schema>

Or you can leave the default form as "unqualified" and override the default 
on each element. Such as:

<schema targetName="http://www.foo.com"/>
    <element name="foo">
      <complexType>
        <sequence>
          <element name=bar" type="xsd:string" form="qualified"/>
          <element name="baz" type="xsd:string" form="qualified"/>
         </sequence>
       </complexType>
    </element>
</schema>

(Don't you just love XML Schema?!?!)

Anne


At 10:26 AM 9/2/2003 -0700, you wrote:
>No, bar and baz need not be global elements (direct children of schema) in
>order to be in the target namespace of the schema, if their 'form' infoset
>property is "qualified".  This can be done overall for the schema, using
>elementFormDefault="qualified" or on individual element declarations.
>
>The root element of the document, foo, can only be in the target namespace
>if it is global.
>
>Jeff
>
>----- Original Message -----
>From: "Anne Thomas Manes" <anne@manes.net>
>To: <axis-user@ws.apache.org>
>Sent: Tuesday, September 02, 2003 9:50 AM
>Subject: RE: xmlns=" " in the doc\literal SOAP message
>
>
> > There are a number of ways to do it, but essentially, you have to define
> > each element as a direct child of the <schema> element. Here's one
>example:
> >
> > <schema targetName="http://www.foo.com"
> >          xmlns:tns="http://www.foo.com"/>
> >          <element name="foo">
> >              <complexType>
> >                    <sequence>
> >                            <element ref="tns:bar" />
> >                            <element ref="tns:baz" />
> >                    </sequence>
> >              <complexType>
> >         </element>
> >         <element name="bar" type="xsd:string"/>
> >         <element name="baz" type="xsd:string"/>
> >   </schema>
> >