Publishing my papers as Linked Research

I intend to make the extra effort of republishing my own research papers as Linked Research, i.e. in a form readable by humans (HTML5), but also embedding meta-data (as RDF) for machine processing.

I’ve started with Authoritative Linked Data descriptions of Debian source packages using ADMS.SW (a good candidate, as it deals with Linked Data ;).

You’ll notice the menu which helps select different style sheets for preparing clean printable versions, not far from the LaTeX output usually converted to PDF.

I hope this will pave the way to more Linked Research, and less opaque publications.

The only hassle at the moment is the conversion from LaTeX to HTML5 which I’m doing manually, in Emacs + nxml-mode.

Update: Check the preprint links in my publications page, for more papers.

This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

5 Responses to Publishing my papers as Linked Research

  1. Zoggy says:

    Hello,

    You could give a try to Stog
    with the Stog-RDF plugin.

    Here is an introduction to the implemented ideas (in french):
    http://www.oranadoz.net/posts/publier-et-braconner.html
    http://www.oranadoz.net/posts/publier-et-braconner-2.html

  2. @Zoggy: interesting. I’m not a big fan of OCaml though… maybe something along those lines could be preferable, but POSH will do for now (http://microformats.org/wiki/posh)

  3. Zoggy says:

    In fact, you don’t need at all to know OCaml, only if you want to add your own plugins for complex rules. And you can already include RDFa and/or use semantic-xhtml in your templates. So you can choose which way you add semantic to your publications: POSH, RDFa, separate RDF graph…

  4. @Zoggy: interesting… but what I’m afraid mainly is to stumble upon bugs or lack of maintenance and to have to dive into its code anyway… so I’d better chose something I’m able to maintain/debug or whose community I’m more connected. YMMV of course 😉

  5. Zoggy says:

    I understand your argument. That’s the same reason that made me keep an XML syntax, so that if one day I want to switch to another system, I should be able to do so without a lot of pain, my documents being already mainly semantic-oriented.

Leave a Reply

Your email address will not be published. Required fields are marked *