Sparql does nested graphs

{
  "head": { "vars": [ "book" , "title" ]
  } ,
  "results": { 
    "bindings": [
      {
        "book": { "type": "uri" , "value": "http://example.org/book/book6" } ,
        "title": { "type": "literal" , "value": "Harry Potter and the Half-Bloo
      {
        "book": { "type": "uri" , "value": "http://example.org/book/book1" } ,
        "title": { "type": "literal" , "value": "Harry Potter and the Philosopher's Stone" }
      }
    ]
  }
}

This is from an online SPARQL query. Notice the use of the sophisticated tab display format. For this output to be truly G machine compatible, the same blocking operators need to be used on input and output.


So my G machine sort of hit the sweet spot in the SPARQL world, the idea of a SPARQL adaptive layer over SQLITE3, makes great sense. But TE is the more advanced language. The way to go here is to map the SPARQL query to TE and run that through the triple machine.