audio/MIDI/CV graph functionality?

[mxmilkiib]

would/could these conventions provide the abstractions/system to supply the features of an audio graph?

as in, that could be used to connect audio/MIDI/CV consuming/producing web tools

such a system would enable not just an audio effects rack style flow, but actual in-browser intra-tool modular synthesis, say, between Cardinal and other such apps

if CV streams are a new one to anyone, they're part of the JACK/PipeWire API and the LV2 plugin format

fwiw fyi, the JACK and LV2 systems have a client/port metadata system that is likely worth looking at, in this regard

Carla, set to multi-client mode (system wide audio graph, not separate internal/external graphs), exposes LV2 plugins it hosts as JACK clients in their own right, using the appropriate plugin metadata as properties for the JACK port type, name, pretty-name, etc.

[dschuff]

I think what you are looking for is more along the lines of an API; IIUC this would be a sort of "standard" that would connect different tools (as opposed to, say just an abstraction over the existing browser APIs like web audio?).

That's a bit more high-level than what this repo is really used for. Mostly it contains ABI conventions (which apply across all APIs at a particular layer) or other low-level conventions that apply to toolchains but not really to user-level APIs.