1. Comments for 802-15 Rev PAR – July 2010 Plenary
doc.: IEEE /0859r0
July 2010
Comments for Rev PAR – July 2010 Plenary
Date:
Authors:
Jon Rosdahl, CSR
Jon Rosdahl, CSR

2. July 2010
doc.: IEEE /0859r0
July 2010
Abstract
Comments from to regarding their proposed Revision PAR.
Jon Rosdahl, CSR
Jon Rosdahl, CSR

3. July 2010
Rev PAR
1.1 Project Number: the “i” should not be included in a revision PAR.
4.3 Project Completion Date for Submittal to RevCom: the date should be chosen to be at least 6 months from the start of the Sponsor Ballot start date. When choosing the “Date for Submittal to RevCom”, ensure that the date matches a RevCom agenda deadline.
Suggest a for a Dec RevCom target.
Jon Rosdahl, CSR

4. July 2010
Rev PAR
5.2 Scope: The Scope should describe what the scope of the final document will be. This section should not describe the work that will be done to make the document. (that is for 5.4 Need). The Scope of the PAR should match the scope that will be in the published document. The text from the proposal could be good information to include in the 5.4 Need paragraph.
Jon Rosdahl, CSR

5. July 2010
Rev PAR
5.4 Purpose: the Purpose should describe the purpose of the final document not the WG/TG effort. If the standard document will not include a purpose, that should be noted here in the PAR. The Purpose and the Scope should not be a word for word match.
5.6 Stakeholders – Describe “who” the stakeholders are e.g.,“…manufacturers and users of telecom, medical….” Do not just list the industries that are involved, or “activities” that may warrant use of the standard.
Jon Rosdahl, CSR

6. July 2010
References
Jon Rosdahl, CSR