W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > October 2005

RE: Comments on Web Services Description Language (WSDL) Version 2.0 Part 0: Primer

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 5 Oct 2005 14:27:41 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E849E23E@RED-MSG-10.redmond.corp.microsoft.com>
To: "Dennis Sosnoski" <dms@sosnoski.com>
Cc: <public-ws-desc-comments@w3.org>

Thanks for your comment.  The WS Description Working Group tracked this
as a Last Call comment LC343 [1].  To clarify this area, the Working
Group agreed to add a note at the bottom of table.  This note will point
out that WSDL 2.0 is different that common 1.1 usage patterns, and we'll
add an example of how NOT to do it within WSDL 2.0 as well to drive the
point home.

If we don't hear otherwise within two weeks, we will assume this
satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC343

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
> On Behalf Of Dennis Sosnoski
> Sent: Monday, September 19, 2005 11:08 PM
> 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 Wednesday, 5 October 2005 21:28:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:32 GMT