Sure, it's the outcome of parsing, but the outcome of the truncation is present in the message as well (missing fields), so I don't think that it's a long stretch to envision that as part of the message. But sure, if you think that it is a more elegant solution to wrap the message in an outer object holding information about truncation, by all means keep the current setup.