home *** CD-ROM | disk | FTP | other *** search
- Submitted-by: jazz@hal.com (Jason Zions)
-
- >If objections are rejected because the working group didn't like the
- >idea, that only serves to defeat the purpose of the balloting group.
-
- Do you really believe that introducing a one-ballot-cycle delay before
- incorporating a change which the working group thought shouldn't be
- implemented and the ballot group does think should be implemented defeats
- the purpose of the ballot group? Remember, that's the *maximum* impact that
- can be caused by inappropriate rejection of a ballot objection that is later
- supported by the ballot group.
-
- >In fact, however, the balloting group has different motivations and
- >strategies than the working group. The fact that the working group
- >has wrestled with something doesn't enable the technical reviewers to
- >make presumptions about the balloting group's consensus.
-
- The fact that they are technical reviewers gives them all the right in the
- world to make presumptions about the ballot group's consensus; if they are
- wrong, the ballot group will so inform them in the next round. As I have
- stated before, technical reviewers need to adopt a position on each change;
- there's nothing wrong with adopting a position which is conservative with
- respect to the express intent of the working group in the absence of
- conflicting direction from the bulk of the ballot group.
-
- It sounds like the only procedure which is acceptable to you is for all your
- objections to be accepted and acted upon by the TRs, and for the ballot
- group to have to overturn you, if you're wrong, on the next round. Given the
- track record of contentious ballot objections seldom being supported by
- ballot groups, what justification do you give for TRs and Technical Editors
- to expend significant amounts of time implementing changes that statistics
- show will be backed-out in the next round?
-
- Jason
-
- Volume-Number: Volume 34, Number 19
-
-