Can you describe exactly what feature you're trying to get from this (i.e. user scenario)?

(In reply to comment #1)
> Can you describe exactly what feature you're trying to get from this (i.e.
> user scenario)?

See "9.2 Enumerating Inputs and Outputs" example:
https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html#enumerating-inputs-and-outputs

That's pretty common... with toJSON, it becomes something like:

function showPorts( midiAccess ) {
  function show(port, i){
     console.log("Input port #" + i + " " + port.toJSON());
  }
  midiAccess.enumerateInputs().forEach(show);
  midiAccess.enumerateOutputs().forEach(show);
}

(In reply to comment #2)
> (In reply to comment #1)
> > Can you describe exactly what feature you're trying to get from this (i.e.
> > user scenario)?
> 
> See "9.2 Enumerating Inputs and Outputs" example:
> https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.
> html#enumerating-inputs-and-outputs
> 
> That's pretty common... with toJSON, it becomes something like:
> 
> function showPorts( midiAccess ) {
>   function show(port, i){
>      console.log("Input port #" + i + " " + port.toJSON());
>   }
>   midiAccess.enumerateInputs().forEach(show);
>   midiAccess.enumerateOutputs().forEach(show);
> }

That sample was just enumerating the parameters for debugging purposes, though - serialization implies deserialization.  I don't think the "serialize everything in the input/output object" is a particularly interesting scenario, unless you're trying to imply that fromJSON() could re-create the port - and this is a "magic host object".  :)

(In reply to comment #3)
> That sample was just enumerating the parameters for debugging purposes,
> though - serialization implies deserialization.  I don't think the
> "serialize everything in the input/output object" is a particularly
> interesting scenario, unless you're trying to imply that fromJSON() could
> re-create the port - and this is a "magic host object".  :)

Ok, fair call. I currently don't have a case for serialization (apart form using it as a stringifier in debugging). 

I think there might be a case for storing serialized versions of previously used ports, etc. But I need to encounter the actual use case through playing around a bit more with the API.... 

Can we mark this as RESOLVED/NEEDSINFO?

Batch-closing RESOLVED MIDI issues. Reminder: midi issues now tracked at https://github.com/WebAudio/web-midi-api/issues