search

mets / METS-board

Documents and wiki pages relevant to the business of the METS Editorial Board
14 stars 6 forks source link

Clarify diskmount TRANSFORMTYPE with Jerry #1

Closed thabing closed 10 years ago

thabing commented 11 years ago

Sent a not to Jerry asking whether relying on a <file MIMETYPE=”application/x-iso9660-image” … > attribute would solve his use case or not.

thabing commented 10 years ago

Rejected by the METS Board with this alternative:

The METS Board met last week and, among other things, discussed your request for the disk mount transformation. There was some discussion of whether a disk mount should be considered a transformation or whether it was really more akin to any other “application” able to “render” a file type, with the appropriate renderer chosen based on the MIMETYPE. For example, you could represent your ISO file like this:

<file MIMETYPE=”application/x-iso9660-image” … > <FLocat … />

And the MIMETYPE would be enough for a processing system to know that the file needed to be mounted and treated as a disk image for it to be useful.

Unfortunately, there seem to be several competing MIME types, and they all are of the “x-“ nonstandard type:

application/x-iso9660-image application/x-iso-image application/x-cd-image application/x-raw-disk-image

The application/x-iso9660-image seems to be the most common, with it appearing on the digitalpreservation.gov web page: http://www.digitalpreservation.gov/formats/fdd/fdd000348.shtml.

The application/x-apple-diskimage also appears frequently for Apple disk images.

Would this type of solution which relies on the MIMETYPE meet your needs, or is there some other use case that you had in mind that would require the “diskmount” transformation?