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
Wait, is anyone else today's years old finding out that MIMETypes deference on the IANA website?
https://www.iana.org/assignments/media-types/application/trig
A list of properties used by the File Formats listed in the current Siegfried/Wikidata signature file. May be of interest to those creating new records.
Maintenance begins at creation, so why are we not creating better?
by @beet_keeperThe 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?”…
Nice surprise, @MediaArea have uploaded a bunch of #NTTW9 videos including mine on JSONID:
https://www.youtube.com/watch?v=ZMVb3Bc_irc
Check out their YouTube, and also I'd love to hear feedback on JSONID too. Please follow it on GitHub: https://github.com/ffdev-info/jsonid/
Euro-Office’s announcement – which sees IONOS, Nextcloud and other companies coming together to create a European alternative to office productivity software – has predictably sparked a wave of comments. Most of these focus on the issue of licensing: is the code open source? Who controls the repository? What are the conditions for forking, modifying or implementing it? While these are all valid questions, they fail to address the most important issue. The fact that almost no one is asking the question that matters tells us something significant about how the debate on digital sovereignty has been framed and who benefits from that framing. A licence tells you who owns the software, while the format tells you who owns the data A licence can be renegotiated, modified or updated. The history of FLOSS is full of projects that have changed governance models, divided communities, or changed course under new management. Licence terms are important, but they operate at the level of the software artefact. The native document format operates at a completely different level. It is the encoding level of every document produced, archived, and exchanged by institutions that adopt the software. It is the invisible structure of administrative memory within
All in a day's work for #archival #superheroes :
> What the data is that data?
> If only I had #METADATA ! 😁 🍰
InnocentZero
Thorsted
#Digital ⚓️ #Vagabond 🦈
Ross Spencer
Negative PID SL
Peter B.