<?xml version="1.0" encoding="utf-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
<teiHeader>
  <fileDesc>
    <titleStmt>
      <title>The Importance of Single Source Publishing in Scientific
Publishing</title>
      <author>Antoine Fauchié</author>
    </titleStmt>
    <publicationStmt>
      <date>2022-05-18</date>
    </publicationStmt>
    <sourceDesc>
      <p>Produced by pandoc.</p>
    </sourceDesc>
  </fileDesc>
</teiHeader>
<text>
<body>
<div type="level1" xml:id="what-is-single-source-publishing">
  <head>What is Single Source Publishing?</head>
  <p><hi rendition="simple:bold">The expression
  <hi rendition="simple:italic">Single Source Publishing</hi> refers to
  generating several formats from a single source.</hi> One and unique
  source can be used to produce various artifacts, 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 <hi rendition="simple:italic">one</hi> source.
  What is this <quote>source</quote>? A set of texts, some metadata,
  some bibliographical data, perhaps some images and other medias.
  Perhaps you already use the principles of Single Source Publishing:
  it’s long and tedious with a classic word processor, it’s a little bit
  complex with LaTeX, it’s expensive and it’s not easy with XML, and
  it’s very powerful and more accessible with tools like Pandoc.</p>
  <p><hi rendition="simple:bold">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.</hi></p>
</div>
<p><figure>
  <graphic url="images/single-source-publishing.png" />
</figure></p>
<div type="level1" xml:id="academic-publishing-constraints">
  <head>Academic publishing constraints</head>
  <p>Scientific publishing has several constraints:</p>
  <list type="unordered">
    <item>
      <p><hi rendition="simple:bold">critical material</hi>: footnotes,
      citations, bibliographies, figures, insert, etc.</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">metadata</hi>: data about data,
      like title, subtitle, authors, standard identifiers (ORCID,
      Wikidata, etc.)</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">text structuration</hi>: semantic
      is a necessity for digital diffusion (especially in XML)</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">bibliographic data</hi>: structured
      references</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">peer review</hi>: a complex
      circulation and validation for the texts</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">specific formats</hi>: articles,
      books, conference proceedings, etc.</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">publish or perish</hi>: publish a
      lot but slowly</p>
    </item>
  </list>
</div>
<div type="level1" xml:id="different-formats-in-and-out">
  <head>Different formats: in and out</head>
  <p><hi rendition="simple:bold">In</hi>: with non-standard formats like
  <seg type="code">.doc</seg>/<seg type="code">.docx</seg>, it’s not
  possible to produce richly structured content. XML is a good solution
  but it’s complex and there are not enough customizable tools to write
  and edit. Lightweight and understandable markup languages is an
  interesting intermediate solution, like Markdown or AsciiDoc.</p>
  <p><hi rendition="simple:bold">Out</hi>: scientific publishing
  requires specific formats: PDF, HTML, and various XML with specific
  schemas (like JATS or TEI).</p>
</div>
<div type="level1" xml:id="benefits-of-single-source-publishing">
  <head>Benefits of Single Source Publishing</head>
  <list type="unordered">
    <item>
      <p><hi rendition="simple:bold">one source</hi>: no need to manage
      multiple versions, like the <seg type="code">.doc</seg> version,
      the <seg type="code">.xml</seg> version and the
      <seg type="code">.indd</seg> version</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">horizontal workflow</hi>: all
      actors of the publishing chain can participate at the same time
      (in theory). Writers, publishers, designers and digital
      distributors can work at the same time</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">multimodal</hi>: one source but
      multiple artifacts/formats</p>
    </item>
    <item>
      <p><hi rendition="simple:bold">time and energy saving</hi></p>
    </item>
    <item>
      <p><hi rendition="simple:bold">work in progress</hi>: building a
      publishing chain can be a work in progress</p>
    </item>
  </list>
