philipashlock
commented
9 years ago I think this is an artifact of initially modeling things in XML and wanting the structure of responses to be consistent whether there was one or many objects returned. We then decided that the JSON variant would be directly mapped to this XML structure which means that responses that only have one object are still returned as an array.
A future version of the spec could take this into consideration more and perhaps drop support for XML altogether.
There are some calls that confused me during modelling the spec, as (to me) it seems strange that they seem to realize an array / 1:n relation