I wonder if the WG has discussed and rejected defining descriptive input (e.g. JSON, JSON-LD) for building graphs.
Currently compute graphs are built programmatically, but using dictionary options.
Taking that a bit further, an alternative could be adding generic ops (ops as string enum parameters) with input and output descriptions, options etc, that are specified in a dictionary (and serialized as JSON/-LD) and fed to a builder method.
That would allow e.g. prior transformations based on client needs. The code would look similar, just more dictionaries and less method calls.
I wonder if the WG has discussed and rejected defining descriptive input (e.g. JSON, JSON-LD) for building graphs.
Currently compute graphs are built programmatically, but using dictionary options. Taking that a bit further, an alternative could be adding generic ops (ops as string enum parameters) with input and output descriptions, options etc, that are specified in a dictionary (and serialized as JSON/-LD) and fed to a builder method.
That would allow e.g. prior transformations based on client needs. The code would look similar, just more dictionaries and less method calls.