Last modified: 2014-11-13 11:29:18 UTC
when requesting wbgetentities with the languagefallback param, in xml format: https://www.wikidata.org/w/api.php?action=wbgetentities&ids=Q42&languages=ii&languagefallback= vs. in json format: https://www.wikidata.org/w/api.php?action=wbgetentities&ids=Q42&languages=ii&format=json&languagefallback= xml has 'for-language' like: <label language="zh-cn" value="道格拉斯·亚当斯" for-language="ii" /> json format seems to be missing it.
In JSON, this is represented by the label's key being different from the value of the language field. I agree that it would be nicer to have this modelled explicitly as a separate for-language field. Note that in cases where translitteration applied, there may be a third language involved (the "original" or "database" language).
Perhaps also make sure the naming in xml and json is the same.
