JSON Format (i.e. database padding)

[GoogleCodeExporter]

1. add database padding so multiple databases can be used in JSON
2. allow singleton form?
   1. especially for query syntax, makes it easier to write
   2. promote object to array on second addition, demote single element
array to object
   3. consistency maybe more import for query results, harder to handle if
multiple formats
   4. generous input, parsimonious output
3. should type be field name with object value, or object with name as member?
   1. i.e. [{“query_name”: {...query parameters…} }, {...} ] or [{“query”:
query_name, ...query parameters…}, {...}]
   2. dollar is valid name in JSON, so {”$”: query_name, ...query parameters}
   3. names should also be legal in XML, or at least matching structure
               1. e.g. —> {”$”: query_name, “parm_1”: 1}
4. where does metadata go?
   1. rule says it should be replicated at widget
   2. no mgmt of common stores

Original issue reported on code.google.com by dbsha...@gmail.com on 24 Sep 2009 at 9:00

[GoogleCodeExporter]

- added database padding to JSON output
- no singleton form (don't want complexity of supporting two formats)
- use query name
- metadata is orthogonal, client manages

Original comment by dbsha...@gmail.com on 30 Sep 2009 at 1:09

• Changed state: Fixed