</div>
<div type="level1" xml:id="issues-involved-in-the-single-source-publishing-principle">
  <head>Issues involved in the Single Source Publishing principle</head>
  <div type="level2" xml:id="legitimization-of-content">
    <head>Legitimization of content</head>
    <p>If the publishing chain can be horizontal, how can we do the
    legitimization of the content? How to deal with the validation of
    content, the structuration and the design of the document?</p>
  </div>
  <div type="level2" xml:id="evolution-of-publishing-practices">
    <head>Evolution of publishing practices</head>
    <list type="unordered">
      <item>
        <p>no more word processing (or much more less)</p>
      </item>
      <item>
        <p>more tech in publishing staff (but less complexity)</p>
      </item>
      <item>
        <p>publishers build their own publishing chain by assembling
        free programs/software</p>
      </item>
      <item>
        <p>publishing workflows can be fun!</p>
      </item>
    </list>
  </div>
  <div type="level2" xml:id="creation-of-adequate-tools">
    <head>Creation of adequate tools</head>
    <p>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 or centralised, they maintain a
    confusion between the structure of the contents and the graphic
    rendering.</p>
    <p><hi rendition="simple:bold">The academic community needs tools
    that correspond to its constraints!</hi> And it’s what a lot of
    people do, with an approach more or less compatible with the Single
    Source Publishing: Manifold, PubPubPub, Coko, Métopes, Quire, Stylo,
    etc.</p>
  </div>
</div>
<div type="level1" xml:id="concepts">
  <head>Concepts</head>
  <p>With Single Source Publishing come some interesting concepts:</p>
  <div type="level2" xml:id="hybridity">
    <head>Hybridity</head>
    <p>From Marshall McLuhan (McLuhan, 1965): the hybridity of the media
    generates new media: the media have an effect on each other. In the
    same way, it is interesting to take into account the influence of
    various formats on their unique source.</p>
  </div>
  <div type="level2" xml:id="hybridization">
    <head>Hybridization</head>
    <p>From Alessandro Ludovico (Ludovico &amp; Cramer, 2012): the
    hybridization of forms and formats is a phenomenon that can be
    observed in the first digital experiments: electronic versions come
    to complete already existing forms, printed and digital artifacts
    become hybrid.</p>
  </div>
  <div type="level2" xml:id="editorialization">
    <head>Editorialization</head>
    <p>From Marcello Vitali-Rosati (Vitali-Rosati, 2016):
    editorialization is the set of dynamics that produce and structure
    digital space. The adaptation of publishing chains to produce
    different artifacts is one way of understanding and constructing
    this space.</p>
  </div>
</div>
<div type="level1" xml:id="academic-single-source-publishing-in-practice-an-example">
  <head>Academic Single Source Publishing in practice: an example</head>
  <p>In the <hi rendition="simple:bold">Revue2.0 project</hi>
  (<ref target="https://revue20.org">revue20.org</ref>) lead by the
  Canada Research Chair on Digital Textualities, several journals have
  experimented Single Source Publishing with Stylo (a semantic editor
  for academic writing and publishing). With one source (a set of text,
  metadata, bibliographic data), scientific journals are able to produce
  the following formats: HTML for their website, PDF for their own
  distribution and for aggregators, and XML formats for digital
  distributors.</p>
  <p><hi rendition="simple:bold">Stylo</hi> is a tool designed to
  transform the digital workflow of scholarly journals in humanities and
  social sciences. As a WYSIWYM (What You See Is What You Mean) semantic
  text editor for the humanities, it aims to improve the academic
  publishing chain. Stylo is ready and free to use:
  <ref target="https://stylo.huma-num.fr">stylo.huma-num.fr</ref>.</p>
</div>
<div type="level1" xml:id="references">
  <head>References</head>
  <p xml:id="ref-blanc_technologies_2018">Blanc, J., &amp; Haute, L.
  (2018). Technologies de l’édition numérique.
  <hi rendition="simple:italic">Sciences du design</hi>,
  <hi rendition="simple:italic">8</hi>(2), 11–17.</p>
  <p xml:id="ref-hyde_single_2021">Hyde, A. (2021). Single Source
  Publishing. In <hi rendition="simple:italic">Coko</hi>.</p>
  <p xml:id="ref-ludovico_post-digital_2012">Ludovico, A., &amp; Cramer,
  F. (2012). <hi rendition="simple:italic">Post-digital print: the
  mutation of publishing since 1894</hi>. Onomatopee.</p>
  <p xml:id="ref-maxwell_mind_2019">Maxwell, J. W. (2019).
  <hi rendition="simple:italic">Mind the Gap: A Landscape Analysis of
  Open Source Publishing Tools and Platforms</hi>. The MIT Press.</p>
  <p xml:id="ref-mcluhan_understanding_1965">McLuhan, M. (1965).
  <hi rendition="simple:italic">Understanding media: the extensions of
  man.</hi> McGraw-Hill.</p>
  <p xml:id="ref-vitali-rosati_what_2016">Vitali-Rosati, M. (2016). What
  is editorialization ? <hi rendition="simple:italic">Sens
  Public</hi>.</p>
</div>
</body>
</text>
</TEI>
