Structured wiki

One direction for collaborating on the web has been Federated Wiki, as described in the ISSS 2019 Corvallis workshop, . However, this form of wiki is rather unstructured (e.g. free-flowing paragraphs and lists) rather than structured.

I’ve been searching on “structured wiki” to see if there are alternatives.

Twiki seems to be a grandfather in structured wikis, dating back to 1998 and written in Perl, see Wikipedia. There was a fork in 2008 leading to a new Foswiki community as an alternative.

In a TWiki versus Foswiki scan in October 2018, the number of site combined are in the hundreds. It’s noted that In a shared hosting environment, TWiki works “out of the box” whereas Foswiki requires some Perl modules that may not be installed by default.

Appreciating ways in which an unstructured text wiki differs from structured is described at What is a “structured wiki”, and what does it mean in Foswiki?

In a more active wiki development community – builtwith counts 25,680 sites – Dokuwiki is available on most shared hosting providers as a PHP package with a one-button installation. (I’ve used it many times, myself).

There’s a struct plugin for Dokuwiki. Further, there’sa series of research publications by Voigt and Gohr that report on their evolution with the technology.

ICKEwiki was created in a two year research project in coorperation the Fraunhofer societies IFF Magdeburg and ISST Berlin and the University of Technology and Commerce Berlin (HTW). It is based on DokuWiki and was created and tested in close cooperation with three pilot companies.

… says

ICKEwiki (in German) is offered as service, supporting Dokuwiki with Struct (and presumably other plugins).

For a small collaborative project, Dokuwiki with Struct could be an easy way to collect and maintain small amounts of structured data.

This plugin?

On Dokuwiki, the Semantic Plugin allows the user to “Add semantic data to your DokuWiki for SEO”. That includes only the Dublin Core schemas, and not user-defined schemas.

As an example, if we used the Alexandrian pattern language definition of “solution to a problem in context”, we could create a structured wiki with (i) solution; (ii) problem; and (iii) context. That’s not in Dublin Core.

On my Wordpress blogs, I added the “Markup (JSON-LD) structured in” plugin last month. So, it’s now semantically clear that a web page is a post (or something else). However, that doesn’t say much about the content that is in the blog post.