| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Bob- On 510//11 9:03 AM, Grow, Bob wrote:
If amendments are balloted as redlines in a consolidated edition, there is no need for for any portion of the document that is outside the scope of the ballot to be in the balloting package. As a practical matter, I believe that would mean that the draft for ballot would only include the clauses that were being added or changed/augmented.I agree balloting as redlines also is often valuable. A speed increase or new PHY type for 802.3 is not likely to show as much benefit from a redline ballot as would energy efficient Ethernet which is much better reviewed in context (as you point out for much 802.1 work). In a very large document though, a complete redline is difficult to find scattered changes, so only supplying changed clauses or a changed clause list might be necessary for a redline ballot.
I agree that is a problem. Again seeking a practical solution, I believe the best way to handle this is one of the following: * For the case where each of the parallel projects is adding a clause or clauses each ballot draft would include: o Project A: the clauses being added for project A and all of the clauses from the common base which currently have redlines against them from open projects. o Project B: the clauses being added for project B and all of the clauses from the common base which currently have redlines against them from open projects. * For the case where one or more of the projects did not involve a new clause: o Project A: all of the clauses from the common base which currently have redlines against them from open projects. Each change in the common base would have to be differentiated by project. This could be done by any one of a number of means, font color, footnote, comments in either the Frame or PDF files o Project B: the clauses being added for project B and all of the clauses from the common base which currently have redlines against them from this project.The only point where I find using consolidated redlines problematic is when amendment projects are very parallel (e.g., in ballot at the same time).
Yes, it is complex, but we are managing a complex situation. I believe that it is the job of the editors, both volunteer and staff to tackle that complexity and reduce it to a form that removes as much of the burden as possible from the developers, voters, implementers and users. I also believe that in systematically doing so, they will make life easier for themselves.
Best regards,
Geoff
--Bob
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.