Model <-> interface link in Squiggle Hub

[berekuk]

Previously discussed here.

For Squiggle Hub, model -> interface (signature) link should really be "export variable" -> interface.

Especially if we want multiple interfaces per model.

Because if we ask for a signature on an interface level, it'll be something like "this interface expects the model to export fn(id1, id2), ids can be from [this list]", and then you can't export multiple different functions from your monorepo-style model, because of the name collisions.

Two alternative options:

1. Define interfaces somewhere in "exported variables config" outside of Squiggle code; basically a JSON file that says "exported var fn implements interface interface_id_1, exported var fn2 implements interface interface_id_2”.
2. Define interfaces (and, more generally, semantical definitions for some variables that the model exports) in Squiggle code.

Option (2) is better in the long run, but harder, because for the optimal DX (e.g. autocompletion) we'd need a deep integration with the external ontologies that are managed by Squiggle Hub.

“Deep integration” means that each piece of Squiggle code should be evaluated and edited in the context of the ontology defined elsewhere (e.g. in Squiggle Hub database / Ken-style graph of concepts).

I’m not sure if that reference to the ontology can be implemented on the same level as our upcoming import/export syntax. My guess is that we’ll need a separate syntax for that.

[OAGr]

Is this done now? Can we close this issue?

(We have some interface support in Squiggle Hub)