For the record, the WG agreed [1] to make the namespaces consistent as you propose. We will assume you agree that we have addressed the issue appropriately unless we hear from you before Oct 13th. [1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC42 ________________________________ From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On Behalf Of Liu, Kevin Sent: Thursday, September 09, 2004 6:41 PM To: 'www-ws-desc@w3.org' Subject: error in part 2, section 3.1.4 The namespace value of "myDataType" is inconsistent in the example (see bold text). Proposal: change the second case to : xmlns:foo="http://example.com/ws/wsdl20/my-ws" <types> <schema targetNamespace="http://example.com/ws/wsdl20/my-ws" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ad="http://www.w3.org/2004/08/wsdl/feature/AD"> <!-- Define the data type we'll use later --> <complexType name="myDataType"> <sequence> <!-- These elements are our data --> <element name="isGoldClubMember" type="xs:boolean" ad:mustUnderstand="true" /> <element name="promotionalCode" type="xs:string" minOccurs="0"/> </sequence> </complexType> </schema> </types> <interface name="customerService"> <operation name="reserveCar"> <input element="myNS:reserveCarRequest"> <property uri="http://www.w3.org/2004/08/wsdl/feature/AD/data"> <constraint xmlns:foo="http://example.com/"> foo:myDataType </constraint> </property> </input> </operation> </interface> Best Regards, Kevin LiuReceived on Wednesday, 29 September 2004 20:01:43 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:00 UTC