Could this not be considered to apply this to generate a PDF of the MIDI 2.0 implementation of a device instead of the fixed MIDI 1.0 "paper" forms ? Even the actual functionality is embedded in the MIDI-CI protocol. There could be behavior things that can related to the MIDI 2.0 spec, such as how the device does protocol selection, implements SysX8, jitter. MIDI 1.0 and/or 2.0, requires 31.250kpsec speed throttling, flex messages , function blocks, # of groups, etc...
Could this not be considered to apply this to generate a PDF of the MIDI 2.0 implementation of a device instead of the fixed MIDI 1.0 "paper" forms ? Even the actual functionality is embedded in the MIDI-CI protocol. There could be behavior things that can related to the MIDI 2.0 spec, such as how the device does protocol selection, implements SysX8, jitter. MIDI 1.0 and/or 2.0, requires 31.250kpsec speed throttling, flex messages , function blocks, # of groups, etc...