#file-formats — Public Fediverse posts

Does Hollywood even use computers? #digipres #fileformats #Reacher

Does Hollywood even use computers? #digipres #fileformats #Reacher

Does Hollywood even use computers? #digipres #fileformats #Reacher

Does Hollywood even use computers? #digipres #fileformats #Reacher

Does Hollywood even use computers? #digipres #fileformats #Reacher

Version 125 of the #PRONOM signature file was released earlier today!

https://pronom.nationalarchives.gov.uk/releases/v125

(with a contribution from @tibhannover for the LabVIEW Virtual Instruments 3.0 file format!)

#digipres #FileFormats

Version 125 of the #PRONOM signature file was released earlier today!

https://pronom.nationalarchives.gov.uk/releases/v125

(with a contribution from @tibhannover for the LabVIEW Virtual Instruments 3.0 file format!)

#digipres #FileFormats

Version 125 of the #PRONOM signature file was released earlier today!

https://pronom.nationalarchives.gov.uk/releases/v125

(with a contribution from @tibhannover for the LabVIEW Virtual Instruments 3.0 file format!)

#digipres #FileFormats

Version 125 of the #PRONOM signature file was released earlier today!

https://pronom.nationalarchives.gov.uk/releases/v125

(with a contribution from @tibhannover for the LabVIEW Virtual Instruments 3.0 file format!)

#digipres #FileFormats

Version 125 of the #PRONOM signature file was released earlier today!

https://pronom.nationalarchives.gov.uk/releases/v125

(with a contribution from @tibhannover for the LabVIEW Virtual Instruments 3.0 file format!)

#digipres #FileFormats

The more I read about Wav files, the more I realise that they're a bit of a time capsule. An echo of a 1991 IBM & Microsoft (and earlier).

Behind the scenes they're actually a format called RIFF (Resource Interchange File Format). Basically tagged data chunks. So it can support most (all?) types of data. A container file format.

What do you think AVI is behind the scenes? (RIFF), WebP, also RIFF (which was a surprise) and a bunch of others.

The Wikipedia page states that RIFF was extended from IFF (Interchange File Format`). A brainchild of Electronic Arts and Commodore from 1985.

Now knowing this, I can see how the design of PNG files were influenced from IFF. Same idea on tagged chunks, different ordering of elements and CRC addition. I did learn that it is noted in the 1.2 PNG spec § 12.4 Why-not-use-format-X.

In parallel to all this, TIFF (Tagged Image File Format) has no relation to IFF.

#FileFormats #History

The more I read about Wav files, the more I realise that they're a bit of a time capsule. An echo of a 1991 IBM & Microsoft (and earlier).

Behind the scenes they're actually a format called RIFF (Resource Interchange File Format). Basically tagged data chunks. So it can support most (all?) types of data. A container file format.

What do you think AVI is behind the scenes? (RIFF), WebP, also RIFF (which was a surprise) and a bunch of others.

The Wikipedia page states that RIFF was extended from IFF (Interchange File Format`). A brainchild of Electronic Arts and Commodore from 1985.

Now knowing this, I can see how the design of PNG files were influenced from IFF. Same idea on tagged chunks, different ordering of elements and CRC addition. I did learn that it is noted in the 1.2 PNG spec § 12.4 Why-not-use-format-X.

In parallel to all this, TIFF (Tagged Image File Format) has no relation to IFF.

#FileFormats #History

The more I read about Wav files, the more I realise that they're a bit of a time capsule. An echo of a 1991 IBM & Microsoft (and earlier).

Behind the scenes they're actually a format called RIFF (Resource Interchange File Format). Basically tagged data chunks. So it can support most (all?) types of data. A container file format.

What do you think AVI is behind the scenes? (RIFF), WebP, also RIFF (which was a surprise) and a bunch of others.

The Wikipedia page states that RIFF was extended from IFF (Interchange File Format`). A brainchild of Electronic Arts and Commodore from 1985.

Now knowing this, I can see how the design of PNG files were influenced from IFF. Same idea on tagged chunks, different ordering of elements and CRC addition. I did learn that it is noted in the 1.2 PNG spec § 12.4 Why-not-use-format-X.

In parallel to all this, TIFF (Tagged Image File Format) has no relation to IFF.

#FileFormats #History

The more I read about Wav files, the more I realise that they're a bit of a time capsule. An echo of a 1991 IBM & Microsoft (and earlier).

Behind the scenes they're actually a format called RIFF (Resource Interchange File Format). Basically tagged data chunks. So it can support most (all?) types of data. A container file format.

What do you think AVI is behind the scenes? (RIFF), WebP, also RIFF (which was a surprise) and a bunch of others.

The Wikipedia page states that RIFF was extended from IFF (Interchange File Format`). A brainchild of Electronic Arts and Commodore from 1985.

