From story time meeting on 03-17:
Different use cases for JSON format version info: API, dump-files, Special:EntityData.
Idea by @daniel and @adrianheine:
Having generic mechanism for a meta-info header that contains version(s) info, license info, etc..
For each of the use cases outlined above, the meta-info would go to a specific location:
- Special:EntityData would have it inlined
- API responses would have it side by side with the entity info
- JSON dump files would be accompanied by a separate .meta.json file