thanks for your suggestions! I recommend to make use of the JSON datatypes (see http://json.org/) and not just export everything as string or as an array. For example, numerical values should be exported as numbers (no quotes) and boolean values (e.g. flash used?) as true/false. Maybe also fractional values such as shutter speed could be exported as numbers.
This ensures that JSON parsers in other languages can automatically convert the value to the correct datatype.
I really appreciate that there will be a "flat" (-G1) and a "nested" (-g1) JSON structure, which should also the data access.
yes, it's definitely a good idea to emit a JSON array even when just one image is read. This ensures the programmer can use the same logic (array iteration) to process a single or multifile-output.
About the boolean values: here we are in an old dilemma - do we want the value to be "queryable" in a database (then boolean values/enumerated constants would be a better option) or "presentable" to an enduser (this means to provide meaningful translations of the values).
I see this problem in a bigger context (also with the recent translation efforts). I think it's to early to definitely decide on it. For now, just implement JSON support in your way... I'm sure sooner or later there will be suggestions to refine it with additional export options.- Franz
Wow, 7.65 comes with JSON support. Thanks a lot. :)
About something I'm wondering: Why is not the uppercase letter -J taken for the output format like -T or -X?
Regards, Jan Friedrich