JSON Snobbery

Database and semantic graphs once again, bear with me.

My topic is the idea that JSON is separate from Javascript. I say JSON script is a subset of Javascript, they should add, as in:

Javascript  append JSON  = Javascript

Why do I bring this up? Because they both are, in script format, expression graphs using asynchronous branch markers, with the same grammar. They both are directly 'executable' by interpreters. And, finally, why not just keep the complete javascript grammar and let data and data generators both be valid graphs?
Javascript isn't database, omigod!
consider:

join(sumof,{for (var i=0;i<256;i++; random(i)})

First, before we freak, what does this mean? Take the sum of 256 random numbers. Written properly, which I am bad at, both sides are valid Javascript expression graphs valid for a join operation as database. It works, because join is a fully re-entrant Javascript interpreter modified to handle operator precedence and traversal. It has a couple of enhanced wild card, traversal logic operators, not shown; but otherwise is just a layer extension of the Javascript interpreter powered by another jump in Moore's law.

Any form of Javascript expression graphs are usable because the join operator uses a limited set of graph traversal methods. Hence, parsed JSON, adapted SQL bases, direct B Tree, memory, plain text or the kitchen sink can be valid expression graph; as long as they have method implementations for the traversal methods.