--- a/midi/specification.html Thu Dec 13 17:28:26 2012 +0200
+++ b/midi/specification.html Thu Dec 13 17:58:27 2012 +0200
@@ -85,7 +85,7 @@
<h3>API Overview</h3>
<p>The Web MIDI API consists of the following set of interfaces and objects, as well as some supporting interfaces:</p>
<ul>
- <li>A <a href="#NavigatorMIDIAccess">NavigatorMIDIAccess</a> interface, which is supported on the window.navigator object in user agents. This interface has only one method which enables a developer to request access to MIDI on the system.
+ <li>A <a href="#requestMIDIAccess">requestMIDIAccess</a> method, which is supported on the window.navigator object in user agents. This method enables a developer to request access to MIDI on the system.
</li>
<li>A <a href="#MIDIAccess">MIDIAccess</a> object, which enables enumeration of and access to the MIDI devices available to the user agent.
</li>
@@ -153,7 +153,7 @@
<li>Additionally, combined access to input and output ports on a given device (the ability to send <b>and</b> receive system exclusive messages, in particular) might allow sophisticated developers to query and test for particular MIDI-connected devices, such as samplers, and either using the presence of those devices for more precise fingerprinting, destroying data (erasing samples or patches on the devices), attempting to capture data from the devices (e.g. downloading samples from samplers, then uploading to the network), or simply initiating malicious action (e.g. sending MIDI commands to a lighting control system to turn lights on and off). </li>
</ol>
<p>
- These issues will be further explored prior to this specification becoming a Recommendation. In the meantime, the <a href="#NavigatorMIDIAccess">suggested security model</a> explicitly allows user agents to require the user's approval before giving access to MIDI devices, although it is not currently required to prompt the user for this approval. It is noted that some web systems (e.g. Java) give access to MIDI interfaces without prompting, although this may not be the security model that this specification eventually uses.
+ These issues will be further explored prior to this specification becoming a Recommendation. In the meantime, the <a href="#requestMIDIAccess">suggested security model</a> explicitly allows user agents to require the user's approval before giving access to MIDI devices, although it is not currently required to prompt the user for this approval. It is noted that some web systems (e.g. Java) give access to MIDI interfaces without prompting, although this may not be the security model that this specification eventually uses.
</p>
</section>
@@ -161,11 +161,11 @@
<h2>Obtaining Access to MIDI Interfaces Available to the User Agent</h2>
<section>
- <h2 id="NavigatorMIDIAccess">The <a>NavigatorMIDIAccess</a> Interface</h2>
+ <h2 id="requestMIDIAccess">requestMIDIAccess()</h2>
<dl class="idl"
- title="interface NavigatorMIDIAccess">
- <dt>void getMIDIAccess(SuccessCallback successCallback,
+ title="partial interface Navigator">
+ <dt>void requestMIDIAccess(SuccessCallback successCallback,
optional ErrorCallback errorCallback)</dt>
<dd>
<p>
@@ -186,8 +186,8 @@
</p>
<p>
- When the <dfn id="dom-navigator-getmidiaccess">
- <code>getMIDIAccess()</code></dfn> method is called, the user
+ When the <dfn id="dom-navigator-requestmidiaccess">
+ <code>requestMIDIAccess</code></dfn> method is called, the user
agent MUST run the following steps:
</p>
@@ -274,8 +274,6 @@
</p>
</dd>
</dl>
-
- <div class="idl" title="Navigator implements NavigatorMIDIAccess"></div>
</section>
<section>
@@ -648,7 +646,7 @@
console.log( "Failed to get MIDI access - " + msg );
}
-navigator.getMIDIAccess( onMIDISuccess, onMIDIFailure );</pre>
+navigator.requestMIDIAccess( onMIDISuccess, onMIDIFailure );</pre>
</section>
<section>
@@ -733,7 +731,7 @@
console.log( "Failed to get MIDI access - " + msg );
}
-navigator.getMIDIAccess( onMIDISuccess, onMIDIFailure );</pre>
+navigator.requestMIDIAccess( onMIDISuccess, onMIDIFailure );</pre>
</section>
</section>