--- a/midi/specification.html Mon Oct 29 14:29:23 2012 -0700
+++ b/midi/specification.html Tue Oct 30 11:33:13 2012 -0700
@@ -81,21 +81,24 @@
<p>
The Web MIDI API is not intended to directly implement high-level concepts such as sequencing; it does not directly support Standard MIDI Files, for example, although a Standard MIDI File player can be built on top of the Web MIDI API. It is also not intended to semantically capture patches or controller assignments, as General MIDI does; such interpretation is outside the scope of the Web MIDI API (though again, General MIDI can easily be utilized through the Web MIDI API).
</p>
- <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>
- <li>A <a href="#MIDIAccess">MIDIAccess</a> object, which enables enumeration of and access to the MIDI devices available to the user agent.
- </li>
- <li>A <a href="#MIDIPort">MIDIPort</a> interface, which represents a MIDI input or output port and exposes information about the interface - its name, manufacturer, type and unique identifier.
- </li>
- <li>A <a href="#MIDIInput">MIDIInput</a> interface, which implements MIDIPort but also enables MIDI message handlers to be attached to the device.
- </li>
- <li>A <a href="#MIDIOutput">MIDIOutput</a> interface, which implements MIDIPort and additionally exposes methods to send MIDI messages to the output port.
- </li>
- <li>A <a href="#MIDIMessage">MIDIMessage</a> interface, which represents a sequence of MIDI data bytes along with a timestamp. This interface is used for receiving MIDI as well as for some types of sending.
- </li>
- </ul>
+ <section>
+ <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>
+ <li>A <a href="#MIDIAccess">MIDIAccess</a> object, which enables enumeration of and access to the MIDI devices available to the user agent.
+ </li>
+ <li>A <a href="#MIDIPort">MIDIPort</a> interface, which represents a MIDI input or output port and exposes information about the interface - its name, manufacturer, type and unique identifier.
+ </li>
+ <li>A <a href="#MIDIInput">MIDIInput</a> interface, which implements MIDIPort but also enables MIDI message handlers to be attached to the device.
+ </li>
+ <li>A <a href="#MIDIOutput">MIDIOutput</a> interface, which implements MIDIPort and additionally exposes methods to send MIDI messages to the output port.
+ </li>
+ <li>A <a href="#MIDIMessage">MIDIMessage</a> interface, which represents a sequence of MIDI data bytes along with a timestamp. This interface is used for receiving MIDI as well as for some types of sending.
+ </li>
+ </ul>
+ </section>
</section>
<section id="conformance">
@@ -133,15 +136,15 @@
<p>
The term <dfn><a href=
"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime/Overview.html#sec-DOMHighResTimeStamp"
- >DOMHighResTimeStamp</a></dfn> is defined in the <a href=
+ >DOMHighResTimeStamp</a></dfn> is defined in <a href=
"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime/Overview.html"
- >High Resolution Time Specification</a>.
+ >[[!HIGH-RESOLUTION-TIME]]</a>.
</p>
<!-- FIXME: This list is not exhaustive. -->
</section>
<section>
- <h2>Security and privacy considerations</h2>
+ <h2>Security and Privacy Considerations</h2>
<p>
There are two primary security and privacy concerns with adding the Web MIDI API to the web platform:
</p>