dokieli documentation

CC BY 4.0


This documentation is intended to help brave developers and authors. It explains dokieli's principles, architectural and design patterns.

Document Status

Living document.


Towards improving the write dimension of the read-write Web, dokieli's design subscribes to the following principles: freedom of expression, interoperability, decentralisation, evolvability, universal access, separation of concerns, █ + █ > = █ █.

Structure and Semantics

This section describes dokieli's practices, and offers some guidelines for developers and authors that would like to maintain uniformity in what they create. Consumers of dokieli should not treat the information here as a profile, or as a yet another super or subset of HTML+RDFa when they author or build new functionality. Creating articles, annotations, and notifications in dokieli is intended to be done through its UI, where it takes care of majority of the semantic content generation. The information here however can be useful for authors that would like to combine hand coding with the functionality that dokieli's UI provides. Takeaway what you find useful, there is no proprietary lock-in here.

dokieli adopts progressive enhancement strategy for the structural, presentational, and behavioural layers to allow content and base functionality to be accessible through different media and devices. The content in HTML+RDFa that dokieli produces is accessible (readable) without requiring any CSS or JavaScript, ie. text-browser safe. Breaking this "rule" in future development should be considered an anti-pattern (or a bug) in dokieli.

dokieli can serialise articles, annotations, and notifications in HTML+RDFa, Turtle, and JSON-LD, depending on server content-negotiation. Articles are represented in HTML+RDFa so that information is usable by both humans and machine consumers while maintaining lowest requirements for publishing, eg. a single URL with full payload in HTML+RDFa can be accessible from any HTTP server. No additional requirements necessary from clients (eg. JavaScript support and enabled) or servers (eg. additional RDF based content-negotiation). For annotations and notifications, dokieli first meets interoperability requirements (for protocols and vocabularies), and remains flexible about the serialisation that servers prefer. Similarly for consuming content, it can work with any of the serialisations as mentioned.

dokieli takes the approach of having all human-visible content in HTML, and all structured statements be made in context of their content in RDFa. This is optimal in avoiding data duplication in the same document which happens to be the case with the other serialisations in RDF. The approach also helps to avoid the creation and usage of multiple data islands, ie. separately for humans and machines. It is efficient in that it has no dependency on JavaScript in order to make the hidden machine-readable content be consumable from a human user interface. One exception to this rule is allowing authors to use the Embed Data feature to include Turtle, JSON-LD, or TriG data blocks for alternative reasons.

dokieli documents

Is there such thing as a "dokieli" document? Must there be?

An article may contain RDF classes like schema:CreativeWork sioc:Post prov:Entity schema:Article, otherwise, there is no unique data that would indicate that it is a "dokieli" document. If the HTML+RDFa representation includes dokieli.js and the DOM is ready, the DO: Object { C: {…}, U: {…} } will be available.
An annotation has the oa:Annotation class. It is possible to know that the article was rendered by dokieli: ?s oa:renderedVia <>, and we can assume that the annotation was created by it as well. This is not strictly true since that property could have been put there by something else. Annotations represented in HTML+RDFa do not include dokieli.js.
A notification may have one of the following classes: as:Announce, as:Like, as:Dislike, as:Relationship. Notifications represented in HTML+RDFa do not include dokieli.js.

HTML patterns

One of the goals of dokieli is not to impose arbitrary restrictions on type of nodes as well as the order they should be in HTML+RDFa. It has its own design patterns. It is an ongoing work to make dokieli as flexible as it can be on what it can consume. Ultimately, well-formed and valid HTML - along with accompanying RDFa, Turtle, JSON-LD, TriG etc - is the only requirement here. Take what you like:

