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

• From: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
• Date: Thu, 20 Jul 2006 09:39:16 -0700
• To: Arthur Ryman <ryman@ca.ibm.com>
• Cc: www-ws-desc@w3.org
• Message-id: <44BFB1B4.4080306@sun.com>

During today's concall, I proposed a small amendment to Arthur's text:

Arthur Ryman wrote:
> 
> 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

   and any further processing, as mandated by the extension
   specification, that depends on such references having been resolved
   to the actual components

> . 
> 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.

Thanks,
Roberto

Received on Thursday, 20 July 2006 16:39:31 UTC