[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - uddi-spec-tc-tn-wsdl-v2.zip uploaded
The document revision uddi-spec-tc-tn-wsdl-v2.zip has been submitted by Luc Clement (email@example.com) to the OASIS UDDI Specification TC document repository. This document is revision #2 of uddi-spec-tc-tn-wsdl-v2.zip. Document Description: We decided at the FTF to generatlise the WSDL portType Reference tModel to allow for its reuse by the BPEL mapping TN. The 20040601 version last posted was updated accordingly; a number of v3 entity keys were also case-folded. Please find attached MSWord, PDF (final/markup) and HTML versions of the TN. I am proposing that we vote the errata #2 for approval at our 20 July telecon. ----- from 20040601 ------ John, Tony and I have completed the second errata of the "Using WSDL in a UDDI Registry, Version 2.0.2" Technical Note. The changes made include: * Changes to tModel content to make them consistent. * Removal of section 2.5.2 (of the 20031104 version) describing an optional v3 mapping. * Removal of Footnote 1 (of the 20031104 version). * Clarified that a keyedReference to the XML Namespace category system MUST only be made if the definitions element has a target namespace, otherwise if there is no target namespace, the reference MUST NOT be made. See sections 2.4.1, 2.4.2 and 2.4.3. Please find attached the following documents for review: a. MS Word - final b. PDF versions - final and markup c. HTML versions Please review and provide comment so we may close on this errata at the June FTF. Thanks, John, Tony, Luc Download Document: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7565/uddi-spec-tc-tn-wsdl-v2.zip View Document Details: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/document.php?document_id=7565 Revision: This document is revision #2 of uddi-spec-tc-tn-wsdl-v2.zip. The document details page referenced above will show the complete revision history PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.