Let the user work from his own and a suggested set finite set of names. He can construct his personal world with a name list, bookmarks, email addresses, a mails, gists and notes, working documents, etc etc. As many names as the user wants,files; they become unique indices into his information storage. Give the client a tool to manage his name space, then from then on, it is dra and drop, tag, any documents can be pointed to from one of the names in his name space. He can nest his name space, do anything with the name space that can be represented in a Json string.
Fro the engine's point of view, is is just another Qson table, but we create the indexed attribute on this table, we know wight away on look up that this is client name space. Any element named with a naming element will be tagged as a member of that set of elements. Then using the client name space, the power of Sqlite3 becomes a natural Json breeze.
On start of a run, the client's name space (or part of it) into the qsort/bsearh symbol table in ram. Access to the subgraph elements of a tagged graph, not a problem when we have rowids and table names That is what I can work on, and let the Json/browser technology proceed on its own.
What would a bookmark list look like in Lazy J?
Bookmark.{title1.url1.icon1.ip1,table2.url2.icon2.ip2, ..,}
So when running this table, the default here is that bookmark is a valid symbol, the engine looks it up. But Bookmark:{NewTitle.UrlNew.IconNew.IP} means to add this to the bookmark subgraph.
So the engine looks up the first item in an expression and is directed from there, but the engine executes a subgraph append if the object is Colonized? I am getting close here, close to something that might work as a tryout.
No comments:
Post a Comment