- From: <sggraham@us.ibm.com>
- Date: Tue, 25 Jun 2002 11:36:54 -0400
- To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
- Cc: "Martin Gudgin" <mgudgin@microsoft.com>, www-ws-desc@w3.org, www-ws-desc-request@w3.org
- Message-ID: <OFC1919946.67B0635F-ON85256BE3.0055C590@us.ibm.com>
+1
++++++++
Steve Graham
sggraham@us.ibm.com
(919)254-0615 (T/L 444)
Emerging Technologies
++++++++
"Sanjiva
Weerawarana" To: "Martin Gudgin" <mgudgin@microsoft.com>, <www-ws-desc@w3.org>
<sanjiva@watson. cc:
ibm.com> Subject: Re: Target namespace in WSDL
Sent by: www-ws-
desc-request@w3.
org
06/25/2002 11:28
AM
I had already inserted an issue to address this in the version of
the doc published last week:
<issue id="issue-require-targetnamespace">
<head>Require targetNamespace attribute?</head>
WSDL 1.1 indicates that the targetNamespace attribute is
optional. I would like to make it required as otherwise
the NCNames used in other places don't make much sense.
<source>Sanjiva Weerwarana</source>
</issue>
Can we get a quick consensus on requiring this? It seems the
only sensible thing to do ...
Sanjiva.
----- Original Message -----
From: "Martin Gudgin" <mgudgin@microsoft.com>
To: <www-ws-desc@w3.org>
Sent: Tuesday, June 25, 2002 4:08 PM
Subject: Target namespace in WSDL
>
> Both WSDL and XML Schema have the notion of a target namespace. In XML
> Schema this property can be absent, denoting constructs that are not
> affiliated with a particular namespace. This was necessary because XML
> Schema describes XML instances, and elements in an XML instance may be
> unqualified ( not affiliated with a namespace ).
>
> The question I would like to pose is 'Does it makes sense to allow the
> target namespace property of WSDL components to be absent?'. And I will
> argue that it does not. WSDL does not describe XML instances, it
> describes messages, portTypes, bindings and services. I think it makes
> sense to mandate that these contructs always be affiliated with a
> namespace.
>
> To this end, I propose that we mandate the 'targetNamespace' AII on the
> definitions EII. And that we modify the spec to say that the value of
> the AII must be a non-zero length URI.
>
> Changes to spec
>
> Section 3.1
>
> Add a bullet between current bullets 2 and 3;
>
> * A target namespace attribute information item amongst its [attributes]
> as described below
>
>
> Section 3.1.1
>
> Add a third bullet
>
> * A type of anyURI in the http://www.w3.org/2001/XMLSchema namespace
>
> Add prose
>
> The value of the targetNamespace attribute information item MUST NOT be
> the empty string.
>
>
>
> Gudge
Attachments
- image/gif attachment: graycol.gif
- image/gif attachment: ecblank.gif
Received on Tuesday, 25 June 2002 11:37:14 UTC