HTML Submission Guide
HTML submissions should be submitted to EasyChair as a ZIP archive that contains the complete content of the paper. It should include a main “index.html” and all used resources to guarantee a correct vizualisation of the document on web browsers. Note that the full content of the paper should be readable offline (no external sources must be used), and the use of any kind of tracking system that may identify readers is totally forbidden.
Authors can use any HTML-based format for the submission, but a mandatory LNCS-like layout should be provided. The submission still needs to comply with the established page limit. To check if your HTML submission is compliant with the page limit constraint, please print or export the LNCS-like layout to PDF.
Authors who are new to HTML submissions may consider to use either dokieli or RASH, detailed below. Both tools can help produce well formatted academic papers using HTML and are capable of rendering papers in the LNCS layout. You can also find other pointers hosted by the W3C Scholarly HTML community group.
Final (“camera-ready”) version
Formatting requirements for the final version differ by call.
- Papers accepted in the Research, In-Use, and Resources tracks 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 papers that have been accepted for publication in LaTeX or Word format. If a paper submitted in HTML is accepted, the authors can choose to do this step manually or using tool support as outlined below.
- Papers accepted in the Posters & Demos track and in the Doctoral Consortium will be published as CEUR-WS.org proceedings volumes. CEUR-WS.org allows paper to be in HTML but, for guaranteed printability and archiving, requires an additional PDF, which should be a print-out of the HTML paper in the LNCS layout.
- Papers accepted in the Industry track will be published on the conference website. The same “HTML+PDF” rule applies as explained above for posters, demos and doctoral papers.
dokieli is a client-side editor for decentralized article publishing in HTML+RDF annotations and social interactions, compliant with the Linked Research initiative (see an example of an article using the LNCS author guidelines) .
dokieli includes a variety of features such as annotations, e.g., replies, peer-reviews, liking, resharing, bookmarking (implements W3C Web Annotation model) and notifications (implements W3C Linked Data Notifications). The following steps devote to simple writing:
- If you have a WebID and a personal online storage, you can author your documents wherever you like on the Web, and you can decide who gets to read and write, e.g., your co-authors, or reviewers.
For any help join the chat.
The Research Articles in Simplified HTML (RASH) format allows one to easily prepare a scientific paper in HTML format (see an example of a paper in RASH). It is composed by a few of the available HTML tags and allows one to add RDF annotations by means of Turtle, JSON-LD, RDF/XML, and RDFa.
Although one could directly write the HTML/RASH syntax (see documentation), the simplest way to produce RASH is to use the native RASH wordprocessor, i.e. RAJE (https://rash-framework.github.io/raje-app/), available for Mac OS X, Windows, and Linux.
Alternatively, one can create an Open Office Writer (ODT) or Microsoft Word (DOCX) document, and then convert it to HTML/RASH using an online tool: http://dasplab.cs.unibo.it/rocs. In summary:
- Prepare your article in Open Office Writer (ODT) or Microsoft Word (DOCX), following the simple RASH guidelines for ODT and DOCX.
- Use ROCS, the RASH online conversion service 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 conversion tool locally on your machine.
- Optionally, if you want to extend the metadata of the paper, add RDF annotations to the HTML code.
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 ROCS can actually convert any RASH markup to LaTeX.