[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uddi-spec] The v3.0.1 Specification has been posted for 30-day review
Tony, These are good catches - I agree with all of them except the one for the section 3.3.2.12 diagram. These diagrams do not imply order. I think that we should instead update sections 1.3.2.1 and 1.3.2.2 to indicate that order is not implied in the diagram structure. We're covered for the entire document then. Thanks, Tom Bellwood Phone: (512) 838-9957 (external); TL: 678/9957 (internal) Co-Chair, OASIS UDDI Specification TC STSM - Emerging Technologies IBM Corporation "Rogers, Tony" <Tony.Rogers@ca.com> on 08/12/2003 04:07:39 AM To: "Luc Clement" <lclement@windows.microsoft.com>, <uddi-spec@lists.oasis-open.org> cc: Subject: RE: [uddi-spec] The v3.0.1 Specification has been posted for 30-day review Some very small comments - all probably qualify as typos: section 1.4 specifies UDDI.org in both 1.4.1 and 1.4.2 - should that now be OASIS? Or our tech committee? section 1.7 para 2 line 2 has "principle" where it should have "principal". section 3.3.2.8 - should that be "contains a part of the actual address in text form" rather than "contains the actual address in text form"? The current text suggests that the entire address is contained within the addressline. section 3.3.2.12 - does this diagram mean to require that all keyed reference groups be placed after all keyed references? I thought there was no constraint on the order of these. section 4.4.2 - second last example is incorrect - it says "uddi:tempuri.com:keygenerator" is a legal derivedkey with a KSS of "keygenerator", but the text has explicitly forbidden KSS to be "keygenerator", so this is not a legal derivedkey. It IS a legal keygeneratorkey, though, isn't it? I suggest this be moved to the end of the examples, and labelled as a legal keygeneratorkey. Tony Rogers tony.rogers@ca.com -----Original Message----- From: Luc Clement [mailto:lclement@windows.microsoft.com] Sent: Tue 12/08/2003 6:01 To: uddi-spec@lists.oasis-open.org Cc: Subject: [uddi-spec] The v3.0.1 Specification has been posted for 30-day review The v3.0.1 specification has been posted at the locationsprovided below. In accordance with Section 1.6 Specification Change Request and Errata Process ( http://www.oasis-open.org/committees/uddi-spec/doc/process/uddi-spec-tc-process-20021212.htm#_Toc27444262 ), this version of the spec is being submitted for a 30 day review period, during which time no changes should be made to either the errata or the marked up document. Any revision necessary as a result of feedback should be made and resubmitted for review; an additional 15 day review period should be allowed but may be waived depending on the nature of the changes. At the end of the review period, the TC Chairs will submit the errata and amended specification document (and schema and WSDL files) for vote as a Committee Specification. Voting rules for this vote are the same as for approval of a TC Committee Specification, as documented in the OASIS TC Process. HTML versions at: http://uddi.org/drafts/pubs/uddi_v3.htm http://uddi.org/drafts/pubs/uddi-v3.0.1-20030809.htm Marked-up MS Word version at http://uddi.org/drafts/pubs/uddi-v3.0.1-20030809-markup.doc (Note: please let me know if you would like a PDF version of the revisions) PDF version at http://uddi.org/drafts/pubs/uddi-v3.0.1-20030809.pdf Schema files at: http://uddi.org/drafts/schema/uddi_v3.xsd http://uddi.org/drafts/schema/uddi_v3custody.xsd http://uddi.org/drafts/schema/uddi_v3policy.xsd http://uddi.org/drafts/schema/uddi_v3policy_instanceParms.xsd http://uddi.org/drafts/schema/uddi_v3replication.xsd http://uddi.org/drafts/schema/uddi_v3subscription.xsd http://uddi.org/drafts/schema/uddi_v3subscriptionListener.xsd http://uddi.org/drafts/schema/uddi_v3valueset.xsd http://uddi.org/drafts/schema/uddi_v3valuesetcaching.xsd WSDL files at: http://uddi.org/drafts/wsdl/uddi_api_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_api_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_custody_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_custody_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_repl_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_repl_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_subr_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_subr_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_sub_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_sub_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_vscache_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_vscache_v3_portType.wsdl http://uddi.org/drafts/wsdl/uddi_vs_v3_binding.wsdl http://uddi.org/drafts/wsdl/uddi_vs_v3_portType.wsdl Luc Clément Microsoft Co-chair, OASIS UDDI Spec TC
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]