Sarven Capadisli

An `https:` based request URI may have response content using `http:` based URI. dokieli should treat them as equivalent (as fallback). First look for https sameAs http and vice-versa.

When a citation is made to a URI which was already cited, dokieli repeats the same process ie. fetches and updates the document; inline text and the references section. Hence,...

On 'Save As' dokieli takes the user input for inbox and annotationService to update the derived document before saving. It is possible that the user specifies URIs for inbox/annotationService that...

Real-time multi-author editing

8

This is going to be a tough one (some issues on concurrency and versioning...) but quite important if we can have multi-authors editing an article simultaneously.

Derived from https://github.com/linkeddata/dokieli/issues/188 . If an annotation has its own `oa:annotationService`, use that to find reactions to the annotation.

Apply user's preferred language to dokieli items

1

Depending on the `DO.C.Lang` value, apply the language for all human-readable content eg. menus, common items that go into the document. This requires all human-readable content to be moved into...

Handle WebID without information at sign in

1

At minimum a WebID is an Agent, and maybe has a name, avatar etc.. If no statement about the WebID is found, the user is currently signed in as "anonymous"...

Improving the dokieli UI using solid-auth-client

2

dokieli is currently (v0.3.20) using https://github.com/solid/solid-auth-client/ to handle WebID-OIDC based authentication. User clicks 'Sign in' from the dokieli menu, and then presented with "OpenID Connect" the option to sign in....

Apply user's preferred license to the UI

2

Apply a user's preferred license (where some information is gathered from their profile) to the UI. So that it is auto-selected for their annotation. Also keep previously selected in memory.