@@ -74,7 +74,7 @@ These diagrams don’t need to be explored in depth for an understanding of how
### HTML
Coko is using HTML as the source of truth. This has been core to Coko’s philosophy - bringing publishing to the web.
Kotahi is using HTML as the source of truth. This has been core to Coko’s philosophy - bringing publishing to the web.
However, we’re also realistic about the ways in which authors are working: they’re largely using Microsoft Word to prepare manuscripts – and editors by and large seem to resist moving away from MS Word. In this case, we need to bring the Word Documents into the web, that is, convert the docx files to HTML at submission time.
...
...
@@ -98,9 +98,11 @@ The following is an excerpt taken from article written by Adam Hyde and Wendell
<li>interpret the original MS Word file and carry forward as much information as that original Word file contained for possible future use in interpreting the document structure – or representing any features of interest – while not actually structuring the document. </li>
</ol>
<p>Interestingly, since HTML does not require you to enforce a strict document structure if you do not have it, an unstructured document flows into HTML as easily as a structured, or partially structured, document flows into it. If your aim is a well-controlled document format, such a failure to enforce strict structures is regarded as a flaw or weakness. Yet, since we do not have much or any document structure in the originating Word document, and our goal is to improve it – HTML’s flexibility becomes a critical feature.” </p>
<p>This process produces an intermediary carrier format – an information-rich, sanitized HTML format that is suitable for improvement. A final step of the xSweet libraries further interprets the information carried over from the conversion which implies structural elements, applies that structure, and then converts the total output to a (configurable) target HTML profile. In an HTML editor, we can then bring to bear further tools (Wax, for example) for adding structure, reviewing, commenting, and revising. </p>
<p>This process produces an intermediary carrier format – an information-rich, sanitized HTML format that is suitable for improvement.</p>
</section>
A final step of the xSweet libraries further interprets the information carried over from the conversion which implies structural elements, applies that structure, and then converts the total output to a (configurable) target HTML profile. In an HTML editor, we can then bring to bear further tools (Wax, for example) for adding structure, reviewing, commenting, and revising.
### Single-Source Publishing
Kotahi's design is also informed by the idea of Single-Source Publishing. There’s a lot that could be said about this; where it’s relevant to Kotahi and JATS is that the Kotahi model sees JATS production as an integral part of the publishing workflow, not something that should be considered as a separate step.
