<?xml version="1.0" encoding="utf-8"?>
<PRONOM-Report xmlns="http://pronom.nationalarchives.gov.uk">
  <report_format_detail>
    <FileFormat>
      <FormatID>2129</FormatID>
      <FormatName>Tweet JSON</FormatName>
      <FormatVersion>
      </FormatVersion>
      <FormatAliases>
      </FormatAliases>
      <FormatFamilies>
      </FormatFamilies>
      <FormatTypes>Text (Mark-up)</FormatTypes>
      <FormatDisclosure>
      </FormatDisclosure>
      <FormatDescription>Tweet JSON represents the serialization of the JSON response payload of the Twitter API when requesting a single Tweet by id. Each Tweet has an author, a message, a unique ID, a timestamp of when it was posted, and sometimes geo metadata shared by the user.
Each Tweet also has "entity" objects, which are arrays of common Tweet contents such as hashtags, mentions, media, and links. If there are links, the JSON payload can also provide metadata such as the fully unwound URL and the webpage’s title and description.
In addition to the text content itself, a Tweet can have over 150 attributes associated with it.</FormatDescription>
      <BinaryFileFormat>
      </BinaryFileFormat>
      <ByteOrders>
      </ByteOrders>
      <ReleaseDate>
      </ReleaseDate>
      <WithdrawnDate>
      </WithdrawnDate>
      <ProvenanceSourceID>244</ProvenanceSourceID>
      <ProvenanceName>Preservica / Preservica</ProvenanceName>
      <ProvenanceSourceDate>18 Jan 2020</ProvenanceSourceDate>
      <ProvenanceDescription>
      </ProvenanceDescription>
      <LastUpdatedDate>18 Jan 2020</LastUpdatedDate>
      <FormatNote>
      </FormatNote>
      <FormatRisk>
      </FormatRisk>
      <TechnicalEnvironment>
      </TechnicalEnvironment>
      <FileFormatIdentifier>
        <Identifier>application/json</Identifier>
        <IdentifierType>MIME</IdentifierType>
      </FileFormatIdentifier>
      <FileFormatIdentifier>
        <Identifier>fmt/1311</Identifier>
        <IdentifierType>PUID</IdentifierType>
      </FileFormatIdentifier>
      <ExternalSignature>
        <ExternalSignatureID>2421</ExternalSignatureID>
        <Signature>json</Signature>
        <SignatureType>File extension</SignatureType>
      </ExternalSignature>
      <InternalSignature>
        <SignatureID>1687</SignatureID>
        <SignatureName>Tweet JSON (Raw JSON)</SignatureName>
        <SignatureNote>The signature assumes a starting "{" character, a terminating "}" and the JSON keys "id_str" and "retweeted". This matches the raw JSON string with no line breaks.</SignatureNote>
        <ByteSequence>
          <ByteSequenceID>1955</ByteSequenceID>
          <PositionType>Absolute from BOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7B*2269645F737472223A*22726574776565746564223A</ByteSequenceValue>
        </ByteSequence>
        <ByteSequence>
          <ByteSequenceID>1956</ByteSequenceID>
          <PositionType>Absolute from EOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7D0A</ByteSequenceValue>
        </ByteSequence>
      </InternalSignature>
      <InternalSignature>
        <SignatureID>1688</SignatureID>
        <SignatureName>Tweet JSON (Linux)</SignatureName>
        <SignatureNote>The signature assumes a starting "{" character, a terminating "}" and the JSON keys "id_str" and "retweeted". This matches a serialization with a new line at the end of the file in linux line-endings.</SignatureNote>
        <ByteSequence>
          <ByteSequenceID>1957</ByteSequenceID>
          <PositionType>Absolute from BOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7B*2269645F737472223A*22726574776565746564223A</ByteSequenceValue>
        </ByteSequence>
        <ByteSequence>
          <ByteSequenceID>1958</ByteSequenceID>
          <PositionType>Absolute from EOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7D</ByteSequenceValue>
        </ByteSequence>
      </InternalSignature>
      <InternalSignature>
        <SignatureID>1689</SignatureID>
        <SignatureName>Tweet JSON (Windows)</SignatureName>
        <SignatureNote>The signature assumes a starting "{" character, a terminating "}" and the JSON keys "id_str" and "retweeted". This signature matches the same with a windows line-ending.</SignatureNote>
        <ByteSequence>
          <ByteSequenceID>1959</ByteSequenceID>
          <PositionType>Absolute from BOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7B*2269645F737472223A*22726574776565746564223A</ByteSequenceValue>
        </ByteSequence>
        <ByteSequence>
          <ByteSequenceID>1960</ByteSequenceID>
          <PositionType>Absolute from EOF</PositionType>
          <Offset>0</Offset>
          <MaxOffset>0</MaxOffset>
          <IndirectOffsetLocation>
          </IndirectOffsetLocation>
          <IndirectOffsetLength>
          </IndirectOffsetLength>
          <Endianness>
          </Endianness>
          <ByteSequenceValue>7D0D0A</ByteSequenceValue>
        </ByteSequence>
      </InternalSignature>
      <RelatedFormat>
        <RelationshipType>Has priority over</RelationshipType>
        <RelatedFormatID>1617</RelatedFormatID>
        <RelatedFormatName>JSON Data Interchange Format</RelatedFormatName>
        <RelatedFormatVersion>
        </RelatedFormatVersion>
      </RelatedFormat>
    </FileFormat>
    <SearchCriteria>Criteria</SearchCriteria>
  </report_format_detail>
</PRONOM-Report>
