In fulfilment of my action item, I reviewed the spec again [1]. The only problem I see is the row for Type Definitions: Type Definition types QName n/a n/a wsdl11.types(types) I think there is confusion here between the wsdl:types element and xs:complexType or xs:simpleType elements. There is no need to identify the wsdl:types element as a whole, although they are free to do so. The intension of that row should have been to identify XSD types defined within the wsdl:types element. These Type Definition elements are useful because they are used in wsdl:message parts. The fix is: Column 1: type QName Column Pointer Part: wsdl11.typeDefinition(type) Example 3.4 should be modified to include the wsdl11.typeDefinition identifiers. [1] http://www.w3.org/TR/wsdl11elementidentifiers/ 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.caReceived on Thursday, 1 February 2007 16:51:42 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:07:05 UTC