rough attempt at scope qualification
authorScott Graham <scottmg@google.com>
Wed, 21 Sep 2011 09:44:02 -0700
changeset 114 c788513485e5
parent 113 5bc8759a9f5f
child 116 4153b586295c
child 117 fd9ea2f17eaa
rough attempt at scope qualification
gamepad.html
--- a/gamepad.html	Wed Sep 21 08:37:44 2011 -0700
+++ b/gamepad.html	Wed Sep 21 09:44:02 2011 -0700
@@ -150,6 +150,26 @@
     </section>
 
     <section>
+
+      <h2>Scope</h2>
+
+      <p>Interfacing with external devices designed to control games has the
+      potential to become large and intractable if approached in full
+      generality. In this specification we explicitly choose to narrow scope
+      to provide a useful subset of functionality that can be widely
+      implemented and broadly useful.</p>
+
+      <p>Specifically, we choose to only support two categories of input from
+      devices: buttons and axes. Both buttons and axes report analog values,
+      buttons ranging from [0..1], and axes ranging from [-1..1]. This allows
+      support for devices common to current gaming systems including gamepads,
+      directional pads, joysticks, wheels, pedals, accelerometers. It excludes
+      support for more complex devices that do motion sensing, depth sensing,
+      video analysis, gesture recognition, and so on.</p>
+
+    </section>
+
+    <section>
       <h2><a>Gamepad</a> Interface</h2>
       <p>
         This interface defines an individual gamepad device.