Advertisement
Guest User

Untitled

a guest
Nov 7th, 2016
206
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 31.11 KB | None | 0 0
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  2. <?xml version="1.0" encoding="UTF-8"?><?xml-model href="grammar/rash.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?><!--
  3. The RASH Framework: enabling HTML+RDF submissions in scholarly venues
  4. by Angelo Di Iorio, Andrea Giovanni Nuzzolese, Francesco Osborne, Silvio Peroni, Francesco Poggi, Michael Smith, Fabio Vitali, Juhn Zhao
  5.  
  6. This work is licensed under a Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/).
  7. You are free to:
  8. * Share - copy and redistribute the material in any medium or format
  9. * Adapt - remix, transform, and build upon the material
  10. for any purpose, even commercially.
  11.  
  12. The licensor cannot revoke these freedoms as long as you follow the license terms.
  13.  
  14. Under the following terms:
  15. * Attribution - You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  16. --><html xmlns="http://www.w3.org/1999/xhtml" prefix="
  17. a: http://www.essepuntato.it/paper/iswc2015/demo/
  18. c: http://www.essepuntato.it/cited-by/iswc2015/demo/
  19. p: http://www.essepuntato.it/person/
  20. o: http://www.essepuntato.it/organisation/
  21. r: http://www.essepuntato.it/role/
  22. fabio: http://purl.org/spar/fabio/
  23. cito: http://purl.org/spar/cito/
  24. pro: http://purl.org/spar/pro/
  25. schema: http://schema.org/
  26. prism: http://prismstandard.org/namespaces/basic/2.0/
  27. frbr: http://purl.org/vocab/frbr/core#
  28. dcterms: http://purl.org/dc/terms/"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><!-- Visualisation requirements (mandatory for optimal reading) --><meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1"><link rel="stylesheet" href="css/bootstrap.min.css"><link rel="stylesheet" href="css/rash.css"><script src="js/jquery.min.js"><![CDATA[ ]]></script><script src="js/bootstrap.min.js"><![CDATA[ ]]></script><script src="js/rash.js"><![CDATA[ ]]></script><!-- /END Visualisation requirements (mandatory for optimal reading) --><!-- Metadata --><title about="a:version-of-record" property="dcterms:title">The RASH Framework: enabling HTML+RDF submissions in scholarly venues</title><!-- Author's data (one or more) --><meta about="mailto:angelo.diiorio@unibo.it" typeof="schema:Person" name="dc.creator" property="schema:name" content="Angelo Di Iorio"><meta about="mailto:angelo.diiorio@unibo.it" property="schema:email" content="angelo.diiorio@unibo.it"><link about="mailto:angelo.diiorio@unibo.it" property="schema:affiliation" href="http://www.essepuntato.it/organisation/cs-unibo"><meta about="mailto:andrea.nuzzolese@example.com" typeof="schema:Person" name="dc.creator" property="schema:name" content="Andrea Giovanni Nuzzolese"><meta about="mailto:andrea.nuzzolese@example.com" property="schema:email" content="andrea.nuzzolese@example.com"><link about="mailto:andrea.nuzzolese@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/cs-unibo"><link about="mailto:andrea.nuzzolese@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/stlab-cnr"><meta about="mailto:francesco.osborne@example.com" typeof="schema:Person" name="dc.creator" property="schema:name" content="Francesco Osborne"><meta about="mailto:francesco.osborne@example.com" property="schema:email" content="francesco.osborne@example.com"><link about="mailto:francesco.osborne@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/kmi-open"><meta about="mailto:silvio.peroni@unibo.it" typeof="schema:Person" name="dc.creator" property="schema:name" content="Silvio Peroni"><meta about="mailto:silvio.peroni@unibo.it" property="schema:email" content="silvio.peroni@unibo.it"><link about="mailto:silvio.peroni@unibo.it" property="schema:affiliation" href="http://www.essepuntato.it/organisation/cs-unibo"><link about="mailto:silvio.peroni@unibo.it" property="schema:affiliation" href="http://www.essepuntato.it/organisation/stlab-cnr"><meta about="mailto:francesco.poggi5@unibo.it" typeof="schema:Person" name="dc.creator" property="schema:name" content="Francesco Poggi"><meta about="mailto:francesco.poggi5@unibo.it" property="schema:email" content="francesco.poggi@unibo.it"><link about="mailto:francesco.poggi5@unibo.it" property="schema:affiliation" href="http://www.essepuntato.it/organisation/cs-unibo"><meta about="mailto:mike@example.com" typeof="schema:Person" name="dc.creator" property="schema:name" content="Michael Smith"><meta about="mailto:mike@example.com" property="schema:email" content="mike@example.com"><link about="mailto:mike@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/w3c-tokyo"><link about="mailto:mike@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/media-keio"><meta about="mailto:fabio.vitali@unibo.it" typeof="schema:Person" name="dc.creator" property="schema:name" content="Fabio Vitali"><meta about="mailto:fabio.vitali@unibo.it" property="schema:email" content="fabio.vitali@unibo.it"><link about="mailto:fabio.vitali@unibo.it" property="schema:affiliation" href="http://www.essepuntato.it/organisation/cs-unibo"><meta about="mailto:j.zhao5@example.com" typeof="schema:Person" name="dc.creator" property="schema:name" content="Jun Zhao"><meta about="mailto:j.zhao5@example.com" property="schema:email" content="j.zhao5@example.com"><link about="mailto:j.zhao5@example.com" property="schema:affiliation" href="http://www.essepuntato.it/organisation/sc-lanc"><!-- Affiliations --><meta about="http://www.essepuntato.it/organisation/cs-unibo" property="schema:name" typeof="schema:Organization" content="Department of Computer Science and Engineering, University of Bologna, Bologna, Italy"><meta about="http://www.essepuntato.it/organisation/stlab-cnr" property="schema:name" typeof="schema:Organization" content="Semantic Technology Laboratory, Institute of Cognitive Sciences and Technologies, Italian National Research Council, Rome, Italy"><meta about="http://www.essepuntato.it/organisation/kmi-open" property="schema:name" typeof="schema:Organization" content="Knowledge Media Institute, The Open University, Milton Keynes, United Kingdom"><meta about="http://www.essepuntato.it/organisation/sc-lanc" property="schema:name" typeof="schema:Organization" content="School of Computing and Communications, Lancaster University, Lancaster, United Kingdom"><meta about="http://www.essepuntato.it/organisation/w3c-tokyo" property="schema:name" typeof="schema:Organization" content="World Wide Web Consortium, Shinjuku, Tokyo, Japan"><meta about="http://www.essepuntato.it/organisation/media-keio" property="schema:name" typeof="schema:Organization" content="Graduate School of Media and Governance, Keio University, Fujisawa, Kanagawa, Japan"><!-- Paper keywords (one or more) --><meta about="a:version-of-record" property="prism:keyword" content="RASH"><meta about="a:version-of-record" property="prism:keyword" content="Semantic Publishing"><meta about="a:version-of-record" property="prism:keyword" content="document conversion"><meta about="a:version-of-record" property="prism:keyword" content="XSLT"><meta about="a:version-of-record" property="prism:keyword" content="Semantic Web"><meta about="a:version-of-record" property="prism:keyword" content="Digital Publishing"><!-- /END Metadata --><!-- Other RDF statements --><script type="text/turtle"><![CDATA[
  29.  
  30. @prefix a: <http://www.essepuntato.it/paper/iswc2015/demo/> .
  31. @prefix p: <http://www.essepuntato.it/person/> .
  32. @prefix fabio: <http://purl.org/spar/fabio/> .
  33. @prefix pro: <http://purl.org/spar/pro/> .
  34. @prefix frbr: <http://purl.org/vocab/frbr/core#> .
  35. @prefix r: <http://www.essepuntato.it/role/> .
  36. @prefix o: <http://www.essepuntato.it/organisation/> .
  37.  
  38. a:rash-framework a fabio:ResearchPaper ;
  39. frbr:realization a:version-of-record ;
  40. frbr:creator p:adi, p:an, p:fo, p:essepuntato, p:fp, p:ms, p:fv, p:jz .
  41.  
  42. a:version-of-record a fabio:DemoPaper ;
  43. frbr:embodiment a:html-format, a:pdf-format .
  44.  
  45. a:html-format a fabio:WebPage ;
  46. frbr:exemplar <https://rawgit.com/essepuntato/rash/master/papers/rash-demo-iswc2015.html> .
  47.  
  48. a:pdf-format a fabio:DigitalManifestation ;
  49. frbr:exemplar <https://rawgit.com/essepuntato/rash/master/papers/rash-demo-iswc2015.pdf> .
  50.  
  51. <mailto:angelo.diiorio@unibo.it> pro:holdsRoleInTime r:adi-author-of-rash-framework , r:adi-affiliation .
  52. <mailto:andrea.nuzzolese@example.com> pro:holdsRoleInTime r:an-author-of-rash-framework , r:an-affiliation .
  53. <mailto:francesco.osborne@example.com> pro:holdsRoleInTime r:fo-author-of-rash-framework , r:fo-affiliation .
  54. <mailto:silvio.peroni@unibo.it> pro:holdsRoleInTime r:essepuntato-author-of-rash-framework , r:essepuntato-affiliation .
  55. <mailto:francesco.poggi5@unibo.it> pro:holdsRoleInTime r:fp-author-of-rash-framework , r:fp-affiliation .
  56. <mailto:mike@example.com> pro:holdsRoleInTime r:ms-author-of-rash-framework , r:ms-affiliation .
  57. <mailto:fabio.vitali@unibo.it> pro:holdsRoleInTime r:fv-author-of-rash-framework , r:fv-affiliation .
  58. <mailto:j.zhao5@example.com> pro:holdsRoleInTime r:jz-author-of-rash-framework , r:jz-affiliation .
  59.  
  60. r:adi-author-of-rash-framework a pro:RoleInTime ;
  61. pro:withRole pro:author ;
  62. pro:relatesToDocument a:rash-framework .
  63. r:an-author-of-rash-framework a pro:RoleInTime ;
  64. pro:withRole pro:author ;
  65. pro:relatesToDocument a:rash-framework .
  66. r:fo-author-of-rash-framework a pro:RoleInTime ;
  67. pro:withRole pro:author ;
  68. pro:relatesToDocument a:rash-framework .
  69. r:essepuntato-author-of-rash-framework a pro:RoleInTime ;
  70. pro:withRole pro:author ;
  71. pro:relatesToDocument a:rash-framework .
  72. r:fp-author-of-rash-framework a pro:RoleInTime ;
  73. pro:withRole pro:author ;
  74. pro:relatesToDocument a:rash-framework .
  75. r:ms-author-of-rash-framework a pro:RoleInTime ;
  76. pro:withRole pro:author ;
  77. pro:relatesToDocument a:rash-framework .
  78. r:fv-author-of-rash-framework a pro:RoleInTime ;
  79. pro:withRole pro:author ;
  80. pro:relatesToDocument a:rash-framework .
  81. r:jz-author-of-rash-framework a pro:RoleInTime ;
  82. pro:withRole pro:author ;
  83. pro:relatesToDocument a:rash-framework .
  84.  
  85. r:adi-affiliation a pro:RoleInTime ;
  86. pro:withRole pro:affiliate ;
  87. pro:relatesToDocument a:rash-framework ;
  88. pro:relatesToOrganization o:cs-unibo .
  89. r:an-affiliation a pro:RoleInTime ;
  90. pro:withRole pro:affiliate ;
  91. pro:relatesToDocument a:rash-framework ;
  92. pro:relatesToOrganization o:cs-unibo , o:stlab-cnr .
  93. r:fo-affiliation a pro:RoleInTime ;
  94. pro:withRole pro:affiliate ;
  95. pro:relatesToDocument a:rash-framework ;
  96. pro:relatesToOrganization o:kmi-open .
  97. r:essepuntato-affiliation a pro:RoleInTime ;
  98. pro:withRole pro:affiliate ;
  99. pro:relatesToDocument a:rash-framework ;
  100. pro:relatesToOrganization o:cs-unibo , o:stlab-cnr .
  101. r:fp-affiliation a pro:RoleInTime ;
  102. pro:withRole pro:affiliate ;
  103. pro:relatesToDocument a:rash-framework ;
  104. pro:relatesToOrganization o:cs-unibo .
  105. r:ms-affiliation a pro:RoleInTime ;
  106. pro:withRole pro:affiliate ;
  107. pro:relatesToDocument a:rash-framework ;
  108. pro:relatesToOrganization o:w3c-tokyo .
  109. r:fv-affiliation a pro:RoleInTime ;
  110. pro:withRole pro:affiliate ;
  111. pro:relatesToDocument a:rash-framework ;
  112. pro:relatesToOrganization o:cs-unibo .
  113. r:jz-affiliation a pro:RoleInTime ;
  114. pro:withRole pro:affiliate ;
  115. pro:relatesToDocument a:rash-framework ;
  116. pro:relatesToOrganization o:sc-lanc .
  117.  
  118. ]]></script><script src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"><![CDATA[ ]]></script><script type="application/ld+json">[{"@context":"http:\/\/vitali.web.cs.unibo.it\/twiki\/pub\/TechWeb16\/context.json","@type":"review","@id":"#review0","article":{"@id":"","eval":{"@id":"#review0-eval","@type":"score","status ":"pso:accepted-for-publication","author":"mailto:jessica.jones@alias.com","date":"7\/11\/2016"}},"0":{"@context":"http:\/\/vitali.web.cs.unibo.it\/twiki\/pub\/TechWeb16\/context.json","@type":"review","@id":"#review0","article":{"@id":"","eval":{"@id":"#review0-eval","@type":"RateDocument","text ":"ciao","author":"mailto:jessica.jones@alias.com","date":"7\/11\/2016"}}},"comments":["#review0-c0"]},{"@context":"http:\/\/vitali.web.cs.unibo.it\/twiki\/pub\/TechWeb16\/context.json","@type":"comment","@id":"#review0-c0","text":"ciao","start":"5484","lenght":"6","author":"mailto:jessica.jones@alias.com","date":"7\/11\/2016"},{"@context":"http:\/\/vitali.web.cs.unibo.it\/twiki\/pub\/TechWeb16\/context.json","@type":"person","@id":"mailto:jessica.jones@alias.com","name":"\r\n\r\nJessica Jones ","as":{"@id":"#role0","@type":"role","role_type":"pro:reviewer","in":""}}]</script></head><body><!-- Abstract --><section role="doc-abstract" class="container"><h1>Abstract</h1>
  119. <p>This paper introduces the <em>RASH Framework</em>, i.e., a set of specifications and tools for writing academic articles in <em>RASH</em>, a simplified version of HTML. RASH focuses strictly o<span class="selectedText" onmouseover="mymouseover(this)" onmouseout="mymouseout(this)" id="review0-c0" unsaved="false">n writ</span>ing 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>
  120. </section><!-- Sections --><section id="sec_introduction"><h1>Introduction</h1>
  121. <p>In the last months of 2014, several posts within technical mailing lists of the <a href="https://lists.w3.org/Archives/Public/public-lod/2014Nov/0003.html">Web</a> and <a href="https://lists.w3.org/Archives/Public/public-lod/2014Oct/0058.html">Semantic Web</a> 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 Publishing has promised us <a href="#force11" title="Bourne, P. E., Clark, T., Dale, R., de Waard, A., Herman, I., Hovy, E. H., &amp; Shotton, D. (2011). FORCE11 White Paper: Improving The Future of Research Communications and e-Scholarship. White paper, 28 October 2011. FORCE11. https://www.force11.org/white_paper" class="cgen">[1]</a> <a href="#shotton-sempub" title="Shotton, D., Portwin, K., Klyne, G., &amp; Miles, A. (2009). Adventures in Semantic Publishing: Exemplar Semantic Enhancements of a Research Article. PLoS Computational Biology, 5(4): e1000361. http://dx.doi.org/10.1371/journal.pcbi.1000361" class="cgen">[6]</a>. However, such formats should support the needs of the actors involved in the production/delivery/use of scholarly articles.</p>
  122. <p>Along the lines of other existing works on this topic (e.g., <em><a href="https://github.com/csarven/linked-research">Linked Research</a></em> project <a href="#linked-research" title="Capadisli, S., Riedl, R., &amp; Auer, S. (2015). Enabling Accessible Knowledge. In Proc. of CeDEM 2015. OA version available at http://csarven.ca/enabling-accessible-knowledge" class="cgen">[2]</a> and <em><a href="http://scholarlymarkdown.com/">ScholarlyMarkdown</a></em> <a href="#scholmd" title="Lin, T. T. Y., &amp; Beales, G. (2015). ScholarlyMarkdown Syntax Guide. Guide, 31 January 2015. http://scholarlymarkdown.com/Scholarly-Markdown-Guide.html" class="cgen">[5]</a>), in this paper we introduce the <em>RASH Framework</em>, i.e., a set of specifications and tools for writing academic articles in <em>RASH</em> (an HTML+RDF-based markup language for writing scholarly documents) which aims at addressing all the aforementioned issues.</p>
  123. <p>The rest of the paper is structured as follows. In <a href="#sec_rationale" class="cgen">Section 2</a> we introduce the rationale for the RASH Framework. In <a href="#sec_tools" class="cgen">Section 3</a> we provide a quick overview of all its tools, that are available in the <a href="https://github.com/essepuntato/rash">Framework repository</a>. Finally, in <a href="#sec_conclusions" class="cgen">Section 4</a> we conclude the paper sketching out some future developments.</p>
  124. </section><section id="sec_rationale"><h1>A <q>Web-first</q> framework for research articles</h1>
  125. <p>Some works, e.g., Capadisli <em>et al.</em> <a href="#linked-research" title="Capadisli, S., Riedl, R., &amp; Auer, S. (2015). Enabling Accessible Knowledge. In Proc. of CeDEM 2015. OA version available at http://csarven.ca/enabling-accessible-knowledge" class="cgen">[2]</a>, 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 <em>linearisations</em> for writing a scholarly text. This freedom could, however, results in two main kinds of issues:</p>
  126. <ul><li><p><em>visualisation bottleneck</em> &ndash; it may affect the correct use of existing, well-developed and pretty standard CSSs;</p></li>
  127. <li><p><em>less focus on the research content</em> &ndash; 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></li>
  128. </ul><p>A further complication to an already complex scenario comes from the <em>necessary</em> 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>
  129. <p>The RASH Framework<sup class="fn cgen"><a name="fn_pointer_fn1" href="#fn1" title="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.">1</a></sup> has been proposed in order to address all the aforementioned issues. It is a set of specifications and tools for writing academic articles in <em>RASH</em> - a summary of the whole framework is introduced in <a href="#fig_framework" class="cgen">Figure 1</a>.</p>
  130. <p>The <em>Research Articles in Simplified HTML</em> (<em>RASH</em>) format is a markup language that restricts the use of <a href="http://www.w3.org/TR/html5/">HTML</a> elements to only <em>25 elements</em> for writing academic research articles, and it is entirely based on a strong theory on <em>structural patterns</em> for XML documents <a href="#patterns" title="Di Iorio, A., Peroni, S., Poggi, F., &amp; Vitali, F. (2014). Dealing with structural patterns of XML documents. Journal of the American Society for Information Science and Technology, 65(9): 1884&ndash;1900. http://dx.doi.org/10.1002/asi.23088" class="cgen">[4]</a>. It allows authors to use <a href="http://www.w3.org/TR/rdfa-syntax/">RDFa</a> annotations within any element of the language. In addition, RASH allows the use of elements <code>script</code> (with the attribute <code>type</code> set to <q>text/turtle</q> or to <q>application/ld+json</q>) within the element <code>head</code> for adding plain Turtle or JSON-LD content. Any RASH documents begins as a simple (X)HTML5 document<sup class="fn cgen"><a name="fn_pointer_fn4" href="#fn4" title="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.">2</a></sup>, by specifying the document element <code>html</code> (with the usual namespace) that contains the element <code>head</code> for defining metadata of the document, and the element <code>body</code> for including the whole content of the document.</p>
  131. <figure id="fig_framework"><p>
  132. <img src="img/rash-demo-iswc2015-framework.png" alt="The RASH Framework"></p>
  133. <figcaption><strong class="cgen">Figure 1. </strong>The RASH Framework and its components addressing needs of different users.</figcaption></figure></section><section id="sec_tools"><h1>Tools in the Framework</h1>
  134. <p>In this section we introduce all the tools shown in <a href="#fig_framework" class="cgen">Figure 1</a> that we have developed in order to support users in adopting RASH - all the tools are distributed under an <a href="http://opensource.org/licenses/ISC">ISC License</a> or a <a href="http://creativecommons.org/licenses/by/4.0/">CC-BY 4.0 International License</a>.</p>
  135. <p><strong>Validation.</strong> All the markup items in RASH are defined as a <a href="http://relaxng.org/">RelaxNG</a> 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 <a href="http://validator.w3.org/nu/">W3C Nu HTML Checker</a> does for all HTML documents.</p>
  136.  
  137. <p><strong>Visualisation.</strong> The visualisation of RASH documents is rendered by the browser in the current form by means of appropriate <a href="http://www.w3.org/Style/CSS/specs.en.html">CSS3</a> stylesheets and javascript scripts developed for this purpose. We are actually using some external libraries, i.e., <a href="http://getbootstrap.com/">Bootstrap</a> and <a href="http://jquery.com/">JQuery</a>, 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 <a href="https://rawgit.com/essepuntato/rash/master/papers/rash-demo-iswc2015.html">https://rawgit.com/essepuntato/rash/master/papers/rash-demo-iswc2015.html</a>.</p>
  138.  
  139. <p><strong>Conversion</strong>. We have spent some efforts in preparing XSLT 2.0 documents for converting RASH documents into different LaTeX styles, such as <a href="http://www.acm.org/sigs/publications/proceedings-templates">ACM ICPS</a> and <a href="http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0">Springer LNCS</a>. This is, actually, one of the crucial steps to guarantee the use of RASH within international events<sup class="fn cgen"><a name="fn_pointer_fn3" href="#fn3" title="https://github.com/essepuntato/rash/#venues-that-have-adopted-rash-as-submission-format">3</a></sup> and to be able to publish RASH documents in the official LaTeX format as required by the organisation committee 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>
  140.  
  141. <p><strong>Enhancement.</strong> 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 <a href="http://purl.org/spar/doco">Document Component Ontology (DoCO)</a> <a href="#doco" title="Constantin, A., Peroni, S., Pettifer, S., Shotton, D., &amp; Vitali, F. (in press). The Document Component Ontology (DoCO). To appear in Semantic Web. OA version available at http://www.semantic-web-journal.net/system/files/swj1016.pdf" class="cgen">[3]</a>. In particular, a Java application called <em>SPAR Xtractor suite</em> 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.</p>
  142. </section><section id="sec_conclusions"><h1>Conclusions</h1>
  143. <p>In this paper we have introduced the <em>RASH Framework</em>, i.e., a set of specifications and tools for writing academic articles in <em>RASH</em>. 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 (<a href="http://www.sparontologies.net">http://www.sparontologies.net</a>), 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>
  144. </section><!-- References --><section role="doc-bibliography" class="container"><h1>References</h1>
  145. <ol about="a:version-of-record" rel="cito:cites"><li id="force11" about="c:force11-expression" typeof="fabio:WhitePaper" property="frbr:realizationOf" resource="c:force11-work" role="doc-biblioentry"><p about="c:force11-expression" property="dcterms:bibliographicCitation">Bourne, P. E., Clark, T., Dale, R., de Waard, A., Herman, I., Hovy, E. H., &amp; Shotton, D. (2011). FORCE11 White Paper: Improving The Future of Research Communications and e-Scholarship. White paper, 28 October 2011. FORCE11. <a about="c:force11-work" typeof="fabio:MeetingReport" property="fabio:hasURL" content="https://www.force11.org/white_paper" href="https://www.force11.org/white_paper">https://www.force11.org/white_paper</a></p></li><li id="linked-research" about="c:linked-research-expression" typeof="fabio:ConferencePaper" property="frbr:realizationOf" resource="c:linked-research-work" role="doc-biblioentry"><p about="c:linked-research-expression" property="dcterms:bibliographicCitation">Capadisli, S., Riedl, R., &amp; Auer, S. (2015). Enabling Accessible Knowledge. In Proc. of CeDEM 2015. <span about="c:linked-research-work" typeof="fabio:ResearchPaper">OA version available at <a about="c:linked-research-expression" property="fabio:hasRepresentation" href="http://csarven.ca/enabling-accessible-knowledge">http://csarven.ca/enabling-accessible-knowledge</a></span></p></li><li id="doco" about="c:doco-expression" typeof="fabio:JournalArticle" property="frbr:realizationOf" resource="c:doco-work" role="doc-biblioentry"><p about="c:doco-expression" property="dcterms:bibliographicCitation">Constantin, A., Peroni, S., Pettifer, S., Shotton, D., &amp; Vitali, F. (in press). The Document Component Ontology (DoCO). To appear in Semantic Web. <span about="c:doco-work" typeof="fabio:ResearchPaper">OA version available at <a about="c:doco-expression" property="fabio:hasRepresentation" href="http://www.semantic-web-journal.net/system/files/swj1016.pdf">http://www.semantic-web-journal.net/system/files/swj1016.pdf</a></span></p></li><li id="patterns" about="c:patterns-expression" typeof="fabio:JournalArticle" property="frbr:realizationOf" resource="c:patterns-work" role="doc-biblioentry"><p about="c:patterns-expression" property="dcterms:bibliographicCitation">Di Iorio, A., Peroni, S., Poggi, F., &amp; Vitali, F. (2014). Dealing with structural patterns of XML documents. Journal of the American Society for Information Science and Technology, 65(9): 1884&ndash;1900. <a about="c:patterns-work" typeof="fabio:ResearchPaper" href="http://dx.doi.org/10.1002/asi.23088">http://dx.doi.org/<span about="c:patterns-expression" property="prism:doi">10.1002/asi.23088</span></a></p></li><li id="scholmd" about="c:scholmd-expression" typeof="fabio:WebContent" property="frbr:realizationOf" resource="c:scholmd-work" role="doc-biblioentry"><p about="c:scholmd-expression" property="dcterms:bibliographicCitation">Lin, T. T. Y., &amp; Beales, G. (2015). ScholarlyMarkdown Syntax Guide. Guide, 31 January 2015. <a about="c:scholmd-work" typeof="fabio:InstructionalWork" property="fabio:hasURL" content="http://scholarlymarkdown.com/Scholarly-Markdown-Guide.html" href="http://scholarlymarkdown.com/Scholarly-Markdown-Guide.html">http://scholarlymarkdown.com/Scholarly-Markdown-Guide.html</a></p></li><li id="shotton-sempub" about="c:shotton-sempub-expression" typeof="fabio:JournalArticle" property="frbr:realizationOf" resource="c:shotton-sempub-work" role="doc-biblioentry"><p about="c:shotton-sempub-expression" property="dcterms:bibliographicCitation">Shotton, D., Portwin, K., Klyne, G., &amp; Miles, A. (2009). Adventures in Semantic Publishing: Exemplar Semantic Enhancements of a Research Article. PLoS Computational Biology, 5(4): e1000361. <a about="c:shotton-sempub-work" typeof="fabio:ResearchPaper" href="http://dx.doi.org/10.1371/journal.pcbi.1000361">http://dx.doi.org/<span about="c:shotton-sempub-expression" property="prism:doi">10.1371/journal.pcbi.1000361</span></a></p></li></ol></section><!-- Footnotes --><section role="doc-footnotes" class="container"><h1>Footnotes</h1><section id="fn1" role="doc-footnote"><p>The full project is available at <a href="https://github.com/essepuntato/rash/">https://github.com/essepuntato/rash/</a>. Please use the hashtag <code>#rashfwk</code> for referring to any of the items defined in the RASH Framework via Twitter or other social platforms.<sup class="hidden-print cgen"><a href="#fn_pointer_fn1">[back]</a></sup></p>
  146. </section><section id="fn4" role="doc-footnote"><p>Please refer to the official RASH documentation, available at <a href="http://cs.unibo.it/save-sd/rash">http://cs.unibo.it/save-sd/rash</a>, for a complete introduction of all the elements and attributes that can be used in RASH documents.<sup class="hidden-print cgen"><a href="#fn_pointer_fn4">[back]</a></sup></p>
  147. </section><section id="fn3" role="doc-footnote"><p><a href="https://github.com/essepuntato/rash/#venues-that-have-adopted-rash-as-submission-format">https://github.com/essepuntato/rash/#venues-that-have-adopted-rash-as-submission-format</a><sup class="hidden-print cgen"><a href="#fn_pointer_fn3">[back]</a></sup></p>
  148. </section></section></body></html>
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement