CR022a: Restriction on How Extensions interact with <import> and <include>

I am splitting CR022 into two separate issues: a) extension behavior wrt 
to <import> and <include>, and b) testing for component equivalent.

This note covers a).


I propose the following addition to Part 1.

4.3 Extensions

The semantics of an extension MUST NOT depend on how components are 
brought into a component model instance via <import> or <include>. That 
is, the components that are defined by a WSDL 2.0 document are determined 
by the contents of the document, except for the resolution of references 
to other components that may be defined in other documents. This 
restriction on the behavior of extensions permits WSDL 2.0 documents to be 
flexibly modularized and efficiently processed. In contrast, note that the 
so-called chameleon include mechanism of XML Schema violates this 
restriction since the namespace of the included XML Schema components is 
determined by the including XML Schema document.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca