The main point of DOM nested rows

Originally, the code I have been posting about going directly from SQL in nested order into a DOM tree. I patent that one too.

But it is great for display because we can directly instantiate a html, svg, or xml tree onto the document. It makes for great overlays in html, great dynamics.

But that got me into simple syntax.
The idea that sql is simple syntax consistent, web authors can do sql. So simple syntax includes sql, and more, an outer sql shell. Adding plot, table, get. Extending the alias concept across author expressions by keeping the as, and limit, offset across the syntax. Make a limit, ten key words, then have the author fight over their definition. But the statement:
plot sales.volume,sales.price;
Works, because simple syntax can expand the sql style table.column reference. The authors document can require a get sales.csv;

We are talking about a command line for authors, based on the persistent table model.