what info should a dsk image archive store?

[jonnosan <jonnosan@gmail.com>]

Following on from topics touched on in '"Ideas for a new A2 site",
I've been thinking about what sort of info a good archive would store
about each disk image.

What I have in mind is a zip file or equivalent that contains one or
more dsk/po/nib images, along with metadata and other relevant
material (e.g. screen shots,  scans of box covers & manuals, soft
dox).

Ideally this format would be:
- easy for a user to put together offline (either by hand or with the
help of an application)
- easy for an online archive to import

Data stored should include data needed to add to a browsable catalogue
of images. For commercial applications, that information will include:
- Application Name
- Application Publisher
- Application Author(s) (if known)
- Year of publication
- Application Category (needs to have some kind of constrained and
structured list of categories e.g. "Applications/Word Processor"
"Games/Arcade"

Since most images for commercial applications will be cracks, other
interesting information to record is:
- how 'clean' a crack is it? not sure how to quantify this - at one
extreme are disks that were COPYAble just by disabling checksum
validation, at the other extreme would be a pirate production with a
custom menu and a bunch of disparate games with trainers.
- what type of protection was used?
- what group/cracker released the disk?

What else should be captured?

Have collectors on other platforms already addressed this same issue?