"In the model we are developing, #libraries would own digital [#books], just as they do with physical books. Libraries would be able to both transfer their books to other libraries and to update books as needed for #preservation or to adapt to new #formats. Rights holders would retain #copyright to their works…Lending would be restricted to one reader at a time."
#NISO just announced a new #standard "enabling the combination of arbitrary portions of content, data, semantics, & other resources from separate sources [e.g. articles, books, data sets, metadata schemes] into a single, standards-based format optimized for interchange, search, & display." https://www.niso.org/publications/z39105-2023-cpld
[Calendrier d'avant Avent] En 2022, du 7 au 30 novembre, il y eut en exclusivité ici sur Framapiaf cet autre #format de calendrier : les 24 jours qui sont avant les 24 jours qui sont avant Noël ! C'est l'avant Avent.
En 2022, ces 24 astuces & trucs & informations concernaient le sujet du #format, https://framapiaf.org/deck/@ThierryStoehr/109304424363728259
Cette année 2023, extension de la période : les 31 dates de novembre vont bénéficier de ce #format, toujours à propos de #format. Et comme tout bon compte, ceci était le [0/31] !
[5/31] Connaissez-vous #Amaya ?
Ce logiciel fut à la pointe du Web. Il fut lancé à l'INRIA, puis fut rattaché au W3C.
Point important : il permettait de lire les pages Web (=navigateur)... mais AUSSI de les écrire et les mettre en ligne !
Amaya a permis de mettre en avant les #formats HTML, CSS, XML, RDF ou encore MathML.
Pour en savoir plus, voici un article et AUSSI un #format video sur l'histoire d'Amaya (interview de Vincent Quint), grâce à Software Heritage : https://www.softwareheritage.org/2023/10/26/unveiling-amaya-story/
Unlike JAWS, NVDA has always lacked the capability to distinguish between links which open other pages on the web and links which move us to other spots on the same page - "same page" links. To view a good example of this shortcoming, check the following: https://brltty.app/download.html
After the Download heading there's a list with 8 "same page links," but NVDA just says, "link," as they are encountered. We have to guess where the destinations for the links are. @NVAccess please do something for this long-standing issue.
@amir Each link there is identified as a link, and looks like any other link, both visually, and to NVDA. The browser itself makes no distinction between a same page and remote link. When you press NVDA+k to report the link destion, NVDA reads, eg: "https://brltty.app/download.html#formats" rather than "#formats" - because that is what the browser presents & also what is shown visually when you hover the mouse over it. I'm not aware of a long standing issue on GitHub, but please link to it & I'll check it out
PS: There are 𝘮𝘢𝘯𝘺 reasons to offer well-formatted HTML alongside PDF, or to stop PDF-only publishing. Accessibility is first, followed closely by making work friendly to mobile users, users with low bandwidth, and users who need to text-mine, cut/paste, or use machine translation.
my work explores the role of digital data, methods and infrastructures in the composition of collective life.
i'm currently focusing on...
📘 a book on public data practices
🌳 arts-based digital methods for exploring environmental issues
🐌 a special issue on critical technical practices in digital research
🗃 documenting online mobilisations of east and southeast asian communities in the uk
i'm senior lecturer in critical infrastructure studies at the department of digital humanities, king's college london; cofounder of publicdatalab.org; and research associate at digitalmethods.net + medialab.sciencespo.fr.