Markup syntax
HTML5 Polyglot Markup is used to ensure that when content is processed or served as HTML or XHTML (text/html, application/xhtml+xml), they can generally be used in both HTML and XML ecosystems without further intervention. See also getDocument (dokieli.js) for details on DOM normalisation.
Unique identifiers (@id) may be placed on any element. Identifiers are auto-generated by normalising some input eg. sections use their heading's text content as input, tables from caption. Anything of importance should have an identifier, and aimed to be included for common patterns out of the box. @id values are reused in RDFa. See also generateAttributeId (dokieli.js) and its application in different places.
  • title is used.
  • main > article (querySelector) is considered to be the location of the primary content.
  • h1 is typically the first element node after main > article
  • There is a resource type, eg. schema:Article that can be found in main > article which is about the article. body may contain broad classes.
Sectioning is declared with section and typically have a heading, eg. h2 as its first child. Subsections may appear as a child of parent section, or as a child of div (which is a child of parent section), ie. section section or section div section. The headings of subsections are enumerated eg. section h2 would have a subsection with section h3. Sections ids and heading text are used to dynamically build the table of contents.
h2 and h3 are used for section titles, div as a typical wrapper (eg. for descriptions), as well as to contain further sub-sectioned content.
asides can technically appear anywhere, but tend to appear as the last element node in section, eg. for related content, footnotes. If the aside is introduced to the DOM via JavaScript for like annotations, they have a similar structure to section.
divs within section are used to wrap a block of arbitrary markup and content. See also RDFa below.
figures typically have figcaptions for things like audio, canvas, iframe, img, object, pre, video, math. For code scripts, figure class="listing" is used, and pre for the code itself with code The listing class is intended to have a collection of figures, which could also have a unique presentation, for example with line numbers or have its caption be prefixed with Listing and counter.
Snippet of section source code
Comparison of systems
d1 d2 d3 m1
Table columns list the dimensions: d1, d2, d3, and the measure: m1.
For mathematical equations figure class="equation" can be used to hint at an equation display. MathML base equation with <math xmlns=""> root can be included here (see also source). Alternatively, if MathJax JavaScript is available in the document, (La)TeX, eg. \lim_{x \to \infty} \exp(-x) = 0 and ASCIIMath, eg. sum_(i=1)^n i^3=((n(n+1))/2)^2, syntaxes can be input within the authoring mode (via Edit).
lim n x = 0
Embedding Turtle, JSON-LD, and TriG
Turtle, JSON-LD, and TriG syntaxes are placed within respective script blocks in head eg. <script id="meta-json-ld" type="application/ld+json" title="JSON-LD"></script>. Data is enclosed in CDATA sections. This pattern is detected, visible and editable from Embed Data in dokieli menu. See also showEmbedData (dokieli.js).
Multiple stylesheets can be included with @media, and when accompanied with @title, some user-agents can provide options for the user to switch between them, as well as from the dokieli menu, eg.
<!-- Primary stylesheet -->
<link href="media/css/basic.css" media="all" rel="stylesheet" title="Basic" />
<!-- Alternate stylesheet -->
<link href="media/css/acm.css" media="all" rel="stylesheet alternate" title="ACM" />
<!-- Applied by default-->
<link href="" media="all" rel="stylesheet" />
See also showViews (dokieli.js).
dokieli can consume and produce RDFa Core 1.1 syntax.
To preserve the order of content, @inlist is used eg. <section inlist="", <dd id="Sarven-Capadisli" inlist="" rel="bibo:authorList" resource="">.
A sections @id value is used as part of section's @resource as a fragment, eg. <section id="introduction" rel="schema:hasPart" resource="#introduction">. This allows the same identifier to be used for humans and machines, the value is derived from normalising its heading value as mentioned earlier.
Relating parts is done with rel="schema:hasPart", eg. sections with subsection:
<section id="structure-and-semantics" inlist="" rel="schema:hasPart" resource="#structure-and-semantics">
  <section id="html-patterns" inlist="" rel="schema:hasPart" resource="#html-patterns">
divs are used to hold a block of HTML markup and types of content together eg. <div datatype="rdf:HTML" property="schema:description" resource="#introduction" typeof="deo:Introduction"> makes it possible to declare that it contains HTML markup, and describes an introductory text.
Some of the prefixes (@prefix) on the body element are defined in the RDFa Core Initial Context. These prefixes are defined in dokieli for the purpose of being compact, robust, and to minimise potential errors for consumers.


