Request #:       <Assigned by HID Chair>
Title:           <Assigned by Requester>
Spec Release:    1.12
Received:        <Assigned by HID Chair>
Requester:       (Must be authorized by the HID Working Group Member Company)
Company:         (Must be a USB HID Working Group Member Company)
Phone:           
FAX:             
email:           
-----------------
CurrentStatus:   Submission
Priority:        <Assigned by HID Chair>
Submitted:       <Assigned by HID Chair>
Voting Starts:   <Assigned by HID Chair>
Voting Ends:     <Assigned by HID Chair>
Required Voter:  (Must be a USB HID Working Group Member Company)
Required Voter:  (Must be a USB HID Working Group Member Company)
Required Voter:  (Must be a USB HID Working Group Member Company)
----------------

Summary:
--------
Enter a one or two sentence description of the purpose of the change to the 
Usage Tables, eg, add usages for a particular set of controls.         

Background:
-----------
Provide background information around the problem and how changes to the HID
Usage Tables will solve the problem.

Proposal:
---------
Provde change text for the HID usage tables, and an explanation of the intent 
and notes on the usage of each change, for example,

Add the following to section xx, Table yy: zzz Page
Usage ID		= <Proposed Usage Value>
Usage Name		= <Proposed Usage Name>
Usage Type		= <Proposed Usage Type>

<Usage Name >< Usage Type> - Definition of the new Usage ID and any constraints 
			     on its use.
If the Review Request utilizes a formerly Reserved Usage, also propose a change
to the range of Reserved Usages to omit the newly defined usage.

Particilarly complex changes should also be accompanied by a sample Report Descriptor
utilizing the changes with a description of the reporting mechanism.

Response:
---------

<Added by HID Chair upon closing the Request>                                      


Notes on Approval Procedure:
----------------------------

HID WG On Line Voting Procedures

1. Votes are on a per company basis.

2. Each Review Request shall have attached a Required Voter List that is the
result of recruiting by the HID Chair and submitter of members of the USB IF.
Required Voter List must include the HID Chair plus 2 companies (other than
the submitter) plus any others designated by the HID Chair at the Chair?s
discretion. The Required Voter List ensures that a quorum is available to
approve the Request.

3. Impose a 7-calendar-day posting time limit for new Review Requests. HID
Chair or designate must post the RR within 7 calendar days. HID Chair or
designate must work with the submitter to make sure the request is valid prior
to posting. Valid review request must include all fields marked as required in
the template. A new template will be adopted that requires at least the
following fields: Change Text, Required Voter List, Review Period End Date and
Voting End Date, Submittal Date, Submitter, Review Request Title and RR Number.

4. If a RR approval process stalls, the HID Chair may call a face-to-face
meeting or conference call to decide the issue. Submitter may request that this
take place.

5. Impose a minimum 15-calendar-day review period on a posted RR prior to the
voting period. At HID Chair discretion, changes to the RR may require this
review period to restart.

6. The Chair will accept votes via documentable means such as mail or e-mail
during the 7 calendar days after the close of the review period. If a Required
Voter does not vote during the period, then there is no quorum and the Chair
may pursue the absent required voter and extend the voting period. The Chair
may designate a substitute for the absent voter and extend the voting period
if necessary.