I conjecture that error detection (and recovery) are layers beneath the file format it's self. They belong in the filing system and storage layers within/under that.
Application code should never need to worry about error recovery.
We're kind of close to this for text files, if only Windows and related programs would join the rest of the sane world. Stop adding 'BOM Marks' and just assume everything is UTF-8 (at least for any txt file created after 2000 and all application stdin/out/errs).
However the biggest barrier here is a complete disconnect between interested parties. Adobe wants to make money and keeps 'pdf' locked away. It's also bad because paper size is enforced, instead of having an aspect ratio, and positioning for different elements. Even HTML rendering isn't that simple, and NO designer is working using those tools. Additionally that complexity is FAR above what the average user can handle and WAY above what they want to deal with even if they can.
Any format which /is/ user friendly will have to support things like 'drawings' / sketches which may or may not be auto OCRed for searching.
I'm of the opinion that this won't really be solved until we have //strong// AI to do transcription and formatting for the lazy humans.