[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [uddi-spec] Initial draft of schemas and WSDL for 3.0.2
Hi John, Thanks for doing all the schema and WSDL work. I checked the files w.r.t. the listed change requests and found the following issues: 1) CR-054 Not addressed (changeRecordConditionFailed not added to replication schema). 2) CR-064 Not addressed (empty string defaults for keyName, sortCode and useType). Also, the change request itself does not capture the usage of the useType simple type in contact, discoveryURL, email, overviewURL, and phone elements and needs to be updated accordingly. 3) CR-046 Provided that you open up CR-046 again due to the change that needs to be made to section 188.8.131.52, it would also be good to document yet another change that is so far not captured: The tenth paragraph of section 5.4.3 needs to be changed from "Following the issue of the dispositionReport by N1 to the transfer_custody call, ..." to "Following the issue of the empty message by N1 to the transfer_custody call, ..." Claus -----Ursprüngliche Nachricht----- Von: John Colgrave [mailto:email@example.com] Gesendet: Montag, 19. Juli 2004 17:01 An: firstname.lastname@example.org Betreff: [uddi-spec] Initial draft of schemas and WSDL for 3.0.2 I have uploaded my first draft of schemas and WSDL for 3.0.2. I have uploaded only those files that have been changed, namely: uddi_v3.xsd uddi_v3custody.xsd uddi_v3replication.xsd uddi_api_v3_portType.wsdl uddi_custody_v3_binding.wsdl uddi_custody_v3_portType.wsdl uddi_repl_v3_binding.wsdl uddi_repl_v3_portType.wsdl uddi_sub_v3_portType.wsdl These changes were due to the following Change Requests: 46 51 54 56 59 63 64 If you are responsible for one of these Change Requests, please check the changes I have made. If you think there should be other Change Requests that should be included, please speak up. In the process of doing this I came across one other spec. change that needs to be added to my CR, CR-046: a change needs to be made to section 184.108.40.206 of the spec. XML Spy is having a hard time with the default attribute that was added in several places by one of the CRs, but I am not sure yet whether that is a bug in XML Spy. It claims that an empty default value can only be used with a small number of built-in types. John Colgrave IBM To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php.