proto-DKR : Workflow

Short overview of the DKR workflow.

entering of a resource

The user visits a web page. The user can enter a URL (the link to the resource), a free text comment, a category (supportive towards DKRs, competition, tool system, human system etc.) and some free text keywords. + their name and email address, for verification.

viewing

The user can use expanded viewSpecs to choose what to see.

commenting

User reads a blog post or views a resource and wants to make comment. The user then clicks a button under the post of resource, labeled 'Supportive', 'Disagree' etc. The users email app is then launched with the 'Subject' filled in for the server to understand what the user was commenting on and what kind of comment it is. If the users email account is known, this comment is also listed in that users blog as well as being linked to the blog post or resource commented on. If not, the user gets to create an account.

HyperBlog Features

The HyperBlog term is a little misleading. Originally it was just a blog. Then we allowed the HyperBlog to work with the Hyperwords Menu and now we are using it for all the internal data storage and querying for in our effort to produce a proto-DKR

We could probably rename the HyperBlog the Hyper-DataBase-With-Conversation&OtherFeatures System. But that would be tiresome. So just remember that the HyperBlog system encompasses the whole blogging world; the resources being discussed as well as the discussion itself.

features

Easy blog text entry via email and web forms.
Easy multimedia entry, images sent via email.
Powerful view specifications, based on:
- Which blogs are to be seen, as more than one can be seen simultaneously, based on keywords.
- Outline generation.
- Paragraph level addressability.
URL which remembers all view settings.
Easily addressable blog posts; the address is the address to the blog subject.
Inter-linked comment system; all comments are also blogs.