HTML Submission Guide

ISWC 2022 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 a main ā€œindex.htmlā€ 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:

  • HTML template: any tooling or process can be used to produce the HTML.
  • 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.
  • 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.
  • Privacy: scripts must not be used to identify or track readers.
  • View: the rendered article (HTML+CSS) should have the ā€œlook and feelā€ 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.

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.

Final (ā€œcamera-readyā€) version

Formatting requirements for the final version differ by call.

  • Articles 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 articles that have been accepted for publication inĀ LaTeX or Word format. If an article submitted in HTML is accepted, the authors can choose to do this step manually or using tool support as outlined below.
  • Articles accepted in the Posters & Demos track and in the Doctoral Consortium will be published asĀ CEUR-WS.orgĀ 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.
  • Articles 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.

Recommendations

We recommend that authors take the following steps independently of the general process:

  • Before sharing your article with ISWC, self-publish your HTML version, eg. at a repository, personal or institution website thatā€™s publicly accessible and archivable from a URL.
  • Include the URL of your self-published article along the lines of: ā€œIdentifier: http://example.org/article ā€œ 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.
  • Consider using aĀ Creative CommonsĀ license likeĀ CC BY 4.0Ā on the self-published version.
  • Create multiple archived copies of the self-published version using on-demand free archive services likeĀ archive.org,Ā archive.is.
  • If you intend to also publish the ā€œAuthorā€™s Accepted Manuscriptā€ version following peer-review, note Springerā€™sĀ self-archiving policy.
  • Send a notification about your original self-published article to theĀ Linked Open Research CloudĀ (LORC) to improve the discoverability of your article.
  • For additional help, authors are welcome toĀ join the public chatĀ onĀ Linked Research. 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.
  • Authors are encouraged to use tooling and processes that work best for them.

dokieli

dokieliĀ is a client-side editor for decentralized article publishing in HTML+RDF annotations, notifications, and social interactions. It implements W3C Recommendations likeĀ Web Annotation,Ā Linked Data Notifications, andĀ ActivityPub.

TheĀ LNCS author guidelinesĀ can be used as template (ZIP package as expected for the submission). There is a list ofĀ examples in the wild.

Authors that would like to self-publish can use any HTTP server. Authors, reviewers, and readers can use their ownĀ WebIDĀ and Linked Data based personal storages, eg.Ā Solid, with dokieli.Ā Join the chatĀ if you need help.

ScholarMarkdown

ScholarMarkdownĀ is framework for writing articles in the lightweight Markdown syntax, with automatic translation into HTML+RDFa, and the option to outputĀ PDF. It provides syntactic sugar to easily perform common tasks such asĀ citing articles, writingĀ math equations, andĀ more. Note: ScholarMarkdown requiresĀ RubyĀ to be installed.

The Markdown-based source files enables straightforward versioning and collaborative editing with version-control systems such as git, and integrates nicely with automatedĀ self-publishing via solutions such as GitHub pages, as demonstrated by theĀ examples in the wild.

To get started, follow theĀ quick start guide, which will provide you with the the required LNCS template in Markdown (Example of the initial template). After compiling yourĀ Markdown files to HTML, an output/ directory will be created (Example of the compiled template). This output/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Ā wiki. Acknowledgements

We would like to thankĀ Sarven CapadisliĀ for his valuable contributions to these guidelines.