J3/01-199 Date: 13 May 2001 To: J3 From: Jeanne Martin Subject: Proposed Work Plan for Meeting 157 There are 5 meetings before F2000 is to be submitted to WG5 in June of 2002. Note that there is only 1 meeting left to complete F95 interpretations that contain edits. Congratulations on the good work at meeting 156. Both DATA and INTEROP polished off all their crucial issues, but DATA managed to get a bunch of new ones generated. New issues have numbers greater than or equal to 314. There are 31 outstanding unresolved issues (down 22 from last meeting even with 19 new ones added). They have been categorized into 2 levels for each of the 3 subgroups and the exception TR development body. The levels are 1) crucial and 2) can be deferred to integration, if necessary. The numbers for each group are: crucial deferrable JOR 4 8 DATA 10 (all new) 5 INTEROP 0 2 Except. TR 1 1 [See below for actual issue numbers.] To meet the deadline, J3 must complete at least the following assignments for the next meeting or inform WG5 that the date has slipped: Meeting 157 Resolve issues arising from the previous meeting, any remaining crucial unresolved issues and as many of the deferred issues as time allows. Also during the meeting, J3 will be processing interpretations, concentrating on those that contain edits (somewhat unpredictable at the outset). The Interp Subgroup can suggest a categorization of the interps into those that are crucial and those that can be deferred. Any committee member submitting a new interp must include at least one possible answer. After meeting 157 (and the 2001 WG5 meeting), the committee is reconstituted for integration. There will be 3 subgroups (This seems to be the optimum number given the committee size and fluctuating attendance.) For identification, call the new subgroups A, B, and C. The document will be divided into 3 Parts (based loosely on number of pages): Part 1: Introduction through Section 7 Part 2: Sections 8 through 12 Part 3: Section 13 through Appendix C Each SG should attempt to resolve any remaining issues in its assigned section and resolve any inconsistencies, ambiguities, etc. with other parts of the document. The assignments are: Meeting 158 Meeting 159 Meeting 160 SG A Part 1 SG A Part 2 SG A Part 3 SG B Part 2 SG B Part 3 SG B Part 1 SG C Part 3 SG C Part 1 SG C Part 2 Meeting 161 Any remaining issues are resolved. Everyone proofreads the entire document. ----- Criteria for selecting which of the unresolved issues are most crucial for early resolution were: 1) The serious ones that arose from papers at the last meeting, because the issues should still be fresh in people's minds. 2) Those that only the originating SG has the expertise to handle. 3) Those that need to be resolved in order to straighten out the terminology, so that nongroup members can help deal with interactions. 4) Topics that give rise to related issues that need to be dealt with concurrently. DATA: Issues 320, 321, 322, and 330 seem to be interrelated. The following are listed in document order per SG. Page numbers are from 01-007R1. Issue Page Issue Page JOR Crucial Deferrable 127 170 295 192 314 196 124 208 308 204 237 226 128 221 326 286 319 341 316 347 311 409 325 414 DATA Crucial Deferrable 328 49 318 17 329 55 323 19 320 66 262 277 321 86 315 341 317 136 324 402 332 156 330 252 322 254 331 255 327 321 INTEROP Crucial Deferrable 241 178 246 388 Except. TR Crucial Deferrable 213 376 171 397 Perhaps INTEROP, as a reward for handling most of their issues, could take on the 2 Except. TR issues and work on INTERPs.