Commit 0329d91e authored by Antoine Fauchié's avatar Antoine Fauchié
Browse files

edit: synopsis and schema

parent 275724f6
---
title: "The importance of single source publishing in scientific publishing"
resume: ""
color: "ffead0-3786b3-265d8a-f26419-000000"
---
## What is Single Source Publishing?
The expression _Single Source Publishing_ refers to generating several formats from a single source.
One and unique source can be used to produce various artefacts, without having to switch from one working progress to another.
With a Single Source Publishing approach it's possible to produce a PDF format for printing, an XML export for a digital platform or a digital version in HTML format, just with _one_ source.
What is this "source"?
A set of texts, some metadata, some bibliographical data, perhaps some images and other medias: some files…
Perhaps you already use the principles of Single Source Publishing: it's possible but painful with a classic word processor, it's a little bit complex with LaTeX, just expansive and black boxes with proprietary solutions, and very powerful with Pandoc.
**This editorial challenge brings up both theoretical and technical questions, such as the legitimization of content, the evolution of publishing practices, and the creation of adequate tools.**
![](single-source-publishing.jpg)
## Academic publishing constraints
Scientific publishing has several constraints:
- **critical material**: footnotes, citations, bibliographies, figures, insert, etc.
- **metadata**: data about data, like title, subtitle, authors, standard identifiers (ORCID, Wikidata, etc.)
- **text structuration**: semantic is a necessity for digital diffusion (especially in XML)
- **bibliographic data**: structured references
- **peer review**: a complex circulation and validation for the texts
- **specific formats**: articles, books, conference proceeding, etc.
- **publish or perish**: publish a lot but slowly
## Different formats: in and out
In: non-standard formats like `.doc`/`.docx`, time to change for comprehensible lightweight markup.
Out: HTML, PDF and XML.
## Benefits of Single Source Publishing
- **one source**: no need to manage multiple versions
- **horizontal workflow**: everyone in the _publishing chain_ can take part at the same part (in theory)
- **multimodal**: one source but multiple artefacts/formats
- **time and energy saving**:
## Legitimization of content
If the publishing chain can be horizontal, how can we do the legitimization of the content?
## Evolution of publishing practices
- no more word processing (or much more less)
- more tech in publishing staff (but less complexity)
- publishing workflows can be fun!
## Creation of adequate tools
Since the 1980's, scientific community use one and unique tool for writing and editing: different generations of word processors like Microsoft Word, LibreOffice Writer or Google Docs.
Proprietary, copycat of proprietary software, centralised, they maintain a confusion between the structure of the contents and the graphic rendering.
**The academic community needs tools that correspond to its constraints!**
And it's what a lot of people do, with an approach more or less compatible with the Single Source Publishing: Manifold, PubPubPub, Métopes, Quire, Stylo, etc.
## Concepts
With Single Source Publishing comes some interesting concepts:
### Hybridity
From Marshal McLuhan:
### Hybridization
From Alessandro Ludovico:
### Editorialization
From Marcello Vitali-Rosati:
## Academic Single Source Publishing in practice: an example
Revue2.0 + Stylo.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment