While creating some tests for assertions I've come
across some assertions that I think specify the same requirement. I'll point
these out here and suggest that a single assertion be defined for each
restriction as multiple assertions may lead to problems interpreting the spec
and will lead to ambiguity wrt the assertion that should be flagged as an error
for a WSDL document that does not comply with the spec.
However, any WSDL 2.0 document that contains component definitions that refer
by QName to WSDL 2.0 components that belong to a different namespace MUST
contain a wsdl:importelement information item for that
namespace (see 4.2 Importing Descriptions ).
As with XML schema, any WSDL 2.0 document that references a foreign component
MUST have a wsdl:importelement information item for the
associated foreign namespace (but which does not necessarily provide a locationattribute
information item that identifies the WSDL 2.0 document in which the
referenced component is defined).
The Working Group tracked this comment as CR100 .
The Working Group removed the assertion markup for Import-0001, see .
A WSDL 2.0 document MUST NOT refer to XML Schema components in a given
namespace unless an xs:import or xs:schemaelement
information item for that namespace is present or the namespace is
the XML Schema namespace, http://www.w3.org/2001/XMLSchema, which contains
built-in types as defined in XML Schema Part 2: Datatypes Second Edition [XML Schema: Datatypes].
When resolving QNames references for schema definitions, the namespace MUST be
imported by the referring WSDL 2.0 document.
The Working Group tracked this comment as CR103 .
The Working Group removed the assertion markup from Types-1300001 and reworded
it into a note, added a reference to Schema-0016 (currently broken, but Arthur
has been notified), and additionally moved the last sentence of 126.96.36.199 to
3.1.2, see [9, 10].