Toby,
One thing to consider is how the format deals with
damage....
Good thought. I wonder if that integrity functional role could be delegated
to the container format rather than the payload element. The payload
doesn't get internally marked up with checksum blocks, but we rely on
LZW/LZW2/other as the guarantor of file integrity. The rest of the
scavenging is done by the metadata/descriptor element (like card 1 = byte
[xxx]-byte[yyy]). Any damage or ambiguity is noted in this external
metadata rather than the actual capture blob. The container ensures that
the integrity of the contents are the same as when they were created. The
descriptor describes what was known at creation time. Workable?
Regards,
Colin Eby