MAS-DT How do we represent pre-defined action templates and preferences in the configuration schema
If we don't want to hard-code a bunch of stuff on the ORI side and instead want to define all these capabilities/rules/preferences in the specification then I'm struggling to see how we do that.
So far what I've got is a single sample_profile action containing all the changeable variables from yo+sample+tbdlist (which is pretty bespoke to MOGli+MAS-DT) and iterates out that 4x4x4(64 combinations) grid of parameters into oneOf actions which have a boolean sample_compliance field.
The user sets prioritise=[speed|endurance] and allow non-compliant sampling=[true|false]
Then the schema says ORI can send any one of those parameter combinations but if the PI has specified they must use the sample_compliance:true ones then that limits the choice.
Ideally I'd separate out the yo behaviour stuff and the sample behaviour stuff but I can't see how we can do that and also define what represents MOGli compliant sampling in the schema.
.. and I definitely can't figure out how we make that generic enough to be used for something other than MOGli.