Skip to main content
Go to the home page of the European Commission (opens in new window)
English English
CORDIS - EU research results
CORDIS

Single-Source Collaborative Publishing

Periodic Reporting for period 1 - OnePub (Single-Source Collaborative Publishing)

Reporting period: 2023-10-01 to 2025-03-31

Over the past 30 years, book publishing has been transformed from a purely physical to a fully digital process. However, the key elements of the pipeline remain the same: An author hands off a manuscript to an editor who, after multiple exchanges back and forth, hands the corrected manuscript to a compositor who, using a template created by a graphic designer, lays out the content. Books with illustrations need an iconographer and/or graphic designer to select or create illustrations. The compositor creates proofs for authors and the editor to check and revise, and updates the content and layout accordingly. The final approved version is sent to the printer, which involves more back-and-forth exchanges to create the PDF-for-press version. Each participant uses different software––authors use text editors, designers use graphic design tools, compositors use layout tools and printers use PDF manipulation tools––and all changes must be propagated throughout the pipeline.

Digital publishing generates additional output formats, such as ePub and HTML, which introduce new constraints, such as accommodating variable-size windows. Each format requires a separate production pipeline, involving additional experts and specialized tools. Recent legislation adds further complexity, such as the European Accessibility Act's mandate that all textbook illustrations include full text descriptions to accommodate visually impaired readers.

The current state of digital publishing raises several key challenges:

- The constant transformation of the content's format at each stage of the pipeline impedes collaboration between authors and production staff. Producing a digital facsimile is the only way to share a state of the current work in progress. For example, an author's or editor's hand-written corrections on a PDF version must be re-entered manually by the compositor, potentially introducing errors or major layout problems.

- Some books, especially textbooks, have stringent page limits. Because authors cannot see a correction's effect on the layout until a new proof is produced, they rarely consider formatting trade-offs and may need multiple discussions to find a suitable solution.

- Creating multiple output formats is not only cumbersome and time-consuming, but also error-prone, since each new format risks generating content that is out of sync with other content.

- Publishers often rely on proprietary software and formats that need specialized tools and expertise. This locks them into restrictive workflows that cannot easily handle new output formats, such as transforming a print book's static images into videos or interactive elements for the HTML version.
OnePub's key innovation is the creation of multiple, specialized editors that allow all participants to collaboratively edit the same 'ground truth' content source, thus mitigating today's time-consuming and error-prone correction process. Centering the publishing process around an open, human-readable format makes it possible to generate diverse publication formats.

We have developed three main components: a back-end, a set of editors, and a set of renderers.

- The back-end manages the document sources, including their history and their dependencies.

- The editors support real-time collaborative editing – both on- and off-line – and are tailored to the specific needs of each type of user. For example, authors can enter content and define semantics, such as specifying a subtitle or a sidebar, and access real-time previews even before the final layout template is finished. Everyone can see the effects of their modifications in real time and communicate directly within the same content source, without worrying that their edits will be lost or misunderstood.

- The renderers generate alternative multimedia formats. Each output format––PDF-for-press, ePub, HTML—can be derived automatically from the shared content source.
OnePub demonstrates the potential of a single-source architecture for managing print and on-line publications. OnePub's open architecture creates a rich, extensible ecosystem where different stakeholders can develop customized tools and services that remain interoperable with the base layer of the architecture. For example, one company might offer AI tools that generate text descriptions of images to meet accessibility guidelines. Another might create specialized editors for creating interactive content.

The prototype developed in the project is being tested in-house and with external users, but must be further developed into an MVP (Minimum Viable Product) in order to be used at scale, in a production environment. Several avenues for reaching the market are being explored, including the creation of a start-up that would use it as a SaaS platform (Software-as-as-Service), as opposed to, e.g. licensing it. The source code of the base system will be made available under an open-source license to encourage uptake by third parties.
OnePub single-source publishing architecture
My booklet 0 0