There is a work in progress to have a distribution version of dokeli, requiring only dokieli.css and dokieli.js in templates.

Servers should use UTF-8 character encoding in their HTTP responses to articles, annotations, and notifications. <meta charset="utf-8" /> is used in HTML.


See also createNoteDataHTML (dokieli.js)

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="">
    <meta charset="utf-8" />
    <meta content="width=device-width, initial-scale=1" name="viewport" />
    <link href="" media="all" rel="stylesheet" title="Basic" />
    <link href="" media="all" rel="stylesheet" />
    <script src=""></script>

  <body about="" prefix="rdf: rdfs: owl: xsd: dcterms: dctypes: foaf: pimspace: cc: skos: prov: mem: qb: schema: void: rsa: cert: wgs: bibo: sioc: doap: dbr: dbp: sio: opmw: deo: doco: cito: fabio: oa: as: ldp: solid: acl: dio: rel:" typeof="schema:CreativeWork sioc:Post prov:Entity">
      <article about="" typeof="schema:Article">

Example article HTML

The subject of the following statements may be anywhere in a document. They tend to give some provenance level information and intended to bring more context and attract reuse of the document in different ways.

<dl id="document-identifier">
  <dd><a href="" rel="owl:sameAs"></a></dd>

The owl:sameAs indirectly gives this article, ie. any copy, an identifier. The identifier is typically where an article was originally made accessible from, so having this by default for copy distribution helps to keep its connection to source.

<dl id="document-inbox">
  <dt>Notifications Inbox</dt>
  <dd><a href="" rel="ldp:inbox">inbox/</a></dd>

ldp:inbox relation gives an article its own Inbox where it can receive notifications about eg. annotations or activities relevant to an article. The notifications can be consumed by applications to offer additional content and interactive possibilities. dokieli can both send and consume notifications by way of discovering an article's inbox. Notifications are created for activities like announcements, creating, (dis)liking, and consumed in order to be displayed in context of available content. The protocol to send and consume notifications in dokieli uses Linked Data Notifications.

<dl id="document-annotation-service">
  <dt>Annotation Service</dt>
  <dd><a href="" rel="oa:annotationService">annotation/</a></dd>

An article may refer to an annotation service (oa:annotationService) that conforms to the Web Annotation Protocol. See also DO.C.AnnotationService in dokieli.js.

<dl id="document-in-reply-to">
  <dt>In Reply To</dt>
  <dd><a href="" rel="as:inReplyTo">Call for Linked Research</a></dd>

If an article is a reply to objects(s), it can have a property like as:inReplyTo.

<dl id="document-published">
  <dd><time content="2017-02-27T00:00:00Z" datatype="xsd:dateTime" datetime="2017-02-27T00:00:00Z" property="schema:datePublished">2017-02-27</time></dd>

<dl id="document-modified">
  <dd><time content="2017-03-12T00:00:00Z" datatype="xsd:dateTime" datetime="2017-03-12T00:00:00Z" property="schema:dateModified">2017-03-18</time></dd>

Dates, you know.. kinda useful. The example above duplicates the ISO date in @content and @datetime, but only one needs to be there, given that there parsers for different RDFa versions.

<dl id="document-license">
  <dd><a href="" rel="schema:license" title="Creative Commons Attribution 4.0 Unported">CC BY 4.0</a></dd>

Nice to declare a license or rights to signal under what conditions the document may be reused, reshared or remixed, eg. via Creative Commons license. Articles and notifications tend to use schema:license and annotations use dcterms:rights (given Web Annotation Vocabulary).

<dl id="document-derived-from">
  <dt>Derived From</dt<
  <dd><a href="" rel="prov:wasDerivedFrom"></a></dd>

<dl id="document-derived-on">
  <dt>Derived On</dt>
  <dd><time datetime="2017-08-06T00:29:45.342Z">2017-08-06T00:29:45.342Z</time></dd>

If a document is derived from another using the Save As operation, derived from and derived on information is declared.

The markup for an anonymous profile is like:

<span typeof="schema:Person">Lunatic Scholar</span>

The markup for a WebID profile including their name:

<span about="" property="schema:name">Sarven Capadisli</span>

If they have an image:

<img alt="" height="48" rel="schema:image" src="" width="48" />

Progressively described name, image, and URL is useful in templates:

<span about="" typeof="schema:Person"><img alt="" height="48" rel="schema:image" src="" width="48" /> <a href="" rel="schema:url"><span about="" property="schema:name">Sarven Capadisli</span></a></span>

Alternatively applying the DRY principle:

<a about="" href="" property="schema:name" rel="schema:url" typeof="schema:Person">Sarven Capadisli</a>

If they are one of the authors of a document, the profile can be wrapped like:

<dd id="Sarven-Capadisli" inlist="" rel="bibo:authorList" resource=""><span about="" rel="schema:creator schema:publisher schema:author"><!-- profile --></span></dd>

See also getUserHTML (dokieli.js)


Annotations have their own URL, fetched, parsed, and then introduced into the DOM. They are normally appended at the bottom of a node (section) in which the annotation has a reference to. It is not required to introduce all of the annotation content into the DOM, nor all of it has to be human-visible. This is a run-time inclusion and typically included within <aside class="note do"></aside>. Write operations like Save, Save As, Export will exclude this (class~="do") when it normalises the DOM to HTML.

Currently dokieli uses oa:replying, oa:commenting, oa:describing, oa:assessing, oa:bookmarking for motivations, and oa:describing and oa:tagging for annotation purpose.

See also createNoteDataHTML (dokieli.js)

Here is an annotation resource at with all information human-visible and machine-readable (HTML+RDFa):

A reply Web Annotation with replying motivation

Its source:

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="">
    <meta charset="utf-8" />
      <article id="b6738766-3ce5-4054-96a9-ced7f05b439f" about="i:" typeof="oa:Annotation" prefix="rdf: schema: dcterms: oa: as: i:">
        <h1 property="schema:name">Sarven Capadisli <span rel="oa:motivatedBy" resource="oa:replying">replies</span></h1>

        <dl class="author-name">
          <dd><span rel="schema:creator"><span about="" typeof="schema:Person"><img alt="" height="48" rel="schema:image" src="" width="48" /> <a href="" rel="schema:url"><span about="" property="schema:name">Sarven Capadisli</span></a></span></span></dd>

        <dl class="published">
          <dd><a href=""><time datetime="2017-04-15T21:24:58.293Z" datatype="xsd:dateTime" property="schema:datePublished" content="2017-04-15T21:24:58.293Z">2017-04-15 21:24:58</time></a>

        <dl class="rights">
          <dd><a href="" rel="dcterms:rights" title="Creative Commons Attribution">CC BY 4.0</a></dd>

        <dl class="canonical">
          <dd about="i:" rel="oa:canonical" resource="urn:uuid:48355bb0-0afd-4f73-9a18-f1e8b6fb415b">48355bb0-0afd-4f73-9a18-f1e8b6fb415b</dd>

        <dl class="target">
          <dt><a href="" rel="oa:hasTarget">In reply to</a> (<a about="" href="" rel="oa:hasSource" typeof="oa:SpecificResource">part of</a>)</dt>
            <blockquote about="" cite="">
              <div rel="oa:hasSelector" resource="i:#fragment-selector" typeof="oa:FragmentSelector">
                <dl class="conformsto">
                  <dt>Fragment selector conforms to</dt>
                  <dd><a property="rdf:value" content="abstract" xml:lang="" lang="" rel="dcterms:conformsTo" href="">RFC3987</a></dd>

                <dl class="refinedby" rel="oa:refinedBy" resource="i:#text-quote-selector" typeof="oa:TextQuoteSelector">
                  <dt>Refined by</dt>
                  <dd><span property="oa:prefix" xml:lang="en" lang="en">rchitecture and implementation, </span><mark property="oa:exact" xml:lang="en" lang="en">demonstrating advanced document authoring and interaction without a single point of control</mark><span property="oa:suffix" xml:lang="en" lang="en">. Such an environment provides t</span></dd>

        <dl class="renderedvia">
          <dt>Rendered via</dt>
          <dd><a about="" href="" rel="oa:renderedVia">dokieli</a></dd>

        <section id="note-b6738766-3ce5-4054-96a9-ced7f05b439f" rel="oa:hasBody" resource="i:#note-b6738766-3ce5-4054-96a9-ced7f05b439f">
          <h2 property="schema:name">Note</h2>

          <dl class="rights">
            <dd><a href="" rel="dcterms:rights" title="Creative Commons Attribution">CC BY 4.0</a></dd>

          <div datatype="rdf:HTML" property="rdf:value schema:description" resource="i:#note-b6738766-3ce5-4054-96a9-ced7f05b439f" typeof="oa:TextualBody">What are you trying to tell me? That I can dodge bullets?</div>
