IEEE 802.11-19/0912r0 Editorial Changes Summary for May 2019 Doc
Gain insights into the editorial changes made to approved resolutions in the IEEE 802.11-19/0912r0 document for May 2019. Explore the editor's process of enhancing grammar and style while ensuring technical accuracy. Examples highlight the nuances of incorporating resolutions effectively.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
May 2019 doc.: IEEE 802.11-19/0912r0 Editorial changes to approved resolutions Date: 2019-05-14 Authors: Name Robert Stacey Affiliations Intel Address Phone email robert.stacey@intel.com Submission Slide 1 Robert Stacey, Intel
May 2019 doc.: IEEE 802.11-19/0912r0 Abstract Overview of some the actions this editor takes when incorporating approved resolutions and in the general maintenance of the draft Submission Slide 2 Robert Stacey, Intel
May 2019 doc.: IEEE 802.11-19/0912r0 Discussion The editor often makes editorial changes to the approved resolutions: To correct grammar To make style more cohesive with rest of the document and other resolutions When this occurs, the editor adds editing notes to the comment tracking database (Editing Notes column) Editor does not make technical changes However, sometimes what the editor perceives to be an editorial fix results in an inadvertant technical change. Editor is not trying to override the editorial will of the group; if a resolution is intended to express an editorial preference, the editor will abide by it The editor has a draft review committee primarily composed of the authors of the resolutions to catch errors Some examples are provided for discussion Submission Slide 3 Robert Stacey, Intel
May 2019 doc.: IEEE 802.11-19/0912r0 Example 1 Following notations are used when describing the indices for a set of subcarriers: [x1:y1] represents the set of subcarriers whose index k satisfies x1 k y1. [x1:y1, x2:y2] represents the set of subcarriers whose index k satisfies either x1 k y1 or x2 k y2. Approved Draft Grammar: Add missing article, adjust number Style: Add bullets, remove periods Submission Slide 4 Robert Stacey, Intel
May 2019 doc.: IEEE 802.11-19/0912r0 Example 2 Valid range of m for Equation (27-131) is as follows. PPDU is a 20, 40, 80 or 160 MHz PPDU: Valid range of m is -iRU26,start+ 1 m -1. PPDU is an 80+80 MHz PPDU and iRU26,start is less than or equal to 37: Valid range of m is -iRU26,start+ 1 m -1. PPDU is an 80+80 MHz PPDU and iRU26,start is greater than 37: Valid range of m is -iRU26,start+ 38 m -1. Approved Draft Grammar: Missing article Style: Align with other variable descriptions Submission Slide 5 Robert Stacey, Intel
May 2019 doc.: IEEE 802.11-19/0912r0 Example 3 A STA transmitting an HE PPDU that carries a broadcast addressed MPDU shall set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to 16 s. A STA transmitting an HE PPDU that carries a group addressed, but not broadcast addressed, MPDU shall not set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to a value which is less than that required for any of the intended recipients in the group address. Approved A STA transmitting an HE PPDU that carries a broadcast MPDU shall set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to 16 s. A STA transmitting an HE PPDU that carries a multicast MPDU shall not set the value of the TXVECTOR parameter NOMINAL_PACKET_PADDING to a value which is less than that required for any of the recipients in the multicast group. Draft for review Draft As identified during review, editor s changes were not appropriate Submission Slide 6 Robert Stacey, Intel
