ACTION-71: Clarify goal #3 in IndieUI events, transition path (including polyfill implementations) are a goal of the working group effort, but not of the spec itself.
--- a/src/indie-ui-events.html Wed Mar 05 16:21:38 2014 -0800
+++ b/src/indie-ui-events.html Wed Mar 05 18:14:54 2014 -0800
@@ -121,12 +121,12 @@
<section id="intro-goals" class="informative">
<h3>Goals</h3>
- <p>The primary goals of this specification are declared as the following:</p>
+ <p>The primary goals of the Events Module specification are declared as the following:</p>
<ol>
<li>Make it easier for web developers to author consistently usable interfaces that are input-agnostic and independent of a user's particular platform, hardware, locale, and preferences.</li>
<li>Enable every type of control in these interfaces to be programmatically determinable and controllable by both mainstream and alternate forms of user input.</li>
- <li>Provide a clear path for web developers to smoothly transition from currently existing physical events to IndieUI events, during the period when implementations of IndieUI are incomplete. This will likely be achieved through polyfill implementations in common JavaScript libraries.</li>
</ol>
+ <p>The IndieUI Working Group also hopes to provide a clear path for web developers to smoothly transition from currently existing physical events to IndieUI events, during the period when implementations of IndieUI are incomplete. This will likely be achieved through polyfill implementations in common JavaScript libraries, though such implementations are not a required deliverable of the IndieUI Working Group, and documentation of this development path is not a requirement of this Events Module specification.</p>
</section>
<section id="intro-scope" class="informative">