-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/10/2015 01:51 PM, Simon Slavin wrote: > With a cursory glance I do see important incompatibilities with > SQLite.
I use JSON as the data format for $work stuff (startups) for years, and these JSON schemas etc miss why some of us use JSON. If you are using a statically typed language like Java or C++, then arbitrary data is very difficult to deal with. XML is very popular in that world because DTDs mean you can make it statically typed. The mindset is that if everything can be specified and constrained in advance, then successfully compiling the code means it is mostly correct. JSON like several other languages (eg Python, Ruby) is dynamically typed. You can stick anything you want in variables/fields, since the type is associated with the value, not the variable name. This allows for far greater flexibility, and especially means you do not have to decide in advance exactly what you will do with data. Dealing with XML is a huge pain! Code is trivial to deal with whatever you get. Importing code does not mean it is correct - running it is how you figure that out. These schema and similar efforts seem to be an exercise in getting the worst of all worlds, combining rigid languages with flexible data by trying to make the data inflexible. Use the right tool for the job. It is also why this and efforts like unsql don't take off - they are bandaids for a mindset being applied in the wrong place. /rant Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUoPX8ACgkQmOOfHg372QSywwCfbHzpZxiOz+/D3wO2UgbbNuMS YGYAniyVNFM9I9JIX2H6Mi9yuiIYV6Np =1ZX9 -----END PGP SIGNATURE-----
