The Microsoft embedded query language

http://en.wikipedia.org/wiki/Language_Integrated_Query
int someValue = 5;

var results = from c in SomeCollection
where c.SomeProperty < someValue * 2
 select new {c.SomeProperty, c.OtherProperty};
 foreach (var result in results)
{ Console.WriteLine(result); }

 No brainer, the graph machine can make this language happen over the web. But it is query only, no floating schemas in the data to manipulate, no graph layer, no named graphs. But great stuff, actually, build the query functions right into the language. Imagine if a graph of data contains its own instructions on unpacking and packing. There is a functional data/declaration language, k, it does this. The focus, abstract a graph layer, a container layer designed for high speed mobility. Then build everything on that. Within that layer, first class objects are automatic. Where object code mapped to memory, we want to lift that a bit, let the object code roam about as it works, hence the graph layer, it provides structured movement.

I start to get anxious to open up the debugger and screw around with the machine. But it has to be really interesting for me to jump in, not quite really interesting, but I like LINQ, and I think it can drive a ton of traffic onto the Global Wide Graph.

Oh, yes.  Everything you can do in LINQ, you can do in R with the Sqlite3 interface, the 150 Essential Lines for R/Sqlite Integration, cut that from the page on the right, you can make it do LINQ and more using R string handlers.