{"id":6764,"date":"2020-11-23T02:50:00","date_gmt":"2020-11-23T01:50:00","guid":{"rendered":"https:\/\/2021.eswc-conferences.org\/?page_id=6764"},"modified":"2021-10-03T20:28:19","modified_gmt":"2021-10-03T18:28:19","slug":"html-submission-guide","status":"publish","type":"page","link":"https:\/\/2023.eswc-conferences.org\/html-submission-guide\/","title":{"rendered":"HTML Submission Guide"},"content":{"rendered":"\n<p><strong>ESWC 2022<\/strong>&nbsp;welcomes research articles employing the Open Web Platform. This document provides guidance to authors who wish to make their contributions available in HTML and related technology stack.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">General Guidance<\/h2>\n\n\n\n<p>Contributions in HTML should be shared in EasyChair as a ZIP archive that contains the complete and self-contained content of the article. It should include a main \u201cindex.html\u201d and all used resources (like media, scripts) to guarantee a correct visualization of the document on common desktop and mobile Web browsers. Please note the following key requirements:<\/p>\n\n\n\n<ul><li>HTML template: any tooling or process can be used to produce the HTML.<\/li><li>Content: the full content of the article must be human-readable with HTML alone. The use of CSS and JavaScript is encouraged, but should not interfere with the accessibility of the content.<\/li><li>Offline-friendly: there must not be any external dependencies (e.g., a network connection) to retrieve, to render, or to manipulate the content of the article.<\/li><li>Privacy: scripts must not be used to identify or track readers.<\/li><li>View: the rendered article (HTML+CSS) should have the \u201clook and feel\u201d of the LNCS authoring guidelines. Pixel-perfection is not expected. This is to ensure visual consistency of the proceedings as well as to have comparative page limits with the print-based publication. The HTML article has to be compliant with the page limit constraint.<\/li><\/ul>\n\n\n\n<p>It should be possible to read the HTML contributions on an average desktop computer or mobile computer that is equipped with a reasonably current, Javascript-enabled Web browser (e.g., Firefox, Chrome\/Chromium, Internet Explorer, Brave, Safari). We encourage authors to make their articles as accessible as possible (for reading and interacting) because different consumers (in this case initially the reviewers and chairs) may have different environments and abilities.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Final (\u201ccamera-ready\u201d) version<\/h2>\n\n\n\n<p>Formatting requirements for the&nbsp;<em>final version<\/em>&nbsp;differ by call.<\/p>\n\n\n\n<ul><li>Articles accepted in the&nbsp;Research, In-Use, and Resources tracks&nbsp;will be published by Springer in the printed conference proceedings, as a part of the Lecture Notes in Computer Science (LNCS) series. Springer requires the sources of articles that have been accepted for publication in&nbsp;<a href=\"http:\/\/www.springer.com\/de\/it-informatik\/lncs\/conference-proceedings-guidelines\">LaTeX or Word format<\/a>. If an article submitted in HTML is accepted, the authors can choose to do this step manually or using tool support as outlined below.<\/li><li>Articles accepted in the&nbsp;Posters &amp; Demos track&nbsp;and in the&nbsp;Doctoral Consortium&nbsp;will be published as&nbsp;<a href=\"http:\/\/ceur-ws.org\/\">CEUR-WS.org<\/a>&nbsp;proceedings volumes. CEUR-WS.org allows articles to be in HTML but, for guaranteed printability and archiving, requires an additional PDF, which should be a print-out of the HTML article in the LNCS layout.<\/li><li>Articles accepted in the&nbsp;Industry track&nbsp;will be published on the conference website. The same \u201cHTML+PDF\u201d rule applies as explained above for posters, demos and doctoral papers.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Recommendations<\/h2>\n\n\n\n<p>We recommend that authors take the following steps independently of the general process:<\/p>\n\n\n\n<p>Before sharing your article with ESWC, self-publish your HTML version, eg. at a repository, personal or institution website that\u2019s publicly accessible and archivable from a URL.<\/p>\n\n\n\n<p>Include the URL of your self-published article along the lines of: \u201cIdentifier:&nbsp;<a href=\"http:\/\/example.org\/article\">http:\/\/example.org\/article<\/a>&nbsp;\u201c after the list of authors and\/or include the URL in the abstract of your article. Make sure to preserve this information in your camera-ready version.<\/p>\n\n\n\n<p>Consider using a&nbsp;<a href=\"https:\/\/creativecommons.org\/\">Creative Commons<\/a>&nbsp;license like&nbsp;<a href=\"https:\/\/creativecommons.org\/licenses\/by\/4.0\/\">CC BY 4.0<\/a>&nbsp;on the self-published version.<\/p>\n\n\n\n<p>Create multiple archived copies of the self-published version using on-demand free archive services like&nbsp;<a href=\"https:\/\/web.archive.org\/\">archive.org<\/a>,&nbsp;<a href=\"https:\/\/archive.is\/\">archive.is<\/a>.<\/p>\n\n\n\n<p>If you intend to also publish the \u201cAuthor\u2019s Accepted Manuscript\u201d version following peer-review, note Springer\u2019s&nbsp;<a href=\"https:\/\/www.springer.com\/gb\/open-access\/authors-rights\/self-archiving-policy\/2124\">self-archiving policy<\/a>.<\/p>\n\n\n\n<p>Send a notification about your original self-published article to the&nbsp;<a href=\"https:\/\/linkedresearch.org\/\">Linked Open Research Cloud<\/a>&nbsp;(LORC) to improve the discoverability of your article.<\/p>\n\n\n\n<p>For additional help, authors are welcome to&nbsp;<a href=\"https:\/\/gitter.im\/linkedresearch\/chat\">join the public chat<\/a>&nbsp;on&nbsp;<a href=\"https:\/\/linkedresearch.org\/\">Linked Research<\/a>. Please note that this not an official communication channel of the conference. It is an open community for scholarly communication and people passionate about the Web.<\/p>\n\n\n\n<p>Authors are encouraged to use tooling and processes that work best for them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">dokieli<\/h3>\n\n\n\n<p><a href=\"https:\/\/dokie.li\/\">dokieli<\/a>&nbsp;is a client-side editor for decentralized article publishing in HTML+RDF annotations, notifications, and social interactions. It implements W3C Recommendations like&nbsp;<a href=\"https:\/\/www.w3.org\/TR\/annotation-model\/\">Web Annotation<\/a>,&nbsp;<a href=\"https:\/\/www.w3.org\/TR\/ldn\/\">Linked Data Notifications<\/a>, and&nbsp;<a href=\"https:\/\/www.w3.org\/TR\/activitypub\/\">ActivityPub<\/a>.<\/p>\n\n\n\n<p>The&nbsp;<a href=\"https:\/\/dokie.li\/lncs-splnproc\">LNCS author guidelines<\/a>&nbsp;can be used as template (<a href=\"https:\/\/iswc2019.semanticweb.org\/files\/2018\/12\/dokieli-authoring-1xkaust.zip\">ZIP package as expected for the submission<\/a>). There is a list of&nbsp;<a href=\"https:\/\/github.com\/linkeddata\/dokieli\/wiki#examples-in-the-wild\">examples in the wild<\/a>.<\/p>\n\n\n\n<p>Authors that would like to self-publish can use any HTTP server. Authors, reviewers, and readers can use their own&nbsp;<a href=\"https:\/\/www.w3.org\/2005\/Incubator\/webid\/spec\/\">WebID<\/a>&nbsp;and Linked Data based personal storages, eg.&nbsp;<a href=\"http:\/\/github.com\/solid\/node-solid-server\/\">Solid<\/a>, with dokieli.&nbsp;<a href=\"https:\/\/gitter.im\/linkeddata\/dokieli\">Join the chat<\/a>&nbsp;if you need help.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">RASH<\/h3>\n\n\n\n<p>The&nbsp;<a href=\"https:\/\/github.com\/essepuntato\/rash\">Research Articles in Simplified HTML (RASH) format<\/a>&nbsp;allows one to easily prepare a scientific paper in HTML format (example:&nbsp;<a href=\"https:\/\/sparontologies.github.io\/article\/spar-iswc2018\/\">online<\/a>,&nbsp;<a href=\"https:\/\/iswc2019.semanticweb.org\/files\/2018\/12\/spar-iswc2018-1a5gcu8.zip\">ZIP package as expected for the submission<\/a>). It is composed by a few of the available HTML tags and allows one to&nbsp;<a href=\"https:\/\/rawgit.com\/essepuntato\/rash\/master\/documentation\/index.html#rdfa\">add RDF annotations<\/a>&nbsp;by means of Turtle, JSON-LD, RDF\/XML, and RDFa.<\/p>\n\n\n\n<p>Although one could directly write the HTML\/RASH syntax (<a href=\"https:\/\/rawgit.com\/essepuntato\/rash\/master\/documentation\/index.html\">see documentation<\/a>), one can create an Open Office Writer (ODT) or Microsoft Word (DOCX) document, and then convert it to HTML\/RASH using an online tool:&nbsp;<a href=\"http:\/\/dasplab.cs.unibo.it\/rocs\">rocs<\/a>. In summary:<\/p>\n\n\n\n<ul><li>Prepare your article in Open Office Writer (ODT) or Microsoft Word (DOCX), following the simple RASH guidelines for&nbsp;<a href=\"https:\/\/rawgit.com\/essepuntato\/rash\/master\/documentation\/rash-in-odt-simplified.odt\">ODT<\/a>&nbsp;and&nbsp;<a href=\"https:\/\/rawgit.com\/essepuntato\/rash\/master\/documentation\/rash-in-docx-simplified.docx\">DOCX<\/a>.<\/li><li>Use&nbsp;<a href=\"http:\/\/dasplab.cs.unibo.it\/rocs\">ROCS, the RASH online conversion service<\/a>&nbsp;to convert your ODT or DOCX document to RASH. This tool will produce a ZIP file with the RASH conversion of your paper (it also includes an LNCS-conforming LaTeX version of the article). This ZIP file can be directly submitted to EasyChair. If you prefer, you could also install the&nbsp;<a href=\"https:\/\/github.com\/essepuntato\/rash\/tree\/master\/tools\/rocs\">conversion tool locally on your machine<\/a>.<\/li><li>Optionally, if you want to extend the metadata of the paper,&nbsp;<a href=\"https:\/\/rawgit.com\/essepuntato\/rash\/master\/documentation\/index.html#rdfa\">add RDF annotations<\/a>&nbsp;to the HTML code.<\/li><\/ul>\n\n\n\n<p>If you choose to write HTML\/RASH manually (which makes sense when collaborating with your co-authors in a source code repository), note that the above-mentioned&nbsp;<a href=\"http:\/\/dasplab.cs.unibo.it\/rocs\">ROCS<\/a>&nbsp;can actually convert&nbsp;<em>any<\/em>&nbsp;RASH markup to LaTeX.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ScholarMarkdown<\/h3>\n\n\n\n<p><a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\">ScholarMarkdown<\/a>&nbsp;is framework for writing articles in the lightweight Markdown syntax, with automatic translation into HTML+RDFa, and the option to output&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/PDF-Compilation\">PDF<\/a>. It provides syntactic sugar to easily perform common tasks such as&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/Snippets#citations\">citing articles<\/a>, writing&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/Snippets#math-equations\">math equations<\/a>, and&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/Snippets\">more<\/a>.<\/p>\n\n\n\n<p>Note: ScholarMarkdown requires&nbsp;<a href=\"https:\/\/www.ruby-lang.org\/en\/documentation\/installation\/\">Ruby<\/a>&nbsp;to be installed.<\/p>\n\n\n\n<p>The Markdown-based source files enables straightforward versioning and collaborative editing with version-control systems such as git, and integrates nicely with automated&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/Self-publishing\">self-publishing via solutions such as GitHub pages<\/a>, as demonstrated by the&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\/Examples\">examples in the wild<\/a>.<\/p>\n\n\n\n<p>To get started, follow the&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown#quick-start\">quick start guide<\/a>, which will provide you with the the required LNCS template in Markdown (<a href=\"https:\/\/iswc2019.semanticweb.org\/files\/2018\/12\/scholarmarkdown-template-initial-1ukmyy2.zip\">Example of the initial template<\/a>). After&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown#3-compile-your-article\">compiling your Markdown files to HTML<\/a>, an&nbsp;<code>output\/<\/code>&nbsp;directory will be created (<a href=\"https:\/\/iswc2019.semanticweb.org\/files\/2018\/12\/scholarmarkdown-template-compiled-10hkhxq.zip\">Example of the compiled template<\/a>). This&nbsp;<code>output\/<\/code>&nbsp;folder contains a standalone version of your article in HTML, and this is the folder that must be submitted on EasyChair. Further details on ScholarMarkdown can be found on the&nbsp;<a href=\"https:\/\/github.com\/rubensworks\/ScholarMarkdown\/wiki\">wiki<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Acknowledgements<\/h2>\n\n\n\n<p>Adapted from the ISWC 2021 HTML Submission Guide. We would like to thank&nbsp;<a href=\"http:\/\/csarven.ca\/#i\">Sarven Capadisli<\/a>&nbsp;for his valuable contributions to these guidelines.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>ESWC 2022&nbsp;welcomes research articles employing the Open Web Platform. This document provides guidance to authors who wish to make their contributions available in HTML and related technology stack. General Guidance Contributions in HTML should be shared in EasyChair as a ZIP archive that contains the complete and self-contained content of the article. It should include [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/pages\/6764"}],"collection":[{"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/comments?post=6764"}],"version-history":[{"count":7,"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/pages\/6764\/revisions"}],"predecessor-version":[{"id":7361,"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/pages\/6764\/revisions\/7361"}],"wp:attachment":[{"href":"https:\/\/2023.eswc-conferences.org\/wp-json\/wp\/v2\/media?parent=6764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}