Some consistency fixes to MIDI API, WRT device-port wording
authorJussi Kalliokoski <jussi.kalliokoski@gmail.com>
Sun, 12 Aug 2012 18:16:58 +0300
changeset 115 d7fa9333e334
parent 114 6e7e48ed2d82
child 116 af0f448cd8b3
Some consistency fixes to MIDI API, WRT device-port wording
midi/specification.html
--- a/midi/specification.html	Sun Aug 12 18:01:36 2012 +0300
+++ b/midi/specification.html	Sun Aug 12 18:16:58 2012 +0300
@@ -321,12 +321,12 @@
           class="idl">
         <dt>sequence&lt;MIDIPort&gt; enumerateInputs()</dt>
         <dd>
-          Returns a list of the MIDI input devices available on the system.
+          Returns a list of the MIDI input ports available on the system.
 <!-- TODO: Specify the steps the UA is required to take. -->
         </dd>
         <dt>sequence&lt;MIDIPort&gt; enumerateOutputs()</dt>
         <dd>
-          Returns a list of the MIDI output devices available on the system.
+          Returns a list of the MIDI output ports available on the system.
 <!-- TODO: Specify the steps the UA is required to take. -->
         </dd>
         <dt><a>MIDIInput</a> getInput(MIDIPort or DOMString target)</dt>
@@ -354,7 +354,7 @@
               <p>
                 If <var>target</var> is not a <code><a>MIDIPort</a></code>
                 instance, or if the MIDIPort is not a valid MIDI input
-                device, throw a <code>TYPE_ERROR</code> exception.
+                port, throw a <code>TYPE_ERROR</code> exception.
               </p>
             </li>
 
@@ -368,7 +368,7 @@
             <li>
               <p>
                 If made necessary by the underlying system APIs, reserve
-                the corresponding device for use within the current process.
+                the corresponding port for use within the current process.
               </p>
             </li>
 
@@ -405,7 +405,7 @@
               <p>
                 If <var>target</var> is not a <code><a>MIDIPort</a></code>
                 instance, or if the MIDIPort is not a valid MIDI output
-                device, throw a <code>TYPE_ERROR</code> exception.
+                port, throw a <code>TYPE_ERROR</code> exception.
               </p>
             </li>
 
@@ -419,7 +419,7 @@
             <li>
               <p>
                 If made necessary by the underlying system APIs, reserve
-                the corresponding device for use within the current process.
+                the corresponding port for use within the current process.
               </p>
             </li>
 
@@ -495,7 +495,7 @@
       <h2><a>MIDIPort</a> Interface</h2>
 
       <p id="event-midiport-disconnect">
-        Whenever the MIDI device corresponding the
+        Whenever the MIDI port corresponding the
         <code><a>MIDIPort</a></code> is disconnected or becomes unavailable,
         the UA SHOULD run the following steps:
       </p>
@@ -511,7 +511,7 @@
       </ol>
 
       <p id="event-midiport-connect">
-        Whenever the MIDI device corresponding the
+        Whenever the MIDI port corresponding the
         <code><a>MIDIPort</a></code> is connected or reconnected,
         the UA MUST run the following steps:
       </p>
@@ -529,11 +529,11 @@
       <dl class="idl" title='enum MIDIPortType'>
         <dt>"input"</dt>
         <dd>
-          If a MIDIPort is an input device, this MUST be this value.
+          If a MIDIPort is an input port, this MUST be this value.
         </dd>
         <dt>"output"</dt>
         <dd>
-          If a MIDIPort is an output device, this MUST be this value.
+          If a MIDIPort is an output port, this MUST be this value.
         </dd>
       </dl>
 
@@ -545,7 +545,7 @@
         <dt>readonly attribute MIDIPortType type</dt>
         <dd>
           <p>
-            A descriptor property to distinguish whether the device is an
+            A descriptor property to distinguish whether the port is an
             input or an output port.
             For <code><a>MIDIOutput</a></code>,
             this MUST be <code>"output"</code>.
@@ -555,24 +555,24 @@
         </dd>
         <dt>readonly attribute DOMString name</dt>
         <dd>
-          <p>The system name of the device.</p>
+          <p>The system name of the port.</p>
         </dd>
         <dt>readonly attribute DOMString manufacturer</dt>
         <dd>
-          <p>The manufacturer of the device.</p>
+          <p>The manufacturer of the port.</p>
         </dd>
         <dt>readonly attribute DOMString version</dt>
         <dd>
-          <p>The version of the device.</p>
+          <p>The version of the port.</p>
         </dd>
         <dt>readonly attribute DOMString fingerprint</dt>
         <dd>
           <p>
-            A unique ID of the device. This can be used by developers to
-            remember devices the user has chosen for different applications.
+            A unique ID of the port. This can be used by developers to
+            remember ports the user has chosen for different applications.
             The User Agent SHOULD make sure the
             <code><a>fingerprint</a></code>
-            is unique to only that device if possible.
+            is unique to only that port if possible.
           </p>
         </dd>
         <dt class="no-docs">[TreatNonCallableAsNull] attribute
@@ -601,7 +601,7 @@
         <p>
           The <code><a>disconnect</a></code> and
           <code><a>connect</a></code> events may not be applicable to all
-          MIDI devices or OS APIs. For example, an actual MIDI port does not
+          MIDI ports or OS APIs. For example, an actual  MIDI port does not
           support the notion of disconnect and connect while a USB MIDI Device
           may be plugged in or out on the fly. Therefore the semantics here is
           SHOULD, rather than MUST.
@@ -612,7 +612,7 @@
         <h3><a>MIDIInput</a> Interface</h3>
 
         <p id="event-midiinput-message">
-          Whenever the MIDI device corresponding the
+          Whenever the MIDI port corresponding the
           <code><a>MIDIInput</a></code> sends a MIDI message, the UA MUST
           run the following steps:
         </p>
@@ -620,7 +620,7 @@
         <ol>
           <li>
             <p>
-              Let <code>device</code> be the <code><a>MIDIInput</a></code>.
+              Let <code>port</code> be the <code><a>MIDIInput</a></code>.
             </p>
           </li>
 
@@ -628,7 +628,7 @@
             <p>
               Let <code>messages</code> be a newly constructed
               <code>sequence&lt;<a>MIDIMessage</a>&gt;</code> corresponding the
-              MIDI messages the device sent.
+              MIDI messages the port sent.
             </p>
           </li>
 
@@ -673,7 +673,7 @@
           <dt>boolean sendMIDIMessage(MIDIMessage message)</dt>
           <dd>
             <p>
-              Sends the MIDI message to the device and returns a boolean
+              Sends the MIDI message to the port and returns a boolean
               signifying whether the operation was succesful.
             </p>
           </dd>
@@ -682,7 +682,7 @@
                                     short? data0, short? dataX)</dt>
           <dd>
             <p>
-              Creates a new MIDI message, sends it to the device
+              Creates a new MIDI message, sends it to the port
               and returns a boolean signifying whether the
               operation was succesful.
             </p>