<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The RASH Framework: enabling HTML+RDF submissions in scholarly venues</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Angelo Di Iorioȯ</string-name>
          <email>angelo.diiorio@unibo.it</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrea Giovanni Nuzzoleseȯӱɞ</string-name>
          <email>andrea.nuzzolese@istc.cnr.it</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francesco Osborneɘ</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Silvio Peroniȯӱɞ</string-name>
          <email>silvio.peroni@unibo.it</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francesco Poggiȯ</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Smithȃӱȁ</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fabio Vitaliȯ</string-name>
          <email>fabio.vitali@unibo.it</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jun Zhaoɒ</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>This paper introduces the RASH Framework, i.e., a set of specifications and tools for writing academic articles in RASH, a simplified version of HTML. RASH focuses strictly on writing the content of the paper leaving all the issues about its validation, visualisation, conversion, and data extraction to the tools developed within the framework.</p>
      </abstract>
      <kwd-group>
        <kwd>Digital Publishing</kwd>
        <kwd>RASH</kwd>
        <kwd>Semantic Publishing</kwd>
        <kwd>Semantic Web</kwd>
        <kwd>XSLT</kwd>
        <kwd>document conversion</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>In the last months of 2014, several posts within technical mailing lists of the Web
and Semantic Web community have discussed an evergreen topic in scholarly
communication, i.e., how authors of research papers could submit their works in
HTML rather than, say, PDF, MS Word or LaTeX. Besides the obvious
justification of simplification and unification of data formats for drafting, submission and
publication, an additional underlying rationale is that the adoption of HTML
in the context of scientific publications would ease the embedding of semantic
annotations, thus making a step towards the improvement of research
communications thanks to already existing W3C standards such as RDFa and Turtle. The
adoption of Web-first formats in scientific literature, i.e., HTML and RDF, is a
necessary step towards the complex (and exciting) scenarios that the Semantic</p>
      <p>
        Publishing has promised us [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. However, such formats should support the
needs of the actors involved in the production/delivery/use of scholarly articles.
      </p>
      <p>
        Along the lines of other existing works on this topic (e.g., Linked Research
project [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and ScholarlyMarkdown [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]), in this paper we introduce the RASH
Framework, i.e., a set of specifications and tools for writing academic articles
in RASH (an HTML+RDF-based markup language for writing scholarly
documents) which aims at addressing all the aforementioned issues.
      </p>
      <p>The rest of the paper is structured as follows. In Section 2 we introduce the
rationale for the RASH Framework. In Section 3 we provide a quick overview of
all its tools, that are available in the Framework repository. Finally, in Section 4
we conclude the paper sketching out some future developments.
2</p>
    </sec>
    <sec id="sec-2">
      <title>A “Web-first” framework for research articles</title>
      <p>
        Some works, e.g., Capadisli et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], suggest not to force any particular HTML
structure for research papers. In this way, the author of a paper is free to use any
possible kinds of HTML linearisations for writing a scholarly text. This freedom
could, however, results in two main kinds of issues:
– visualisation bottleneck – it may affect the correct use of existing,
welldeveloped and pretty standard CSSs;
– less focus on the research content – the fact that a certain paper is not
visualised in a browser very well could bring the author to work on the
presentation of the text, rather than on its research content.
      </p>
      <p>A further complication to an already complex scenario comes from the
necessary involvement of publishers. Leaving the authors free of using their own
HTML format could be also counterproductive from a publisher’s perspective,
in particular when we speaking about the possibility of adopting such HTML
formats for regular conference/journal camera-ready submissions.</p>
      <p>The RASH Framework7 has been proposed in order to address all the
aforementioned issues. It is a set of specifications and tools for writing academic
articles in RASH - a summary of the whole framework is introduced in Fig. 1.</p>
      <p>
        The Research Articles in Simplified HTML (RASH) format is a markup
language that restricts the use of HTML elements to only 25 elements for
writing academic research articles, and it is entirely based on a strong theory on
structural patterns for XML documents [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. It allows authors to use RDFa
annotations within any element of the language. In addition, RASH allows the use
of elements script (with the attribute type set to “text/turtle” or to
“application/ld+json”) within the element head for adding plain Turtle or JSON-LD
content. Any RASH documents begins as a simple (X)HTML5 document8, by
7 The full project is available at https://github.com/essepuntato/rash/. Please
use the hashtag #rashfwk for referring to any of the items defined in the RASH
Framework via Twitter or other social platforms.
8 Please refer to the official RASH documentation, available at http://cs.unibo.it/
save-sd/rash, for a complete introduction of all the elements and attributes that
can be used in RASH documents.
specifying the document element html (with the usual namespace) that contains
the element head for defining metadata of the document, and the element body
for including the whole content of the document.
In this section we introduce all the tools shown in Fig. 1 that we have developed
in order to support users in adopting RASH - all the tools are distributed under
an ISC License or a CC-BY 4.0 International License.
      </p>
      <p>Validation. All the markup items in RASH are defined as a RelaxNG
grammar and are compatible with HTML5. We have developed a script to enable
RASH users to check their documents simultaneously both against the specific
requirements in the RelaxNG grammar and also against the full set of HTML
checks that the W3C Nu HTML Checker does for all HTML documents.</p>
      <p>Visualisation. The visualisation of RASH documents is rendered by the
browser in the current form by means of appropriate CSS3 stylesheets and
javascript scripts developed for this purpose. We are actually using some
external libraries, i.e., Bootstrap and JQuery, in order to guarantee the current
clear visualisation and for adding additional tools to the user. As an example, the
RASH version of this paper is available at https://rawgit.com/essepuntato/
rash/master/papers/rash-demo-iswc2015.html.</p>
      <p>Conversion. We have spent some efforts in preparing XSLT 2.0 documents
for converting RASH documents into different LaTeX styles, such as ACM ICPS
and Springer LNCS. This is, actually, one of the crucial steps to guarantee the
use of RASH within international events9 and to be able to publish RASH
documents in the official LaTeX format as required by the organisation committee
9
https://github.com/essepuntato/rash/#venues-that-have-adopted-rash-assubmission-format
of such events. In addition, we have already developed another XSLT 2.0
document to perform conversions from OpenOffice documents into RASH documents,
which allows authors to write a paper through the OpenOffice editor and then
converting the related ODT file into RASH automatically.</p>
      <p>
        Enhancement. A recent development of the RASH Framework has
concerned the automatic enrichment of RASH documents with RDFa annotations
defining the actual structure of such documents in terms of the Document
Component Ontology (DoCO) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. In particular, a Java application called SPAR
Xtractor suite has been developed: it takes a RASH document as input and
returns a new RASH document where all its markup elements have been annotated
with their actual (structural) semantics.
4
      </p>
    </sec>
    <sec id="sec-3">
      <title>Conclusions</title>
      <p>In this paper we have introduced the RASH Framework, i.e., a set of
specifications and tools for writing academic articles in RASH. We have discussed
the rationale behind the development of RASH, and we have presented the
language with all the validation/visualisation/conversion/extraction tools we have
developed so far. As immediate future developments, we plan to create
additional scripts for extracting RDF statements from RASH documents according
to SPAR Ontologies (http://www.sparontologies.net), and to develop
additional XSLT documents in order to convert DOCX documents into RASH and
to convert RASH documents into several formats for scholarly communications,
such as EPUB, DocBook, and LaTeX IEEE styles.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bourne</surname>
            ,
            <given-names>P. E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dale</surname>
            , R., de Waard,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herman</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hovy</surname>
            ,
            <given-names>E. H.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <source>FORCE11 White Paper: Improving The Future of Research Communications and e-Scholarship. White paper, 28 October</source>
          <year>2011</year>
          .
          <article-title>FORCE11</article-title>
          . https://www.force11.org/white_paper
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Capadisli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riedl</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>Enabling Accessible Knowledge</article-title>
          .
          <source>In Proc. of CeDEM</source>
          <year>2015</year>
          . OA version available at http://csarven.ca/enablingaccessible-knowledge
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Constantin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peroni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pettifer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Vitali</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <article-title>(in press). The Document Component Ontology (DoCO)</article-title>
          . To appear in Semantic Web. OA version available at http://www.semantic
          <article-title>-web-journal</article-title>
          .net/system/files/swj1016.pdf
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Di</given-names>
            <surname>Iorio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Peroni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Poggi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            , &amp;
            <surname>Vitali</surname>
          </string-name>
          ,
          <string-name>
            <surname>F.</surname>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Dealing with structural patterns of XML documents</article-title>
          .
          <source>Journal of the American Society for Information Science and Technology</source>
          ,
          <volume>65</volume>
          (
          <issue>9</issue>
          ):
          <fpage>1884</fpage>
          -
          <lpage>1900</lpage>
          . http://dx.doi.org/10.1002/asi.23088
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lin</surname>
          </string-name>
          , T. T. Y., &amp;
          <string-name>
            <surname>Beales</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2015</year>
          ).
          <article-title>ScholarlyMarkdown Syntax Guide</article-title>
          . Guide,
          <issue>31</issue>
          <year>January 2015</year>
          . http://scholarlymarkdown.com/Scholarly-Markdown-Guide.html
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Shotton</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Portwin</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klyne</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2009</year>
          ).
          <article-title>Adventures in Semantic Publishing: Exemplar Semantic Enhancements of a Research Article</article-title>
          .
          <source>PLoS Computational Biology</source>
          ,
          <volume>5</volume>
          (
          <issue>4</issue>
          ): e1000361. http://dx.doi.org/10.1371/journal.pcbi. 1000361
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>