WSDL 2.0 Core, section 2.3.3, "xs:include"

I believe that the table (2-1) and column "meaning" may be incomplete as to xs:include, or it imposes a restriction on XML Schema within WSDL that is not constrained by XML Schema alone.

The current text in this table for xs:include notes:

"Merge XML Schema components from another XML Schema document that has the SAME targetNamespace."

This text implies/states that an xs:include(d) schema MUST have a targetNamespace, which is not true.

The notion of a "chameleon" schema is one that implements an xs:include from a parent schema (often a proxy or umbrella schema). The xs:include(d) schema in this example is not required to have a targetNamespace. That is, the xs:include(d) namespace might not have any namespace at all, or it can have the same targetNamespace.

The parent or xs:include(ing) schema would then act as a proxy to apply its namespace to all xs:include(d) and referenced declarations (assuming it has a targetNamespace, which is also not required).

If the xs:include(d) schema does not have a targetNamespace declared, it is then coerced into the namespace of the xs:include(ing) parent schema (again, if that parent schema has a targetNamespace). In this case and by virtue of having no targetNamespace, the xs:include(d) schema does NOT have the same namespace as the xs:include(ing) schema. This condition would appear to violate the text in table 2-1.

If the xs:include(d) schema does have a targetNamespace declared, it then MUST be the same as the xs:include(ing) parent schema (this condition is satisfied by the text in table 2-1).

Was the intent of the working group such that the current application of targetNamespace and xs:include as allowed by XML Schema is not allowed when implemented via a WSDL <types/> reference ?

J. Bean
P.O. Box 30171
Phoenix, AZ  85046-0171

RDBMS@aol.com
XML-Guy@hotmail.com