Exchanging variable between two graph over the ontology network

The engine supports Gout = convolve(G1,G2)
G1 an G2 are nested form ontology graphs with link operators that may include sript. Consider:

Gout = convolve(G1={ params.(0,1,4)},G2 = {params.(p1=#,p2=#,p3 = #)} )
Here I use the pass wild card to grab a sequence from G1 for use in G2.
Gout is null, G2 has modified some internal node values using script operators. The standard way to manage variables.

This is actually very useful for setting parameters in a large convolution, and then launching it. So the client just sets the parameter set, installs them in a larger graph, then launches the larger graph into the web. The open source ontology engine uses the technique to set engine paramters, it has an internal ontology called the Machine. It is available to set some paramaters, like regular expression string that attach to quotes, or sql sequences installed to match an operator, upgrading operators from proprietary vendors. The machine should be able to install dll routines and attach them to operators, using install convolutions with its own system graph.

Notice the idea here is to push just about all the functionality out onto graph programming, spo the core open source software noly manages about ten operators, most of them simple graph script.