From story time meeting on 03-17:
* Different use casesses for JSON format version info: API, dump-files, Special:EntityData.
Idea by @daniel and @adrianheine:
** Special:EntityData and API: we could put the version Having generic mechanism for a meta-info in the same place as we have the reviheader that contains version(s) info (revision ID), license info, etc..
** dump-files: skip that for nowFor each of the use cases outlined above, the meta-info would go to a specific location:
** there should be a separate task for having that info in the database (we will not do it for now)
Idea by @daniel and @adrianheine: Special:EntityData would have it inlined
* API responses would have it side by side with the entity info
having a header for meta-info that contains v* JSON dump files would be accompanied by a separate .meta.json file
NOTE: Version(s) infoning of the *model* (DataValue, licence info,Wikibase) is separate for the versioning of the *serialization*. etc..Ideally, and put it into a separate file for dumps
@daniel can you describe this idea a bit more in detail?our meta-data would contain both.
NOTE: There should be a separate task for having JSON version info in the database (we will not do it for now).