Example annotation HTML
<dl class="canonical">
  <dd rel="oa:canonical" resource="urn:uuid:48355bb0-0afd-4f73-9a18-f1e8b6fb415b">48355bb0-0afd-4f73-9a18-f1e8b6fb415b</dd>

oa:canonical refers to a canonical IRI that can be used to deduplicate the annotation. If an user chooses to store their annotation at their personal Webspace as well as when an annotation service (if offered), dokieli treats the resource at personal space as the canonical, and the resource at the annotation service as the copy where it refers to the personal space (oa:via).

If an annotation resource is introduced to the article's DOM as part of an aside, they have a structure similar to an article, and may be displayed in different ways, eg. in marginalia:

<aside class="note do">
  <blockquote cite="">
    <article about="i:" id="461819979" prefix="i:" typeof="oa:Annotation">
    <!-- Reconstruction of the original annotation (from RDF) -->

An inline reference to that annotation as aside would have a structure like:

<span class="ref do" rel="schema:hasPart" resource="#r-461819979" typeof="dctypes:Text"><mark id="r-461819979" property="schema:description">demonstrating advanced document authoring and interaction without a single point of control</mark><sup class="ref-annotation"><a rel="cito:hasReplyFrom" href="#461819979" resource="">💬</a></sup></span>

