- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Tue, 23 Aug 2005 16:24:31 -0400
- To: Hugo Haas <hugo@w3.org>
- Cc: public-ws-desc-comments@w3.org, public-ws-desc-comments-request@w3.org
- Message-ID: <OF7678C1BF.F2FF73EC-ON85257066.00700F8A-85257066.00701A73@ca.ibm.com>
Hugo, Elements go into the {element declarations} property. 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 Hugo Haas <hugo@w3.org> Sent by: public-ws-desc-comments-request@w3.org 08/23/2005 07:25 AM To public-ws-desc-comments@w3.org cc 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/
Attachments
- application/octet-stream attachment: signature.asc
Received on Tuesday, 23 August 2005 20:24:42 UTC