Now knowing this, I can see how the design of PNG files were influenced from IFF. Same idea on tagged chunks, different ordering of elements and CRC addition. I did learn that it is noted in the 1.2 PNG spec § 12.4 Why-not-use-format-X.

In parallel to all this, TIFF (Tagged Image File Format) has no relation to IFF.

#FileFormats #History

The more I read about Wav files, the more I realise that they're a bit of a time capsule. An echo of a 1991 IBM & Microsoft (and earlier).

Behind the scenes they're actually a format called RIFF (Resource Interchange File Format). Basically tagged data chunks. So it can support most (all?) types of data. A container file format.

What do you think AVI is behind the scenes? (RIFF), WebP, also RIFF (which was a surprise) and a bunch of others.

The Wikipedia page states that RIFF was extended from IFF (Interchange File Format`). A brainchild of Electronic Arts and Commodore from 1985.

Now knowing this, I can see how the design of PNG files were influenced from IFF. Same idea on tagged chunks, different ordering of elements and CRC addition. I did learn that it is noted in the 1.2 PNG spec § 12.4 Why-not-use-format-X.

In parallel to all this, TIFF (Tagged Image File Format) has no relation to IFF.

#FileFormats #History

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/

Comments: https://news.ycombinator.com/item?id=49508608

#HackerNews #ReverseEngineering #ImHex #FileFormats #TechTutorials #Cybersecurity

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/

Comments: https://news.ycombinator.com/item?id=49508608

#HackerNews #ReverseEngineering #ImHex #FileFormats #TechTutorials #Cybersecurity

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/

Comments: https://news.ycombinator.com/item?id=49508608

#HackerNews #ReverseEngineering #ImHex #FileFormats #TechTutorials #Cybersecurity

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/

Comments: https://news.ycombinator.com/item?id=49508608

#HackerNews #ReverseEngineering #ImHex #FileFormats #TechTutorials #Cybersecurity

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/

Comments: https://news.ycombinator.com/item?id=49508608

#HackerNews #ReverseEngineering #ImHex #FileFormats #TechTutorials #Cybersecurity

Search Engine Roundtable: Google Search Showing Fewer PDF Files. But Why?. “Google seems to be showing fewer and fewer PDF files, and when it does show PDF files, it seems not to show them from some pretty important sites, like IRS.gov, New York State, and some others. But in some cases we are seeing Google show PDF documents, without you having to explicitly filter for PDF file types.”

Search Engine Roundtable: Google Search Showing Fewer PDF Files. But Why?. “Google seems to be showing fewer and fewer PDF files, and when it does show PDF files, it seems not to show them from some pretty important sites, like IRS.gov, New York State, and some others. But in some cases we are seeing Google show PDF documents, without you having to explicitly filter for PDF file types.”

Search Engine Roundtable: Google Search Showing Fewer PDF Files. But Why?. “Google seems to be showing fewer and fewer PDF files, and when it does show PDF files, it seems not to show them from some pretty important sites, like IRS.gov, New York State, and some others. But in some cases we are seeing Google show PDF documents, without you having to explicitly filter for PDF file types.”

Search Engine Roundtable: Google Search Showing Fewer PDF Files. But Why?. “Google seems to be showing fewer and fewer PDF files, and when it does show PDF files, it seems not to show them from some pretty important sites, like IRS.gov, New York State, and some others. But in some cases we are seeing Google show PDF documents, without you having to explicitly filter for PDF file types.”

Search Engine Roundtable: Google Search Showing Fewer PDF Files. But Why?. “Google seems to be showing fewer and fewer PDF files, and when it does show PDF files, it seems not to show them from some pretty important sites, like IRS.gov, New York State, and some others. But in some cases we are seeing Google show PDF documents, without you having to explicitly filter for PDF file types.”

Tell me you work with obscure #fileformats without telling me you work with obscure unknown formats. #digipres #ai #fullcircle what is it called when AI references your own blog?

Tell me you work with obscure #fileformats without telling me you work with obscure unknown formats. #digipres #ai #fullcircle what is it called when AI references your own blog?

Tell me you work with obscure #fileformats without telling me you work with obscure unknown formats. #digipres #ai #fullcircle what is it called when AI references your own blog?

Tell me you work with obscure #fileformats without telling me you work with obscure unknown formats. #digipres #ai #fullcircle what is it called when AI references your own blog?

Tell me you work with obscure #fileformats without telling me you work with obscure unknown formats. #digipres #ai #fullcircle what is it called when AI references your own blog?

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ' (hex: 0x27) and double quotes " (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

Declarative all the way down: Building PRONOM signatures with JSONID

PRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.

Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.

XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?

The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.

But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.

The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.

We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.

And standards are well and good, but what if tooling could help us?

For JSON this is exactly what I have tried to do in JSONID.

What does this feature look like? And what does it get us? Let’s take a look.

I almost cancelled my Adobe subscription last year - then realised I couldn't.
Software like Adobe's isn't just selling tools, it's locking you in. The real cost isn't the subscription. It's that your work - effects, libraries, templates built over years - lives in proprietary formats. Cancel, and you lose access to your own assets.
It's not about price. It's about owning the way you work.
Ever been locked out of an old project?
#todormotion #DreamDesignDeliver #fileformats #Adobe

I almost cancelled my Adobe subscription last year - then realised I couldn't.
Software like Adobe's isn't just selling tools, it's locking you in. The real cost isn't the subscription. It's that your work - effects, libraries, templates built over years - lives in proprietary formats. Cancel, and you lose access to your own assets.
It's not about price. It's about owning the way you work.
Ever been locked out of an old project?
#todormotion #DreamDesignDeliver #fileformats #Adobe

I almost cancelled my Adobe subscription last year - then realised I couldn't.
Software like Adobe's isn't just selling tools, it's locking you in. The real cost isn't the subscription. It's that your work - effects, libraries, templates built over years - lives in proprietary formats. Cancel, and you lose access to your own assets.
It's not about price. It's about owning the way you work.
Ever been locked out of an old project?
#todormotion #DreamDesignDeliver #fileformats #Adobe

I almost cancelled my Adobe subscription last year - then realised I couldn't.
Software like Adobe's isn't just selling tools, it's locking you in. The real cost isn't the subscription. It's that your work - effects, libraries, templates built over years - lives in proprietary formats. Cancel, and you lose access to your own assets.
It's not about price. It's about owning the way you work.
Ever been locked out of an old project?
#todormotion #DreamDesignDeliver #fileformats #Adobe

I almost cancelled my Adobe subscription last year - then realised I couldn't.
Software like Adobe's isn't just selling tools, it's locking you in. The real cost isn't the subscription. It's that your work - effects, libraries, templates built over years - lives in proprietary formats. Cancel, and you lose access to your own assets.
It's not about price. It's about owning the way you work.
Ever been locked out of an old project?
#todormotion #DreamDesignDeliver #fileformats #Adobe

I'd sell my soul to have bundled html + css + images + assets in a zipped format.

Basically, modern web - all of javascript. Instead of using PDFs.

That'd be a banger way to create and distribute documents. Also very versatile and portable, cuz, like, websites lol. Prove me wrong.

EDIT: I reinvented sophisticated epubs. Wow.

#pdf #pdfs #html #css #document #fileformatwars #fileformats #fileformat #epub #epubs

I'd sell my soul to have bundled html + css + images + assets in a zipped format.

Basically, modern web - all of javascript. Instead of using PDFs.

That'd be a banger way to create and distribute documents. Also very versatile and portable, cuz, like, websites lol. Prove me wrong.

EDIT: I reinvented sophisticated epubs. Wow.

#pdf #pdfs #html #css #document #fileformatwars #fileformats #fileformat #epub #epubs

I'd sell my soul to have bundled html + css + images + assets in a zipped format.

Basically, modern web - all of javascript. Instead of using PDFs.

That'd be a banger way to create and distribute documents. Also very versatile and portable, cuz, like, websites lol. Prove me wrong.

EDIT: I reinvented sophisticated epubs. Wow.

#pdf #pdfs #html #css #document #fileformatwars #fileformats #fileformat #epub #epubs

I'd sell my soul to have bundled html + css + images + assets in a zipped format.

Basically, modern web - all of javascript. Instead of using PDFs.

That'd be a banger way to create and distribute documents. Also very versatile and portable, cuz, like, websites lol. Prove me wrong.

EDIT: I reinvented sophisticated epubs. Wow.

#pdf #pdfs #html #css #document #fileformatwars #fileformats #fileformat #epub #epubs

New PRONOM release! v124 #digipres #droid #fileformats #signatures https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml

New PRONOM release! v124 #digipres #droid #fileformats #signatures https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml

New PRONOM release! v124 #digipres #droid #fileformats #signatures https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml

New PRONOM release! v124 #digipres #droid #fileformats #signatures https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml

New PRONOM release! v124 #digipres #droid #fileformats #signatures https://www.nationalarchives.gov.uk/aboutapps/pronom/release-notes.xml

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

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?

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

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?

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

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?

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

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?

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

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?

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid

The MP3 fatigue
https://negativepid.blog/the-mp3-fatigue/

#music #MP3 #vinyls #analogueMusic #fileFormats #soundCompression #Internet #tech #IT #science #STEM #computing #inventions #innovation #digitalRights #copyrights #streamingServices #negativepid