W3C home > Mailing lists > Public > www-ws@w3.org > February 2004

WSDL definitions / targetNamespace

From: Rob Henley <rob.henley@freeuk.com>
Date: Sun, 8 Feb 2004 17:21:44 -0000
Message-ID: <002601c3ee68$077bf700$ec356a20@99VXT21>
To: <www-ws@w3.org>
Can anyone help me understand the use of the (optional) targetNamespace on the WSDL 1.1 defintions tag?

The value can clearly be different from any targetNamespace(s) on schema elements in the types section., but is often the same in simple examples.

One use for the targetNamespace at the defintions level seems to be to restrict imports of other WSDL files (they must all have the same targetNamespace). Other issues which occur to me are:

- if I'm using rpc style then the outer level tag of a SOAP request is derived from the WSDL operation name (i.e. it isn't defined in Schema). Do these outer tags in the SOAP instance document belong to the namespace defined at the WSDL defintions level? (With their child elements potentially belonging to other namespaces as specified on WSDL schema elements?)

- if there is no targetNamespace attribute on a WSDL schema element, does it default to the target namespace of the defintions element?

- if there is no targetNamespace on the WSDL defintions element?

Many thanks!
Rob
Received on Monday, 9 February 2004 03:36:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:45 GMT