All in all it is clear that this kind of a protocol and notation, is much more forgiving than SQL. The syntax is well known, powerful and simple in the same time. Because this is just JavaScript.  In the same time, opposite of SQL, DBJSON is message “packaging” protocol, allowing for unlimited nesting, presence of functions, etc. Great care was taken to make all of this flexibility available but still not wildly foreign to standard relational databases, and their users.

At the end of the day, DBJSON protocol is a question of a contract between message sender and message consumer.

The whole web applications community will have to make an effort to decide and standardize on one single and consistent DBJSON protocol specification. In the same time carefully avoiding to fall into the “jack of all trades” trap, DBJSON must not become “a little bit for everyone, but not enough for anyone”.

Further Reading

Mapping Between JSON and XML:  http ://msdn.microsoft.com/en-us/library/bb924435.aspx

DBJSON(tm) idea is by no means finished. I am working on it right now.

(c) 2009-2012-2016 by DusanB. Jovanovic

1: That is not true. The MIME media type for JSON text is application/json . The default encoding is UTF-8. (Source: RFC 4627). RFC 4627 — The application/json Media Type for JavaScript Object Notation (JSON)

6 thoughts on “DBJSON: SELECT * FROM persons AS JSON”

Comments are closed.