What should this machine to to adopt those?
1) Make TE syntax compatible with JSON
2) Find a mapping between BSON and triplet: <key.<link><pointer>
whrere BSON types are overloading attributes on the link field,
and BSON sequences may have free expression with the pointer, for local pointing.
3) Build the schema operator around BSON types, perhaps merge the bson overloads with the schema and attribute operators.
4) Use bson triplets to define graph variables which may be altered.
5) Find packages with bson methods that we can incorporate.
6) Finally, grab onto those bson attribute names, double, string, etc. Add table,url to the list and make them reserved words.
Basically, the externally formatted bson, take that approach, the bson community will have to adopt some external field approach anyway.
No comments:
Post a Comment