This BP 1.0 rule implies that there can be multiple <xsd:schema>
definitions within a <types> section:
5.2.2 Schema targetNamespace SyntaxRequiring a
targetNamespace on all xsd:schema elements that are children of
wsdl:types is a good practice, places a minimal burden on authors of WSDL
documents, and avoids the cases that are not as clearly defined as they
R2105 All xsd:schema elements contained in a
wsdl:types element of a DESCRIPTION MUST have a targetNamespace attribute
with a valid and non-null value, UNLESS the xsd:schema element has
xsd:import and/or xsd:annotation as its only child element(s).
At 11:18 AM 10/27/2003, Tom Jordahl wrote:
I don't know if BP 1.0 allows
If it does (or doesn't address this at all), we should make WSDL 2.0
that it is allowed.
If it does NOT, we need to think about this more, and perhaps follow
lead in this.
Macromedia Server Development
From: Sanjiva Weerawarana
Sent: Friday, October 24, 2003 8:27 AM
Subject: Re: Can one inline schema import definitions from a second
"Tom Jordahl" <firstname.lastname@example.org> writes:
> I think we should make sure that 2.0 is clear that multiple
> schema fragments are allowed and should be supported by
Does WS-I BP 1.0 allow *multiple* <xsd:schema> elements inside
<types>? If not let's restrict to a single.
+1 to your proposal in any case Tom.