Like this:
Sql:{Tables,Columns,Conditions}
The Json will soon have operators, arithmetic and variable updates. So, all graph machines, underneath the grammar, know what to do. ' The elementary path is Json easy text to Bson precompiled. Make Sql a defined identifier? Hmm, how does the Dublin Core do that, lemme see.. well something like that. Joins come with the convolution operator, so its coming. But we need some very simple rules for a forward symbol definition, something natural to the clients has they type Hmm.
The point though, is the query can be tested at home, gotten just right then sent off to the tables in the big graph as Bson. But Json, with that engine code, sort of feeds the installed graph processor. I have that engine tuuned to support script, Bson, lazy Json, sqlite3. It is self contained, carrys its own symbols. The graph layer (Sqlite3) provides an exo path!. That machine will bind faster than anything else, graft right onto the exokernel, port right into a Cray. It is so simple, anyone can Json at the terminal, the rules so simple. Done anonymously, the pinball machine, no loops everything eventually comes home. I have won this, I have the Regex of ontology navigating, and it is ready just in time for MIT, its 1500 lines of code where is my zillion dollars?
No comments:
Post a Comment