home.social

#fileformats — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fileformats, aggregated by home.social.

  1. Maintenance begins at creation, so why are we not creating better?

    by @beet_keeper

    The beats are the same. You work for government, or academia (lets face it, that’s probably where 90% of the work is) you have a deliverable; you save it; you print to PDF; you store it on an institutional repository with some metadata (or Zenodo, OSF or equivalent) and its done.

    There’s a small chance that it’s FAIR (Findable, Accessible, Interoperable, Reusable) right? It has metadata that can be discovered by an audience looking for it and can be indexed by search engines. The data is potentially accessible if published correctly. They’re not particularly interoperable or easily converted, and PDFs aren’t really designed for reuse, even if tools like Apache Tika help ease the burden of extracting artifacts. It’s just a PDF, why are we even talking about FAIR? There begins a story…

    The beats are the same, yet, we work in digital preservation, our backgrounds are in GLAM or software, why do we want to shoot ourselves in the foot? Why are we not using our skills to create better?


    #Archives #BetterPoster #ContinuumModel #createToMaintain #digipres #DigitalArchiving #DigitalContunuity #digitalLiteracy #DigitalPreservation #FAIR #FileFormats #GLAM #informationRecordsMangagement #NationalDigitalStewardshipAlliance #NDSA #OpenAccess #OpenData #PDF #RDM #ResearchDataLifecycle #RIM
  2. Maintenance begins at creation, so why are we not creating better?

    by @beet_keeper

    The beats are the same. You work for government, or academia (lets face it, that’s probably where 90% of the work is) you have a deliverable; you save it; you print to PDF; you store it on an institutional repository with some metadata (or Zenodo, OSF or equivalent) and its done.

    There’s a small chance that it’s FAIR (Findable, Accessible, Interoperable, Reusable) right? It has metadata that can be discovered by an audience looking for it and can be indexed by search engines. The data is potentially accessible if published correctly. They’re not particularly interoperable or easily converted, and PDFs aren’t really designed for reuse, even if tools like Apache Tika help ease the burden of extracting artifacts. It’s just a PDF, why are we even talking about FAIR? There begins a story…

    The beats are the same, yet, we work in digital preservation, our backgrounds are in GLAM or software, why do we want to shoot ourselves in the foot? Why are we not using our skills to create better?

    Continue reading “Maintenance begins at creation, so why are we not creating better?”


    #Archives #BetterPoster #ContinuumModel #createToMaintain #digipres #DigitalArchiving #DigitalContunuity #digitalLiteracy #DigitalPreservation #FAIR #FileFormats #GLAM #informationRecordsMangagement #NationalDigitalStewardshipAlliance #NDSA #OpenAccess #OpenData #PDF #RDM #ResearchDataLifecycle #RIM
  3. Maintenance begins at creation, so why are we not creating better?

    by @beet_keeper

    The beats are the same. You work for government, or academia (lets face it, that’s probably where 90% of the work is) you have a deliverable; you save it; you print to PDF; you store it on an institutional repository with some metadata (or Zenodo, OSF or equivalent) and its done.

    There’s a small chance that it’s FAIR (Findable, Accessible, Interoperable, Reusable) right? It has metadata that can be discovered by an audience looking for it and can be indexed by search engines. The data is potentially accessible if published correctly. They’re not particularly interoperable or easily converted, and PDFs aren’t really designed for reuse, even if tools like Apache Tika help ease the burden of extracting artifacts. It’s just a PDF, why are we even talking about FAIR? There begins a story…

    The beats are the same, yet, we work in digital preservation, our backgrounds are in GLAM or software, why do we want to shoot ourselves in the foot? Why are we not using our skills to create better?


    #Archives #ContinuumModel #createToMaintain #digipres #DigitalArchiving #DigitalContunuity #digitalLiteracy #DigitalPreservation #FAIR #FileFormats #GLAM #informationRecordsMangagement #NationalDigitalStewardshipAlliance #NDSA #OpenData #PDF #RDM #ResearchDataLifecycle #RIM
  4. Maintenance begins at creation, so why are we not creating better?

    by @beet_keeper

    The beats are the same. You work for government, or academia (lets face it, that’s probably where 90% of the work is) you have a deliverable; you save it; you print to PDF; you store it on an institutional repository with some metadata (or Zenodo, OSF or equivalent) and its done.

    There’s a small chance that it’s FAIR (Findable, Accessible, Interoperable, Reusable) right? It has metadata that can be discovered by an audience looking for it and can be indexed by search engines. The data is potentially accessible if published correctly. They’re not particularly interoperable or easily converted, and PDFs aren’t really designed for reuse, even if tools like Apache Tika help ease the burden of extracting artifacts. It’s just a PDF, why are we even talking about FAIR? There begins a story…

    The beats are the same, yet, we work in digital preservation, our backgrounds are in GLAM or software, why do we want to shoot ourselves in the foot? Why are we not using our skills to create better?


    #Archives #ContinuumModel #createToMaintain #digipres #DigitalArchiving #DigitalContunuity #digitalLiteracy #DigitalPreservation #FAIR #FileFormats #GLAM #informationRecordsMangagement #NationalDigitalStewardshipAlliance #NDSA #OpenData #PDF #RDM #ResearchDataLifecycle #RIM
  5. Maintenance begins at creation, so why are we not creating better?

    by @beet_keeper

    The beats are the same. You work for government, or academia (lets face it, that’s probably where 90% of the work is) you have a deliverable; you save it; you print to PDF; you store it on an institutional repository with some metadata (or Zenodo, OSF or equivalent) and its done.

    There’s a small chance that it’s FAIR (Findable, Accessible, Interoperable, Reusable) right? It has metadata that can be discovered by an audience looking for it and can be indexed by search engines. The data is potentially accessible if published correctly. They’re not particularly interoperable or easily converted, and PDFs aren’t really designed for reuse, even if tools like Apache Tika help ease the burden of extracting artifacts. It’s just a PDF, why are we even talking about FAIR? There begins a story…

    The beats are the same, yet, we work in digital preservation, our backgrounds are in GLAM or software, why do we want to shoot ourselves in the foot? Why are we not using our skills to create better?


    #Archives #BetterPoster #ContinuumModel #createToMaintain #digipres #DigitalArchiving #DigitalContunuity #digitalLiteracy #DigitalPreservation #FAIR #FileFormats #GLAM #informationRecordsMangagement #NationalDigitalStewardshipAlliance #NDSA #OpenAccess #OpenData #PDF #RDM #ResearchDataLifecycle #RIM
  6. Hot take on digital sovereignty of #fileformats #digipres "A license tells you who owns the software, while the format tells you who owns the data", "Digital sovereignty is not achieved by changing who hosts the software, but by changing the format in which data is encoded." blog.documentfoundation.org/bl

  7. Do you think custom text file formats are a good idea? or should we just always use JSON/YAML/TOML?

    #programming #plaintext #fileformats

  8. ✨Bringing light to #FileFormats

    Tough on the outside with food for thought inside!
    File formats reveal a lot about the different meanings of an object.
    CPP-008 and CPP-010 help you uncover them through #FileFormatIdentification and #FileFormatValidation:
    tiny.cc/cpp-desc

    #EOSCEDEN #CPPs #digitalpreservation #FAIRdata

  9. ✨Bringing light to #FileFormats

    Tough on the outside with food for thought inside!
    File formats reveal a lot about the different meanings of an object.
    CPP-008 and CPP-010 help you uncover them through #FileFormatIdentification and #FileFormatValidation:
    tiny.cc/cpp-desc

    #EOSCEDEN #CPPs #digitalpreservation #FAIRdata

  10. ✨Bringing light to #FileFormats

    Tough on the outside with food for thought inside!
    File formats reveal a lot about the different meanings of an object.
    CPP-008 and CPP-010 help you uncover them through #FileFormatIdentification and #FileFormatValidation:
    tiny.cc/cpp-desc

    #EOSCEDEN #CPPs #digitalpreservation #FAIRdata

  11. ✨Bringing light to #FileFormats

    Tough on the outside with food for thought inside!
    File formats reveal a lot about the different meanings of an object.
    CPP-008 and CPP-010 help you uncover them through #FileFormatIdentification and #FileFormatValidation:
    tiny.cc/cpp-desc

    #EOSCEDEN #CPPs #digitalpreservation #FAIRdata

  12. ✨Bringing light to #FileFormats

    Tough on the outside with food for thought inside!
    File formats reveal a lot about the different meanings of an object.
    CPP-008 and CPP-010 help you uncover them through #FileFormatIdentification and #FileFormatValidation:
    tiny.cc/cpp-desc

    #EOSCEDEN #CPPs #digitalpreservation #FAIRdata

  13. Sure, we've all seen Mark YAML and even JSON Statham, but have y'all met TOML Holland yet?

    #DadJokes #TomHolland #TOML #JSON #YAML #FileFormats

  14. Sure, we've all seen Mark YAML and even JSON Statham, but have y'all met TOML Holland yet?

    #DadJokes #TomHolland #TOML #JSON #YAML #FileFormats

  15. Sure, we've all seen Mark YAML and even JSON Statham, but have y'all met TOML Holland yet?

    #DadJokes #TomHolland #TOML #JSON #YAML #FileFormats

  16. Sure, we've all seen Mark YAML and even JSON Statham, but have y'all met TOML Holland yet?

    #DadJokes #TomHolland #TOML #JSON #YAML #FileFormats

  17. Sure, we've all seen Mark YAML and even JSON Statham, but have y'all met TOML Holland yet?

    #DadJokes #TomHolland #TOML #JSON #YAML #FileFormats

  18. Ah, the "Binary Formats Gallery"—because what the world really needed was a #museum for file formats, complete with GraphViz diagrams and hex dump visualizers! 🤓🖥️ I mean, who doesn't want to spend their Sunday afternoon compiling Kaitai Struct libraries just to admire the metadata of a Quake 2 model? 🌟🔍
    formats.kaitai.io/ #BinaryFormatsGallery #FileFormats #TechArt #KaitaiStruct #Quake2 #HackerNews #ngated

  19. Ah, the "Binary Formats Gallery"—because what the world really needed was a #museum for file formats, complete with GraphViz diagrams and hex dump visualizers! 🤓🖥️ I mean, who doesn't want to spend their Sunday afternoon compiling Kaitai Struct libraries just to admire the metadata of a Quake 2 model? 🌟🔍
    formats.kaitai.io/ #BinaryFormatsGallery #FileFormats #TechArt #KaitaiStruct #Quake2 #HackerNews #ngated

  20. Ah, the "Binary Formats Gallery"—because what the world really needed was a #museum for file formats, complete with GraphViz diagrams and hex dump visualizers! 🤓🖥️ I mean, who doesn't want to spend their Sunday afternoon compiling Kaitai Struct libraries just to admire the metadata of a Quake 2 model? 🌟🔍
    formats.kaitai.io/ #BinaryFormatsGallery #FileFormats #TechArt #KaitaiStruct #Quake2 #HackerNews #ngated

  21. Ah, the "Binary Formats Gallery"—because what the world really needed was a #museum for file formats, complete with GraphViz diagrams and hex dump visualizers! 🤓🖥️ I mean, who doesn't want to spend their Sunday afternoon compiling Kaitai Struct libraries just to admire the metadata of a Quake 2 model? 🌟🔍
    formats.kaitai.io/ #BinaryFormatsGallery #FileFormats #TechArt #KaitaiStruct #Quake2 #HackerNews #ngated

  22. Revisiting bsdiff as a tool for digital preservation


    by @beet_keeper

    I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

    On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

    In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

    #ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

  23. Revisiting bsdiff as a tool for digital preservation


    by @beet_keeper

    I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

    On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

    In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

    Continue reading “Revisiting bsdiff as a tool for digital preservation”

    #ac3 #archives #audio #audiovisual #audit #authenticity #av #bash #bsdiff #checksums #code4lib #corruption #corruptionIndex #digipres #digitalArchiving #digitalForensics #digitalLiteracy #digitalPreservation #digitalStorage #diplomatics #fileFormats #glitch #glitchAudio #glitchart #integrity #preservationAnalysis #preservationMetadata #provenance #sensitivityIndex #storage

  24. Revisiting bsdiff as a tool for digital preservation


    by @beet_keeper

    I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

    On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

    In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

    #ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

  25. Revisiting bsdiff as a tool for digital preservation


    by @beet_keeper

    I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

    On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

    In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

    #ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav

  26. Revisiting bsdiff as a tool for digital preservation


    by @beet_keeper

    I introduced bsdiff in a blog in 2014. bsdiff compares the differences between two files, e.g. broken_file_a and corrected_file_b and creates a patch that can be applied to broken_file_a to generate a byte-for-byte match for corrected_file_b.

    On the face of it, in an archive, we probably only care about corrected_file_2 and so why would we care about a technology that patches a broken file?

    In all of the use-cases we can imagine the primary reasons are cost savings and removing redundancy in file storage or transmission of digital information. In one very special case we can record the difference between broken_file_a and corrected_file_b and give users a totally objective method of recreating corrected_file_b from broken_file_a providing 100% verifiable proof of the migration pathway taken between the two files.

    #ac3 #Archives #audio #audiovisual #Audit #authenticity #av #Bash #bsdiff #checksums #Code4Lib #corruption #corruptionIndex #digipres #DigitalArchiving #DigitalForensics #digitalLiteracy #DigitalPreservation #DigitalStorage #diplomatics #FileFormats #flac #glitch #glitchAudio #GlitchArt #integrity #mp3 #PreservationAnalysis #PreservationMetadata #provenance #sensitivityIndex #Storage #wav