SC32/WG2 N0879 Proposal for WG2-level formal resolution using Bugzilla Japan National body ISO/IEC JTC1 SC32 WG2 Toronto Meeting 2005/09/26-30

SC32/WG2 N , 30 2 Proposal-abstract Japan proposes that WG2-level formal resolutions can be made using Bugzilla if all the P-members are formally noticed that the resolution will be made on Bugzila and if all the P-members are given a proper time to consider the proposed resolution. For more detail, see slide 5 and 6.

SC32/WG2 N , 30 3 Rationale JTC1 Directives, 5th edition says 7 Meetings 7.1 General JTC 1 and its subsidiary bodies should work as much as possible by correspondence. … The Convener shall convene meetings of the WG if questions cannot be solved by correspondence… Use of Electronic Messaging JTC 1, recognising the requirement that committees work as much as possible by correspondence, endorses the use of electronic messaging as a very useful tool in international communication and encourages broader use of electronic messaging within its committees. That is, the normal procedure to solve questions is by correspondence, including electronic message. The face-to-face meeting is convened by the convener only if questions cannot be solved by correspondence, including electronic messages.

SC32/WG2 N , 30 4 Background We live in the era of dog-year. If we cannot produce the standards in response to the request of the time, we will lose the power. For this purpose, only the discussions during the face-to- face meeting are not enough. Even if we reach the consensus using Bugzilla, if we have to wait for the next face-to-face meeting for the WG2-level formal resolutions, we cannot conduct our jobs as efficiently as the time requires.

SC32/WG2 N , 30 5 Proposal-details 1 Any P-members, Convener and Project editors can put a proposed resolution on Bugzila. Proposed resolution at least has to include; Resolution proposed  The proposed resolution should be made after the substantial discussions are made, using Bugzilla or face-to-face. How this proposed resolution is adopted.  Since WG-level work is done consensus-base (i.e. the substantial support of the P-memmbers), basically it should be as follows; –The proposed resolution will be adopted if no objection is made by any P-members by the end of yymmdd (the closing date specified).  At least five working days (including the day the proposed resolution is put on the Bugzilla and the closing date) have to be given.  Time and date are based on GMT.

SC32/WG2 N , 30 6 Proposal-details 2 Then, Bugzila should automatically send the notification to all the P-members, Convener and Project editors. Bugzilla may need some additional settings for the proper notifications. Currently, sc32wg2-news may not cover all the P-members. Each P-member has to respond it by the closing date specified if it has any objections. It is each P-member’s responsibility to decide who is actually responsible for it in SC32WG2.

SC32/WG2 N , 30 7 Resolution which should not be made on Bugzilla (1 of 2) The following resolutions should not be made on Bugzilla but should be made at the WG2 meeting prior to SC32 meeting because they need to be adopted by SC32. Section 1 - Programme of Work Resolutions Resolution WG 02 / 1: SC 32/WG 02 Programme of Work and Project Editor Assignments SC 32/WG 02 approves the Programme of Work, Target Dates and Project Editor Assignments contained in … Resolution WG 02 / 2: SC 32/WG 02 Project Subdivisions SC 32/WG 02 approves the following subdivisions and minor enhancements to existing work: SC 32/WG 2 instructs its Convener to forward these subdivisions to SC 32 for endorsement. Resolution WG 02 / 3: SC 32/WG 02 Project Withdrawals SC 32/WG 02 approves the following withdrawals from existing work: SC 32/WG 02 instructs its Convener to forward these withdrawals to SC 32 for endorsement. Resolution WG 02 / 4: Standards Due for Periodic Review SC 32/WG 02 approves the following: SC 32/WG 02 instructs its Convener to inform SC 32 of the above recommendations. Resolution WG 02 / 5: New Projects SC 32/WG 02 approves the following: Upon receipt of texts, SC 32 WG 02 recommends that SC 32 submit to JTC 1 the referenced Proposals for New Work Items: Resolution WG 02 / 6: Study Period SC 32 WG 02 recommends that SC 32 submit to JTC 1 the following Proposals for Study Period:

SC32/WG2 N , 30 8 Resolution which should not be made on Bugzilla (2 of 2) (Continued from the previous slide) Section 2 - Project Document Resolutions Resolution WG 02 / 7:Committee Draft (CD) Ballots (CD, PDAM, PDISP, PDTR) Upon receipt of texts, SC 32/WG 02 requests its SC 32 Secretariat to register as CDs, PDAMs, PDISPs, PDTRs and issue letter ballots on the following projects: Resolution WG 02 / 8:Final Committee Draft (FCD) Ballots (FCD, FPDAM, FPDISP, FPDTR, DCOR) Upon receipt of texts, SC 32/WG 02 requests its SC 32 Secretariat to register as FCDs, FPDAMs, PDTRs, FPDISPs, DCORs and issue letter ballots on the following projects: Resolution WG 02 / 9:Final Draft International Standard (FDIS) Ballots (FDIS, FDAM, DTR) Upon receipt of texts, SC 32/WG 02 requests its SC 32 Secretariat to register as FDISs, FDAMs, DTRs and submit to ITTF for the following projects:

SC32/WG2 N , 30 9 Questions (1 of 3) Other than above, in what cases are WG2-level formal resolutions (including on Bugzilla) necessary? Case1 To request to register a WD to SC32 secretariat.  Maybe no, this is a project editor’s decision. Case2 To request to register a CD after WG 02 / 7 type resolution is already made.  Maybe no. This is a project editor’s decision. Note: JTC1 Directives  The WD remains in Stage 2 until all of the following three conditions are met: … the SC has decided in a resolution during a meeting or by letter ballot that the WD be forwarded to the ITTF for registration as a CD.  Optionally, an SC may authorise a WG to decide that a WD should be forwarded, via the SC Secretariat, for registration as a CD.

SC32/WG2 N , Questions (2 of 3) (continued from the previous slide) Case3 To make a CD progress to a FCD after WG 02 / 8 type resolution is already made.  If no, this is a project editor’s decision. Note: JTC1 Directives  The project editor, after consultation with the SC secretariat and, if necessary, the SC chairman, shall indicate if it is the case that the proposed CD is intended to be the final CD (FCD) on this subject.  Consideration of successive CDs shall continue until the substantial support of the P-members of the committee has been obtained for an FCD or a decision to abandon or defer the project has been reached.  It is the responsibility of the SC Secretariat, if necessary in consultation with the ITTF, to judge when substantial support has been obtained…

SC32/WG2 N , Questions (3 of 3) (continued from the previous slide) Case4 To advance a FCD to a FDIS after WG 02 / 9 type resolution is already made.  If no, this is a project editor’s decision. Note: JTC1 Directives  An FCD shall be advanced to FDIS only if the text has been stabilised, consensus has been demonstrated, and the substantial support of the P-members of the SC has been obtained…. Case5 Approval of the comments disposition on a CD or FCD ballot. Case6 Others. For example, a resolution on a miscellaneous issue discussed on Bugzilla.