Most of the Person records returned by the API contain an also_known_as array field with one member for each alias of the person represented by the record. But that's not always what comes back. In the case of record 100196 (Gary Brooker), for example, there is a single member appearing in the array with dozens of aliases in that one array member, for a total of 559 characters (including a superfluous leading space). Are there any length constraints for the name values in this array which would prevent this from happening? Or is consuming software expected to deal with such denormalized storage of the person aliases?

Also, if there's a better place to report problems with the API, please let me know.