digital-preservation / droid

DROID (Digital Record and Object Identification)
BSD 3-Clause "New" or "Revised" License
278 stars 75 forks source link

Likely malformed container signature data #923

Open CharlotteZed opened 1 year ago

CharlotteZed commented 1 year ago

Internal signatures with IDs 39511 and 39516 (both corresponding to fmt/1342) are the only two signatures which have a BinarySignatures element nested directly under the Files element instead of inside of a parent File element. The formatting on the XML itself around these in the file served here and at https://www.nationalarchives.gov.uk/aboutapps/pronom/droid-signature-files.htm do suggest that this is erroneous as well.

Attached here is a screenshot of a prettified copy of the same xml in question, where the odd BinarySignature elements are easy to see. image

Since each of these occurrences is also preceded by a file element with a path but no binary signatures, it seems like the BinarySignatures are meant to be nested under their direct predecessors as in this screenshot:

image

Dclipsham commented 1 year ago

I've posted a corrected Container Signature file in #924