RE: [uddi-spec] FW: Agenda for 9/13 OASIS UDDI Specification Technical Committee Meeting

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

Title: FW: Agenda for 9/13 OASIS UDDI Specification Technical Committee Meeting

Luc,

 

Thanks for the draft UDDI Spec TC Process.

Here are my initial comments and suggestions, all refering to the document's line numbers:

 

Typos

59 "identify refine and prioritize" should be "identify, refine, and prioritize"

101 "of one or more a Working Drafts" should be "of one or more Working Drafts"

 

Clarification

75 shouldn't "complete the Working Draft" be "complete a subcommittee Working Draft"?

85 shouldn't "basis of a TC Specification" be "basis of a TC Working Draft"?

128 shouldn't "The error process" be "The errata process"

163 This is the only time where the suggested uddi-spec Yahoo Group, proposed for our document management, is mentioned. There should be a more general note about this process in Chapter 3.

 

Suggestion

104 IMO, Candidate Drafts should be made public in order to get public feedback as early as possible.

114-123 IMO, we do not need a "Committee Draft Specification". Three steps (Working Draft, Candidate Draft and Committee Specification should be sufficient, since there is also the possible subsequent status of an OASIS specification (usual OASIS process).

134 Rather than talking about errors only, I suggest to state "When an error, inconsistency, or unintentional ambiguity is discovered".

138 Rather than having debates about individual errata items on two separate mailing lists, I suggest to use the uddi-spec mailing list only and to inform those who introduced the item on the uddi-spec-comment list about the TC's consensus later.

168 I am not sure if a 2/3 majority vote of the TC membership may be reasonable, but why is it more "difficult" to get a TC errata approved than the TC specification itself (a 2/3 vote of TC members, with no more than 1/4 objecting)?

172-175 I don't see a need for a separate process for "specification change requests". The errata process should cover all items, including those from the UDDI Operator's Council.

189 Rather than talking about "Vendor Publications" I suggest to name this kind of note "Usage Idea".

 

Talk to you on Friday.

 

Best regards,

 Claus

 

-----Original Message-----
From: Luc Clement [mailto:lclement@microsoft.com]
Sent: Donnerstag, 12. September 2002 05:33
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] FW: Agenda for 9/13 OASIS UDDI Specification Technical Committee Meeting

Dear members,

As proposed in the agenda, we will be introducing a draft of the "UDDI Spec TC Process" document. Section 1.3.2 refers.

1.3.2   UDDI Spec TC Documents

The DRAFT UDDI Spec TC Process document “uddi-spec-tc-process-20020903.doc” introduces a set of documents and rules related to managing specifications, TC technical notes and best practices. Also covered in this document is a proposed document management and collaboration process.

TC Chairs will present an initial version of this document and engage the TC in a discussion.

Please accept for your review "uddi-spec-tc-process-20020910.doc".

<<uddi-spec-tc-process-20020910.doc>>
 
Luc Clément
Microsoft
Co-chair, OASIS UDDI Spec TC

-----Original Message-----
From: Tom Bellwood [mailto:bellwood@us.ibm.com]
Sent: Monday, September 09, 2002 11:13
To: arun_candadai@yahoo.com; hbs@bea.com; mkomal@bea.com; william.cox@bea.com; zahid.ahmed@commerceone.com; Tony.Rogers@ca.com; ssarukkai@coxygen.com; archer@cp.net; mmartin@certivo.net; maud.cahuzac@rd.francetelecom.com; shishir.garg@rd.francetelecom.com; mwdn@fsw.fujitsu.com; kibakura@jp.fujitsu.com; bellwood@us.ibm.com; zagelow@us.ibm.com; hately@us.ibm.com; colgrave@hursley.ibm.com; mweiner@us.ibm.com; sanjay.patil@iona.com; pyounguk.cho@iona.com; joel.d.munter@intel.com; sandip.h.mandera@intel.com; sviens@inflexionpoint.com; alex@lisa.org; alison@smp-m.com; mike@lisa.org; arle@lisa.org; pmacias@lmi.org; Hedyalb@aol.com; Karsten Januszewski; Bob Atkinson; Chris Kurt; jpollock@modulant.com; mvoskob@msi.com.au; pfelsted@novell.com; a.shimaya@ntta.com; y.hashida@ntta.com; a.kawai@ntta.com; sam.lee@oracle.com; Alok.Z.Srivastava@oracle.com; matthew.dovey@las.ox.ac.uk; Andy.Sweet@perficient.com; claus.von.riegen@sap.com; ucorda@seebeyond.com; scott@storagepoint.net; trey.drake@sun.com; david.gadbois@sun.com; mark.wahl@sun.com; anne@manes.net; ianh@tibco.com; Philip.rossomando@unisys.com; jcha@vml.com; matt@xmlglobal.com; kirby@thecave.com

Cc: Luc Clement

Please find attached the agenda for our first OASIS UDDI Specification Technical Committee meeting.  You will note that several significant votes will be taken in order to establish the existing contributed specifications as OASIS Committee Specifications and as the basis for all our future work as we move forward from here on with UDDI.  Please plan to attend.

<<TCAgenda-V1.01-20020913.doc>>
(See attached file: TCAgenda-V1.01-20020913.doc)

Thanks,
Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
(internal)
Senior Technical Staff Member
Emerging Technologies
IBM Corporation