Request #: HUTRR62 Title: Application Collection usage for System Multi-Axis Controllers Spec Release: 1.12 Received: Requester: Nathan C. Sherman Company: Microsoft Phone: +1.425.882.8080 FAX: +1.425.936.7329 email: nathans@microsoft.com ----------------- CurrentStatus: Approved Priority: Normal Submitted: 26 Feb 2016 Voting Starts: 14 Mar 2016 Voting Ends: 21 Mar 2016 Required Voter: Wacom Required Voter: Intel Required Voter: Apple Required Voter: Microsoft (Chair) ---------------- Summary: -------- The request is to establish a usage on the Generic Desktop Page for multi-axis controllers that are intended specifically for OS use to manipulate OS objects. Background: ----------- The current Generic Desktop page contains a CA usage for a Multi-Axis controller. However, this collection is generally available to any application that might wish to discover and use it. It is desirable to provide controllers for use of the operating system that are not made availble to applications while still permitting applications to use the typical multi-axis controllers that are already in the marketplace. Proposal: --------- Allocate usage Ox0E "System Multi-Axis Controller" Add the following to section 4, Table 6: Page 27: Usage ID = 0x0E Usage Name = System Multi-Axis Controller Usage Type = CA Change the following entry in the same Table Usage ID = 0F-2F (Per HUTRR51) Usage Name = Reserved Add to the description section 4.1, Page 29: System Multi-Axis Controller CA - A collection of controls that may contain the same controls as listed in Multi-Axis Controller (Usage 0x08) and/or additional associated controls such as wheels, dials, buttons etc., for exclusive use of the System. ========================================= Response: --------- 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.