Descriptive Language Usage in TGv

Slides:



Advertisements
Similar presentations
LB84 General AdHoc Group Sept. Closing TGn Motions
Advertisements

[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
Motions Date: Authors: January 2006
IEEE White Space Radio Contribution Title
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
TGp Closing Report Date: Authors: July 2005 Month Year
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
JTC1 Ad Hoc Closing Report
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Quick Beacon Impacts on LB 92
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
CID#102 - Channel Allocation for P2P
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
IEEE WG Opening Report – July 2008
ADS Study Group Mid-week Report
Attendance for July 2006 Date: Authors: July 2006
IEEE P Wireless RANs Date:
Attendance for November 2006
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
IEEE White Space Radio Intended timeline
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
TGv Redline D0.10 Insert and Deletion
IEEE WG Opening Report – July 2007
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGp Closing Report Date: Authors: March 2007 Month Year
November Opening Report
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
Liaison Report From Date: Authors: Month Year
Beamforming and Link Adaptation Motions
[ Policies and Procedure Summary]
Draft P802.11s D1.03 WordConversion
IEEE White Space Radio Liaisons
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGp Closing Report Date: Authors: January 2006 Month Year
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
11k Public Awareness Program
Attendance for November 2006
IEEE White Space Radio First Call for Contributions
TGp Closing Report Date: Authors: November 2006 Month Year
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Descriptive Language Usage in TGv Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 November 2007 Descriptive Language Usage in TGv Authors: Date: 2007-11-07 Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair stuart@ok-brit.com as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Slide 1 Emily Qi (Intel Corp) et al Page 1 John Doe, Some Company Emily Qi

Month Year Month Year doc.: IEEE 802.11-yy/xxxxr0 doc.: IEEE 802.11-yy/xxxxr0 November 2007 Abstract This document provide a guidance for descriptive language usage in TGv draft. Slide 2 Emily Qi (Intel Corp) et al Page 2 Emily Qi John Doe, Some Company

November 2007 Background It is a good idea to use descriptive language in clause 7, 8, and 10, but it is not a requirement from 802.11 WG Editor. In 802.11-2007 std, “shall” and “may” are used everywhere in clause 7 Some suggestions from 802.11 WG Editor: use “is” instead of “shall” use “can” or “might” or “may” instead of “should”. The current 802.11k draft follows the following guidance: shall" and "may" are normative language terms and should not be used in clause 7 frame format descriptions.  Use "is present“ in place of "shall be present" and "can be present" in place of "may be present". Slide 3 Emily Qi (Intel Corp) et al

Guidance for TGv draft Option 1: November 2007 Guidance for TGv draft Option 1: Use "is present“ in place of "shall be present" and "can be present" in place of "may be present“ in clause 7 and clause 10 Option 2: Use "is present“ in place of "shall be present" and “may be present" in place of “not always present” in clause 7 and clause 10 Slide 4 Emily Qi (Intel Corp) et al