W3C home > Mailing lists > Public > www-ws-desc@w3.org > September 2005

Resolution of LC 343 incoporated (was RE: Comments on Web Services Description Language (WSDL) Version 2.0 Part 0: Primer )

From: Liu, Kevin <kevin.liu@sap.com>
Date: Thu, 29 Sep 2005 22:32:22 -0700
Message-ID: <3470F33FF8ED12498D07F3A9651AA18E5B59A4@uspale20.pal.sap.corp>
To: <paul.downey@bt.com>, <dms@sosnoski.com>, <www-ws-desc@w3.org>

I have rewritten the section to make it more readable. Please check out
the new version at
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-primer.ht
ml#more-types

Hopefully the new version is less confusing. Let me know if you still
see room for improvement.

Best Regards,
Kevin
  

> > -----Original Message-----
> > From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org]On
> > Behalf Of Dennis Sosnoski
> > Sent: 20 September 2005 07:08
> > To: www-ws-desc@w3.org
> > Subject: Comments on Web Services Description Language 
> (WSDL) Version
> > 2.0 Part 0: Primer
> > 
> > 
> > 
> > I'm puzzled at the use of a special mechanism for importing 
> > XML schemas, 
> > as discussed in 2.3.2. AFAIKS, the same effect can be had by 
> > just using 
> > a simple xs:schema wrapper element:
> > 
> >   <xs:schema>
> >     <xs:import .../>
> >   </xs:schema>
> > 
> > This is a cleaner approach than just in-lining the xs:import and 
> > xs:include, since it minimizes the number of different ways 
> > of doing the 
> > same thing. From the comment at the end of 2.3.1, it seems 
> > that there's 
> > a misunderstanding of how schema operates here. As I understand it, 
> > imported schema definitions become part of the schema and 
> > have the same 
> > visibility as definitions made directly under the including 
> > schema. In 
> > support of this interpretation, section 4.2.3 of Schema Part 1 
> > (http://www.w3.org/TR/xmlschema-1/#composition-schemaImport) 
> > ends with:
> > 
> > The *schema components* 
> > <http://www.w3.org/TR/xmlschema-1/#key-component> (that is {type 
> > definitions} <http://www.w3.org/TR/xmlschema-1/#type_definitions>, 
> > {attribute declarations} 
> > <http://www.w3.org/TR/xmlschema-1/#attribute_declarations>, 
> {element 
> > declarations} 
> > <http://www.w3.org/TR/xmlschema-1/#element_declarations>, 
> > {attribute group definitions} 
> > <http://www.w3.org/TR/xmlschema-1/#attribute_group_definitions
> > >, {model 
> > group definitions} 
> > <http://www.w3.org/TR/xmlschema-1/#model_group_definitions>, 
> > {notation 
> > declarations} 
> <http://www.w3.org/TR/xmlschema-1/#notation_declarations>) 
> of a schema corresponding to a <schema> 
> <http://www.w3.org/TR/xmlschema-1/#element-schema> element 
> information 
> item with one or more <import> 
> <http://www.w3.org/TR/xmlschema-1/#element-import> element 
> information 
> items must include not only definitions or declarations 
> corresponding to 
> the appropriate members of its [children] 
> <http://www.w3.org/TR/xml-infoset/#infoitem.element>, but 
> also, for each 
> of those <import> <http://www.w3.org/TR/xmlschema-1/#element-import> 
> element information items for which clause 2 
> <http://www.w3.org/TR/xmlschema-1/#c-ims> above is satisfied, 
> a set of 
> *schema components* <http://www.w3.org/TR/xmlschema-1/#key-component> 
> identical to all the *schema components* 
> <http://www.w3.org/TR/xmlschema-1/#key-component> of *I*.
> 
> Given this, I don't see any possible reason why xs:imported 
> components 
> of a schema would not be available for reference by QName in the WSDL.
> 
>   - Dennis
> 
> 
Received on Friday, 30 September 2005 05:32:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:37 GMT