Skip to main content
Service phase: Beta

This service is still in development. Give us your feedback or view this page on the current PRONOM service.

Format

DROID File Collection File Format

Summary

Name
DROID File Collection File Format
Version
1.0
Identifiers
  • PUID: fmt/120
  • MIME: text/xml
Format type
Text (Mark-up)
Disclosure
Full
Description
The DROID File Collection File format is a format for storing the results of file format identifications generated by the DROID software tool. It was developed by The National Archives of the UK. A DROID File Collection File is an XML document, comprising a 'FileCollection' element, which describes the version of DROID and Signature File version number used to perform the identifications number, and date on which the identifications were generated. This element contains a 'File' element for each file being identified. A File Collection File may either be generated prior to identification, in which case each 'File' element simply contains the fully-qualified pathname of the file, or it can be generated after identification, in which case each 'File' element additionally contains the identification result.
File extensions
xml
Source
Digital Preservation Department / The National Archives
Developed by
Digital Preservation Department / The National Archives

Relationships

Has priority over

Internal signatures

DROID File Collection File

Note
<FileCollection>…<DROIDVersion> elements. {0-50} < F I l e C o l l e c t I o n {0-100} < D R O I D V e r s I o n > {1-10} < / D R O I D V e r s I o n > - NB. The signature byte sequence is currently massaged to steer around the known PRONOM bug in the are of the left fragment matching when the longest fragment is not nearest BOF. The last fragment in the BOF byte sequence has been shortened by 2 bytes to ensure that the first fragment is the longest. This abbreviation does not reduce the overall signature strength too much and so will hopefully not result in any false positive identification. When the PRONOM bug has been fixed, "0D0A" should be appended to the BOF byte sequence and this note reduced.

Byte sequences

Min Frag Length
Absolute from BOF
Offset
0
Max offset
None
Byte Sequence
{0-50}3C46696C65436F6C6C656374696F6E20{0-100}3C44524F494456657273696F6E3E{1-10}3C2F44524F494456657273696F6E3E
Endianness
None

Changelog

  • Added in V34

    Release date
    2 April 2010

    DROID File Collection File Format: Signature improved through DROID 5.0 research