Objective: to enable researchers (in Web Science for example), to share and reuse research knowledge by employing the native Web stack.

Linked Research is set out to socially and technically enable researchers to take full control, ownership, and responsibility of their own knowledge, and have their contributions accessible to the society at maximum capacity, by dismantling the use of archaic and artificial barriers.

This is to work towards a solution where researchers can publish and consume research documents that are both human and machine-friendly.

See also a proposed acid test aimed at this.

There is a living documentation (“nightly”) published as part of this repository. It is not versioned.

Linked Research is a single HTML 5 Polyglot document. Different CSS are used to present the information for different media e.g., screen, print. JavaScript is used to progressively enhance the document and bring in interactivity. In a nutshell:

• Documents are human and machine-readable.
• Using the plain old semantic HTML marking process, with further semantic annotations using RDF and microformats.
• Intended to minimize friction in publishing and consuming; no installations, server, or account requirements. No out of band tooling. Works on local machine / Web browser.

See the examples in the wild in the wiki. Add your article's URL.

This repository is published and accessible from http://linked-research.270a.info/, e.g:

• http://linked-research.270a.info/{filename}
• ACM SIG Proceedings Paper
• LNCS Author Guidelines

The dependencies listed below are only enhancements, and so they are optional. Everything is still functional from ground up (whether you are using a Line Mode Browser or Firefox Nightly). If you do not want them, they can be removed or turned-off without effecting core HTML or CSS.

• jQuery Core (MIT License)
• html5sortable (MIT License)
• Shower (MIT License)

Apache License, Version 2.0

• Use it! Provide URLs to your work (see examples).
• Enable your colleagues to the same.
• Break things.
• Report issues and document.
• Resolve issues.
• Optimize.
• Work on features.