<?xml version="1.0" encoding="utf-8"?>
<PRONOM-Report xmlns="http://pronom.nationalarchives.gov.uk">
  <report_format_detail>
    <FileFormat>
      <FormatID>769</FormatID>
      <FormatName>DROID File Collection File Format</FormatName>
      <FormatVersion>1.0</FormatVersion>
      <FormatAliases>
      </FormatAliases>
      <FormatFamilies>
      </FormatFamilies>
      <FormatTypes>Text (Mark-up)</FormatTypes>
      <FormatDisclosure>Full</FormatDisclosure>
      <FormatDescription>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.</FormatDescription>
      <BinaryFileFormat>Text</BinaryFileFormat>
      <ByteOrders>
      </ByteOrders>
      <ReleaseDate>17 Sep 2005</ReleaseDate>
      <WithdrawnDate>
      </WithdrawnDate>
      <ProvenanceSourceID>1</ProvenanceSourceID>
      <ProvenanceName>Digital Preservation Department / The National Archives</ProvenanceName>
      <ProvenanceSourceDate>11 Oct 2005</ProvenanceSourceDate>
      <ProvenanceDescription>
      </ProvenanceDescription>
      <LastUpdatedDate>11 Oct 2005</LastUpdatedDate>
      <FormatNote>
      </FormatNote>
      <FormatRisk>
      </FormatRisk>
      <TechnicalEnvironment>
      </TechnicalEnvironment>
      <FileFormatIdentifier>
        <Identifier>fmt/120</Identifier>
        <IdentifierType>PUID</IdentifierType>
      </FileFormatIdentifier>
      <FileFormatIdentifier>
        <Identifier>text/xml</Identifier>
        <IdentifierType>MIME</IdentifierType>
      </FileFormatIdentifier>
      <Developers>
        <DeveloperID>1</DeveloperID>
        <DeveloperName>Digital Preservation Department</DeveloperName>
        <OrganisationName>The National Archives</OrganisationName>
        <DeveloperCompoundName>Digital Preservation Department / The National Archives</DeveloperCompoundName>
      </Developers>
      <Document>
        <DocumentID>64</DocumentID>
        <DisplayText>Brown, A, 2005, Automatic format identification using PRONOM and DROID, Digital Preservation Technical Paper, 1, The National Archives</DisplayText>
        <DocumentType>Authoritative</DocumentType>
        <AvailabilityDescription>Public</AvailabilityDescription>
        <AvailabilityNote>
        </AvailabilityNote>
        <PublicationDate>17 Sep 2005</PublicationDate>
        <TitleText>Automatic format identification using PRONOM and DROID</TitleText>
        <DocumentIPR>
        </DocumentIPR>
        <DocumentNote>
        </DocumentNote>
        <DocumentIdentifier>
          <Identifier>www.nationalarchives.gov.uk/aboutapps/fileformat/pdf/automatic_format_identification.pdf</Identifier>
          <IdentifierType>URL</IdentifierType>
        </DocumentIdentifier>
      </Document>
      <ExternalSignature>
        <ExternalSignatureID>765</ExternalSignatureID>
        <Signature>xml</Signature>
        <SignatureType>File extension</SignatureType>
      </ExternalSignature>
      <InternalSignature>
        <SignatureID>176</SignatureID>
        <SignatureName>DROID File Collection File</SignatureName>
        <SignatureNote>&lt;FileCollection&gt;…&lt;DROIDVersion&gt; elements. {0-50} &lt; F I l e C o l l e c t I o n  {0-100} &lt; D R O I D V e r s I o n &gt; {1-10} &lt; / D R O I D V e r s I o n &gt; - 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.</SignatureNote>
        <ByteSequence>
          <ByteSequenceID>209</ByteSequenceID>
          <PositionType>Absolute from BOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>
          </MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>{0-50}3C46696C65436F6C6C656374696F6E20{0-100}3C44524F494456657273696F6E3E{1-10}3C2F44524F494456657273696F6E3E</ByteSequenceValue>
        </ByteSequence>
      </InternalSignature>
      <RelatedFormat>
        <RelationshipType>Has priority over</RelationshipType>
        <RelatedFormatID>638</RelatedFormatID>
        <RelatedFormatName>Extensible Markup Language</RelatedFormatName>
        <RelatedFormatVersion>1.0</RelatedFormatVersion>
      </RelatedFormat>
    </FileFormat>
    <SearchCriteria>Criteria</SearchCriteria>
  </report_format_detail>
</PRONOM-Report>
