Due to what I assume are compatibility issues, the JSON ws/2 returns things in somewhat unusual ways. For example, https://musicbrainz.org/ws/2/release/c62d1506-9e8c-447c-88de-e3feee7da8ae?fmt=json has

{... "packaging-id":"119eba76-b343-3e02-a292-f0f00644bb9b", ..., "packaging":"None" ...}.

It would be much more sensible to provide this as {... "packaging": {"id":"119eba76-b343-3e02-a292-f0f00644bb9b", "name":"None"} ...}. The same applies to many other ids and to things like attribute values, which are stored as { "attribute-values": { "attributename": "value } } rather than as part of an attribute object each.