Note that the human-visible anchor hyperlinks (#461819979) to the annotation aside id="461819979".


Notifications are discovered from LDN Inboxes. An article (or a fragment within) may have an inbox relation (ldp:inbox) which helps dokieli to discover it, and then fetch the notifications.

Notifications are intended to be brief, giving sufficient information for consumers to decide if they want use to them. If the notifications are generated by dokieli, eg. via an annotation activity, they typically include some provenance level data like generation date, actor that triggered it, license, where the annotation can be found, what it annotated, and the motivation for it. Notifications will not include the annotation body, but consumers can fetch their URLs (as mentioned in the annotation section).

See also createNoteDataHTML (dokieli.js)

Here is a notification resource at with all information human-visible and machine-readable (HTML+RDFa):

A notification referring to an annotation

Its source:

<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="">
    <meta charset="utf-8" />
    <title>Notification: Announced</title>
  <body prefix="xsd: rdf: as: oa: schema:">
        <h1>Notification: Announced</h1>
          <dl about="">
            <dd><a about="" href="" typeof="as:Announce">Announce</a></dd>

            <dd><a href="" property="as:object"></a></dd>

            <dd><a href="" property="as:target"></a></dd>

            <dd><time datetime="2017-04-15T21:31:45.711Z" datatype="xsd:dateTime" property="as:updated" content="2017-04-15T21:31:45.711Z">2017-04-15 21:31:45</time></dd>

            <dd><a href="" property="as:actor"></a></dd>

            <dd><a href="" property="schema:license"></a></dd>

          <dl about="">
            <dt>Object type</dt>
            <dd><a about="" typeof="oa:Annotation" href="">Annotation</a></dd>

            <dd><a href="" property="oa:motivation">replying</a></dd>
Example notification HTML

User interface

Document modes

There UI adapts to the document mode the user is in: author, review, social. By default the social mode is engaged. The dokieli menu allows the user to engage the author mode through the Edit operation, and the review mode with Review. See also setDocumentMode (dokieli.js).

dokieli menu

Sign in
This is where the user can enter their WebID to let dokieli know about who they are. dokieli fetches their WebID and related information to further help with dokieli's operations. Authentication is not done at this stage.
User can share the current article or a part of it with their contacts, automatically discovered via foaf:knows as well as traversing equivalent profiles (owl:sameAs). Notification can also be sent to specific targets by entering their IRIs. dokieli sends a notification to the selected targets with information like: who sent it, when, license, motivation.
An article can be replied with a note and have its own license. To choose the location of the reply, the resource browser can be used on personal storage or an annotation service.
This feature changes the document mode to Review and gives different context for annotations. When a user selects a span of text, a toolbar provides the following options to motivations:
General agreement with the selected text. Optional text should specify why it is a strong point or a convincing argument.
General disagreement with the selected text. Optional text should specify why it is a weak point, an error, or inaccurate.
Request to increase specificity on selected text. Optional text should indicate that a citation or more specificity is needed.
This feature allows a new document to be created at specified location. The new document is constructed based on If the user is signed in with their WebID and their personal storage location is identifier, the default location for the new resource will have the storage URL (pim:storage) as its base. If the user does not have a WebID and a storage, and if the article refers to an annotation service (oa:annotationService), it will use that URL instead. The URL can be input directly, and otherwise a name will be autogenerated for the resource. This feature uses the resource browser to navigate HTTP URLs. See also generateAttributeId (dokieli.js). On create, the resulting hyperlink will be shown and a new tab in the browser will be prompted.
Documents can be opened from a local filesystem or by entering an HTTP URL. Both options read the resource's content, and if dokieli's CSS and JavaScript are not present, they are included before updating the DOM and initiating dokieli. This feature uses the resource browser to navigate HTTP URLs. See also openDocument (dokieli.js).
This feature makes a write operation (HTTP PUT) request to the current location of the document (window.location). The document is normalised in that dokieli related items are removed from the DOM before making the request.
Save As
The Save As operation is similar to New for normalising some of the URLs and same as Save operation for normalising the DOM before making the request to specified location. If Derivation data is checked for inclusion, derived from and on information is included in the created document. This feature uses the resource browser to navigate HTTP URLs.
Provides options to 1) exports the article as HTML and save to filesystem, 2) Makes a request to the Internet Archive to crawl all resources references in this article.
Requests to print the current document (window.print()).
Editor is one of the document modes a user can be in. The available features reflect the edit operation. Edits reside in the DOM until a Save or Save As is triggered. There are several editor features in following categories: content formatting and structuring (2, 3, 4, , , , , code, , , , , ), including interactive and embeddable objects (), inline semantic relations (), footnotes and citations (), and annotations ().
Users can edit the current state of the article. Updating, only updates the DOM, and leave the saving to Save or Save As.
Embed Data
This feature allows hidden RDF data to be stored with the document. Turtle, JSON-LD, and TriG can all be edited and stored independently.

To determine the base URL, when new documents are created or saved as, media resources from head link, [src], object[data] (querySelector) will have their URLs normalised to use current document's base URL as its absolute URL (this is the Use references as is option). If Copy to your storage is selected, relative URLs will not be updated as the copy operation reuses the same file paths when resource are copied to destination. The copy operation does an HTTP GET for each source, then HTTP PUT to target.

