> These are all great points! Some of it depends on whether implementation > is in authoring (by hand or in InDesign) or ingestion (this is what Wendy > has suggested, but there is currently no spec for what publishing platforms > should do at ingestion time) or in the RS. Still lots to figure out. > If we want support across potentially all EPUB and reading systems, we can't rely on authoring or ingestion IMO. Authoring would mean that millions of EPUB files already on the market would not support these virtual locators. Ingestion doesn't really exist as a concept in EPUB. Some retailers process EPUB files to either transform them into something else or tweak them, but we also have dozens of EPUB reading apps that simply import files without any pre-processing ahead of time. In Readium Mobile, we generate what we call a positions list <https://readium.org/architecture/models/locators/positions/> when an app opens an EPUB file. Although our locator model <https://readium.org/architecture/models/locators/> supports the ability to indicate a CFI, this is not something that we actually generate since it would be too costly to do so on a smartphone/tablet. In Readium Web, our current plan is to generate the positions list server-side on the fly. The client (most of the time a Web App, but this could also work fine with native apps) can fetch this list as a separate JSON document.
Received on Saturday, 5 June 2021 10:34:25 UTC