Have you read the article? There’s half a sentence in like the fifth paragraph that might be explaining what it does or might just be making an aside comment. At no point do they say what it is. Just what they’re doing with it.
It’s like they’re talking about farming without explaining what a tractor is.
Two links down https://iiif.io/get-started/how-iiif-works/ :
> Learning about IIIF (generally pronounced “triple-eye-eff”) can be overwhelming at first,
I don’t think that’s our fault, that’s the authors’ fault.
I hate people who talk in circles and then imagine themselves misunderstood geniuses. Just fuckin… read some Feynman already and adjust your attitude.
Below the fold, two pages deep:
> Modern Web browsers understand how to display formats like .jpg and .mp4 at defined sizes, but cannot do much else. The IIIF specifications align with general Web standards that define how all browsers work to enable richer functionality beyond viewing an image or audio/visual files. For images, that means enabling deep zoom, comparison, structure (i.e., for an object such as a book, structure = page order) and annotation. For audio/visual materials, that means being able to deliver complex structures (such as several reels of film that make up a single movie) along with things like captions, transcriptions/translations, annotations, and more.
That’s all I wanted to know. Now I know if I care. Wait, what were we talking about? I’ve got four shelf-feet of unread books and a “read later” bookmark list and a “watch later” YouTube list that is so long you would cry. Do I want to get into this still or work on those?
Don’t bore the reader, or stuff like this ^ will go through their head. ESPECIALLY now that attention spans are getting shorter.