The resource browser eg. available for New, Open, Save As operations can be used to navigate through a Webspace. It does this by using the Linked Data Platform's containment rules to retrieve and then display the container's index. If the user's personal storage location is known, it will be used as default location for the resource browser. Alternatively, if the article refers to an annotation service, it will be used as start location.

Users are given a choice to specify the rights and license for their annotations from a list of Creative Commons licenses, eg. CC BY 4.0. If applicable, the notification payload will use the CC0 1.0 Universal license.

The dokieli menu will list primary and alternate stylesheets that are detected in HTML. Native is always available and it will essentially disable all other stylesheets, thereby user-agent's default stylesheets are gets applied. When a view is selected, eg. Basic (which happens to be the one that is used on this article as primary), it becomes the primary stylesheet, and the rest of the stylesheets become alternate and disabled.

HTTP operations

dokieli conforms to Linked Data Platform (LDP) protocol for create, update, and delete operations.

Article operations like New, Save, Save As, Reply use HTTP PUT, Review and other annotation operations use HTTP POST.

Notifications are sent with HTTP POST. Save and Save As normalises the HTML before sending.

Request to send
HTTP method(s) Content-Type
AnnotationOPTIONS, POSTtext/html, application/ld+json, text/turtle
NotificationOPTIONS, POSTtext/html, application/ld+json, text/turtle
Articles typically use text/html with embedded RDFa. Where a server implements GET with text/html, and allows PUT for writing, the assumption is that it can allow text/html. In the future, dokieli can check for the Accept-Put header with OPTIONS to determine a suitable type. At this time, HTML+RDFa is an important default for articles.
Annotations use the POST method with Content-Type header value determined by type of location to write to: personal storage space eg. given a profile's pim:storage; made to an annotation service eg. an article's oa:annotationService; sent to profile's outbox's outbox: as:outbox. The Web Annotation Protocol requires application/ld+json by default. dokieli sends an OPTIONS request to check for the Accept-Post header and sends the payload in one of the serializations that the server prefers. If it is not set, it will fallback to application/ld+json as preferred by Wen Annotation and ActivityPub.
Notifications use OPTIONS to check the response's Accept-Post HTTP header. If it is set and matches one of the acceptable RDF mediatypes that dokieli can parse, it will use that mediatype to serialize the payload before POSTing. If it is not set, it will fallback to application/ld+json as required by the Linked Data Notifications specification.

Due to Mixed Content implementations in Web browsers, ie. fetching of content over unencrypted or unauthenticated connections in the context of an encrypted and authenticated document, is subject to being blocked by the Web browser. Hence, an https document (eg article at https) will not be able to use the contents of an http document (eg. an http WebID). As a workaround, dokieli uses a proxy endpoint by default in order to use the contents of an http resource. An https document fetching an https resource will not use the proxy.


dokieli was originally intended to handle different authentication mechanisms. WebID-TLS is currently supported to authenticate with servers.


Personal storage
WebID's with pim:storage can get to use their personal online data storage with dokieli's read-write operations, eg all annotations, Reply, Review, New, Save As.
Local storage
There is a Local Storage feature which uses user-agent's window.localStorage, with default 1m autosave.

Web Extension

The dokieli Web Extension is a minimal package of dokieli which contains the core CSS and JavaScript that works as a browser add-on. When user triggers it from their browser toolbar, it provides the same functionality as a single-page application, ie. initialised and rendered in the browser DOM.

Currently the extension works with Firefox and Chrome/Chromium browsers. Two ways to do this:

  1. Extensions are available from Add-ons for Firefox and Chrome Web Store.
  2. Clone and import directory:
    • Firefox: Load Temporary Add-on from Add-ons (or go to about:debugging from addressbar) and import by selecting a file from the directory (eg manifest.json). See also temporary add-on installation.
    • Chrome/Chromium: Check the developer more option, under Extensions (or go to chrome://extensions/ from addressbar) and import the directory.


git clone
cd dokieli

# Install packages
npm install

# Build stuff eg. scripts/dokieli.js
npm run build

# or automatically rebuild when files change
npm run watch