Hopefully I am allowed to post my own paper.

Try http://slypstreem.com/PortableGridEngine.pdf


Its a little out of date and it doesnt go into detail about the modeling language.

Obviously, if I want this to catch on I plan on explaining how to use the language. Im hoping to do that piece wise by example rather than in a technical book.

If anyone has an idea of how I can do that here let me know. After we get a slightly better example in code I will post the software and some examples.

Until then...

The modeling technique involves moving a cursor around an information structure and reading or writing to it. Because it involves moving a cursor complete structures need not be defined, For example, we can have a word that just moves to a color field and then is used for seting, reading or searching over it.

Because of that we shouldnt define words like MountainBike but we should define mountain and bike. The engine can scan around inside the definitions to see if anything can be made to match. So we could also use Big Red Bike to define, search, or describe.


It makes function calls look a little strange because references to the arguments are done by descriptions of them or by their positions (e.g. the first red bike), not by their names. Because these can be resolved early it wont slow processing down much.

If that makes sense to you then you are a better reader than I am! I will try to speed this along.

One last teaser which I hope will sound cool to some people but not scare the others: The operators for moving the cursor around information are similar to the arithmetic =, +, *.

Keep working on ideas people! I did the software but I think people here could make a better UI than I could.