Doc.: IEEE 802.11-07/xxxxr0 Submission July 2007 Terry Cole, AMDSlide 1 802.11 Common Editorial Comment Resolution Process Date: 2007-06-29 Authors:

Slides:



Advertisements
Similar presentations
Overview of the IEEE Process. Overview of Process l Project Approval l Develop Draft Standards l Ballot Draft l IEEE-SA Standards Board Approval l Publish.
Advertisements

Overview of the IEEE Process IEEE P1620 Working Group Meeting 18 September 2002.
Doc.: IEEE /2079r0 Submission July 2007 Terry Cole, AMDSlide 1 WG Technical Editors Opening Report (July) Date: Authors:
Doc.: IEEE /2389r0 Submission Sept 2007 Terry Cole, AMDSlide 1 WG Technical Editors Opening Report (September) Date: Authors:
Doc.: IEEE /0674r0 Submission June 2009 Bruce Kraemer, Marvell; Adrian Stephens, Intel Corporation Slide 1 P802.11n report to EC on request for.
Doc.: IEEE /0642r0 Submission May 2008 Jesse Walker, Intel CorporationSlide 1 IEEE JTC1 Ad Hoc Mid-Week Status May 2008 Date:
Doc.: IEEE Submission November 2004 Robert F. HeileSlide 1 Forward P REVa-D6 to RevCom Robert F. Heile Chair
Editor’s Guideline July 2006 Terry Cole, AMDSlide Editor’s Guideline Version 1.1 Terry Cole, AMD WG Technical Editor & Simon Barber,
Doc.: IEEE /1084r00 Submission September 2015 Adrian Stephens, Intel CorporationSlide WG Chair comments to TGah Date: Authors:
Doc.: IEEE /197R0 Submission March 2003 Terry Cole, AMDSlide WG Technical Editor’s Report Terry Cole, AMD (WG technical editor status.
1 Session # Relay TG Opening Remarks and Session Agenda IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE j-07/021.
Overview of the IEEE Process. Overview of Process l Project Approval l Develop Draft Standards l Ballot Draft l IEEE-SA Standards Board Approval l Publish.
Session # Maintenance Task Group Closing Plenary Report IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE maint-09/0009.
Doc.: IEEE /197R3 Submission July 2003 Terry Cole, AMDSlide WG Technical Editor’s Report Opening Session, July 2003 Plenary Meeting Terry.
Title: LE TG Closing Report for Session #64 Document Number: h-09/0029 Date Submitted: Nov. 19, 2009 Source: Chair of LE TG: Mariana GoldhamerVoice:+972.
July 2006 Richard Paine, BoeingSlide 1 doc.: IEEE /1121r0 Submission k San Diego Closing Report
Doc.: IEEE /0792r0 Submission July 2008 Adrian Stephens, Intel CorporationSlide TGn Editor Report July 2008 Date: Authors:
Doc.: IEEE /0828r0 Submission May 2007 Harry Worstell, AT&TSlide 1 Procedural Clarification Notice: This document has been prepared to assist.
Doc.: IEEE /320R0 Submission May 2003 Terry Cole, AMDSlide SDL Amendments Terry Cole, AMD WG Technical Editor.
Doc.: IEEE /0408r0 Submission May 2005 John Klein, SymbolSlide 1 TPC Comments Notice: This document has been prepared to assist IEEE It.
Title: LE TG Closing Report for Session #60 Document Number: P802.16h-09/0007 Date Submitted: March 12, 2009 Source: Chair of LE TG: Mariana GoldhamerVoice:+972.
Minutes Document March 2006 Terry Cole, AMDSlide Editor’s Best Practices Terry Cole, AMD WG Technical Editor & Simon Barber, Devicescape.
Doc.: IEEE /1218r0 SubmissionBruce Kraemer, MarvellSlide 1 +1 (321) Marvell Lane, Santa Clara, CA, Name Company Address Phone.
Doc.: IEEE /0884r0 Submission July 2011 Adrian Stephens, Intel CorporationSlide 1 Introduction to the MC Date: Authors:
Doc.: IEEE /2263r1 Submission July 2007 Peter Ecclesine, Cisco SystemsSlide 1 TGy July Closing Report Date: Authors:
Doc.: IEEE /0777r0 Report July 2016 Yongho Seok (NEWRACOM)Slide 1 Date: Authors: P802.11ah Report to EC on Approval to forward draft.
Doc.: IEEE /0377r2 Submission March 2005 Adrian Stephens, Intel CorporationSlide 1 Ballotting Process Improvements Notice: This document has been.
Resolving Deadlocks in Comment Resolution
Relevant Rules on Recirculation
Sponsor Ballot Process
Editor’s Guideline Version 1.0
WG Technical Editor’s Report
IEEE aj Task Group May 2017 Agenda
November 2008 doc.: IEEE /1437r1 July 2011
P802.11s report to EC on request for approval to proceed to RevCom
November 2008 doc.: IEEE /1437r1 July 2011
July 2010 doc.: IEEE /0872r1 July 2010 P802.11u report to EC on request for conditional approval to proceed to RevCom Date: Authors:
P802.11n report to EC on request for approval to proceed to RevCom
P802.11n report to EC on request for approval to proceed to RevCom
P802.11w report to EC on request for approval to proceed to RevCom
P802.11z conditional approval report to ExCom
P802.11z conditional approval report to ExCom
WG Technical Editor’s Opening Report (March)
P802.11z conditional approval report to ExCom
Procedural review of initial WG ballot on P802.1CF
WG Technical Editor’s Report
Title: LE TG report for the opening plenary – Session #66
Avoiding unnecessary delays in the WG Letter Ballot process
P802.11w report to EC on request for approval to proceed to RevCom
November 2010 doc.: IEEE /0872r4 November 2010
P802.11w report to EC on request for approval to proceed to RevCom
P802.11w report to EC on request for approval to proceed to RevCom
Session # Maintenance Task Group Closing Plenary Report
Sponsor Ballot Comment Resolution
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [A Brief Overview of Draft Approval.
Title: LE TG Closing Report for Session #63.5
IEEE MEDIA INDEPENDENT HANDOVER
June 2009 r2doc.: IEEE /0674r0 doc.: IEEE /0674r0 April 2010
TGu Motions Authors: March 2010 Date: March 2010
WG Technical Editor’s Report
TGu Teleconference Motions
TGn Editor Report Sept 2008 Date: Authors:
September, 2001 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Briefing on IEEE Standards Style Manual]
Avoiding unnecessary delays in the WG Letter Ballot process
IEEE MEDIA INDEPENDENT HANDOVER
Sheung Li Task Group J Chairperson March 19, 2004
IEEE P Wireless Personal Area Network
Title: LE TG report for the opening plenary – Session #62
May 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG w May 2019 Closing Report] Date.
P802.11j Sponsor Ballot Procedure 10
Presentation transcript:

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide Common Editorial Comment Resolution Process Date: Authors:

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 2 Abstract A common process for dealing with editorial comments is presented for use in all groups functioning as comment resolution committees. Guidance is provided for dealing with “Must Be Satisfied”, “Technical”, and “Editorial” labels. Guidance is provided for writing responses to all editorial comments. Guidance is provided for recirculation of comments. Brings alignment within and with IEEE SA Supported by the hierarchy of policies and procedures of and above Reviewed by IEEE staff, CAC, and editors’ group

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide Common Editorial Comment Resolution Process Once a letter ballot reaches the 75% threshold, the WG Chair selects a Comment Resolution (CR) committee that is usually the Task Groups of that particular ballot. All groups within functioning as CR committees are expected to resolve WG and SB letter ballots comments using the following process starting from the opening session of the July meeting in San Francisco.

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 4 Must Be Satisfied Comments The IEEE-SA balloting rules are primarily concerned whether or not the comment was labeled as Must Be Satisfied and was attached to a Negative (Disapprove) vote. 1.Must Be Satisfied' is only meaningful if attached to a comment associated with a Disapprove vote or a comment from a mandatory coordination body (e.g., SCC10, SCC14, SA Editorial Staff, RAC). 2.Comments associated with Approve votes are left to the discretion of the CR committee. Attached to Disapprove Vote Marked Must Be Satisfied Attached to Approve Vote Obligation of CR committee If not marked “Must Be Satisfied” At discretion of CR committee

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 5 Editorial vs. Technical Comments The following guidelines are provided to help assess editorial vs. technical comments for use in : 1.The IEEE-SA balloting rules are unconcerned with labels such as Technical or Editorial. The only thing that matters is whether or not the comment was labeled as Must Be Satisfied and was attached to a Negative (Disapprove) vote. 2.Some things are clearly editorial. Some things are clearly technical. Other items are less clear. In some instances, what may appear as editorial to some may be technical to others. Marked “Must be Satisfied” NOT Marked “Must be Satisfied” Clearly Technical Clearly Editorial Middle Ground

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 6 Editorial vs. Technical Comments The following guidelines are provided to help assess editorial vs. technical comments for use in : 3.Clearly Technical Comment 1.If interoperability or the air or other interface is affected with and without the change. 2.If changing something from normative to optional, or vice versa. 4.Clearly Editorial Comment 1.If concerns only: grammar, spelling, punctuation, abbreviation, word usage, font, font size, font style, headings, figure or table titles, front matter material, formatting bibliography and references, and creating and using acronyms. 2.If concern only: (re)numbering items, clause and sub-clause titles, table and figure captions, moving and organizing text; must be not clearly technical per above. 3.Changing to an assigned number. 4.Changing editor’s note and footnotes. 5.If in doubt for middle ground, choose technical. In some instances, what may appear as editorial to some may be technical to others. Clearly Technical Clearly Editorial Middle Ground

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 7 Editorial Comment Resolution Editorial Comment Classification 1.CR chair classifies all comments by the voters T and E for purposes of work within the ballot resolution committee. May change voter’s self assessment of classification if deemed in error Must refer to statements regarding the editorial vs. technical for guidance Delegation to Editor and Reporting Back 2.CR chair delegates the E comments to the editor and instructs editor to report back to the CR body by a specific time on E comments that may have technical impact. Must refer to statements regarding the editorial vs. technical for guidance 3.Editor reports back to the body on any E comments that may have technical impact. –CR chair rules if these are reclassified and assigned back to the body 4.CR chair asks the body if any other editorial comments should be reclassified as T. –CR chair rules if these are reclassified and assigned back to the body Guidance to Editor 5.CR chair asks the editor if there is need for any non-binding straw poll as guidance to the editor for any editorial matters.

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 8 Editorial Comment Resolution 6.The CR chair entertains proposal to adopt a resolution for all E comments not attached to Negative votes or not marked as Must Be Satisfied, the body considers the proposal and adopts a resolution. Suggested resolution is as follows: This comment is deemed editorial and delegated to the document editor for consideration in developing future drafts. Please note that the IEEE standards are edited professionally prior to publication. Note: Editors may provide additional notes on what they do with comments but these are not part of the formal comment response and may be created after comment resolution is completed 7.The editor brings forward proposed comment resolutions for all E comments attached to Negative votes and marked as Must be Satisfied, the CR body considers the proposal, and the CR committee adopts a resolution. An appropriate response could be many things but will ultimately be determined by acknowledgement or acceptance by the balloter, review and agreement by the ballot group, process review by ExCom, RevCom, etc. Examples include: Agreed. State what will be done. Disagree. State why. Agreed. This change will be implemented by IEEE-SA Editorial Staff prior to publication. The WG will request that IEEE-SA Editorial Staff review this comment prior to publication and implement changes as required by their editorial guidelines.

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 9 Editorial Comment Resolution Marked “Must be Satisfied” NOT Marked “Must be Satisfied” Clearly Technical Clearly Editorial Middle Ground CR committee adopts resolution with response language in step 6, and the comment is delegated to editor for future document development. Editor drafts comment response and CR committee adopts resolution in step 7.

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 10 Editorial Comment Resolution Editorial Comment Recirculation –E comments marked as Must Be Satisfied and attached to a Negative vote are treated as any other comment. They are presented to the voters in recirculation ballot once. Editorial Improvement in the Document –Items are delegated to the editor for future document development in step 6. The TG editor will be diligent to incorporate as many of these as is feasible to improve the editorial maturity of the draft. Not all editorial comment proposals are valid solutions. The editor is not bound to act positively on all editorial comments delegated to the editor. Not all comments delegated to the editor may be acted on immediately. The editor will have a work plan that calls for doing some changes at a later time or together with other changes. Some (few) items delegated to the editor may be referred by the editor to the IEEE staff to be addressed during professional editing prior to publication by IEEE staff. –The TG editor is diligent to move forward with minimal editorial change once the required approval rate is achieved.

doc.: IEEE /xxxxr0 Submission July 2007 Terry Cole, AMDSlide 11 Editorial Comment Resolution Marked “Must be Satisfied” NOT Marked “Must be Satisfied” Clearly Technical Clearly Editorial Middle Ground Presented to voters once in subsequent recirculation ballot per step 8.