RE: Description's {type definitions} mapping

Thanks for your comment.  The WS Description Working Group tracked this
as a Last Call comment LC307 [1].  The Working Group closed this issue
with no action in response to your mail at [2].

We will use [2] as evidence that we've satisfied your concern.

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC307
[2]
http://lists.w3.org/Archives/Public/public-ws-desc-comments/2005Aug/0012
.html

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Hugo Haas
> Sent: Tuesday, August 23, 2005 4:26 AM
> To: public-ws-desc-comments@w3.org
> Subject: Description's {type definitions} mapping
> 
> In Part 1, section 2.1.3 Mapping Description's XML Representation to
> Component Properties reads:
> 
>   {type definitions}
> 
>   The set of Type Definition components corresponding to all the type
>   definitions defined as descendants of the types element information
>   item, if any, plus any (via xs:include) or imported (via xs:import)
>   Type Definition components. At a minimum this will include all the
>   global type definitions defined by XML Schema simpleType and
>   complexType element information items. It MAY also include any
>   definitions from some other type system which describes the
>   [attributes] and [children] properties of an element information
>   item. It is an error if there are multiple type definitions for each
>   QName.
> 
> Why are simpleType and complexType called out here, and not element
> for example?
> 
> I propose simplifying the second sentence:
> 
>   At a minimum this will include all the global definitions defined by
>   XML Schema declarations.
> 
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Thursday, 15 September 2005 19:02:13 UTC