In the syntax, we have to have overloads?
table$MyTable.key1.key2...
Dunno, getting beyond my paygrade. But, I would think, table are intrinsic to the triple streams from the engine. But maybe not all tables are SQL in the long run?
How to we distinguish between a remote table and a local table? The URL overload?
url$(www.sometable.com)
Naw, too hokey. Dunno? Another reason I am hesitant to proceed knowing much of this is sorted by industry consensus. However, I do think local tables attributes should be merged with the SQLITE3 master table. Not a plan, just throwing that out.
One thing might be to key on the first TE word by custom, it is automatically a locator.
Still waiting to hear what happens beyond that stupid SPARQL thingie.
No comments:
Post a Comment