So far I have used an abstract model to identify DKS/OHS interactions.
I used this figure.
The Goal(s) or Problem(s) serve to focus use of the DKR, and
the Node Map provides navigation and attribution within the DKR.
Experience, Learning, and Knowledge represent
categories of information with each having a
relatively higher level of refinement or evolution.
It is fundamental that the DKR can contain any number of categories,
each having a well defined or no relationship to other categories.
The categories in this DKR example are chosen from some of the
best examples I have seen so far, almost totally inspired by
Douglas Engelbart and my association with this unRev2 program.
To show a use case sequence I start with an information item
distilled from the Data/Information universe
and submitted by a collaborator.
and progress to an action taken by a collaborator
to achieve a DKR goal.
Given that the DKR goal can be won
by development of necessary knowledge
on which to base an action,
I used the term Wisdom to describe the
action of using that knowledge
to achieve the goal.
Showing feedback in the process,
the action of
exhibiting Wisdom to achieve the goal,
even if completely successful,
will certainly generate new Data/Information
to be brought into the DKR.
So a linear sequence
from the point of view of an information item
is entry through Experience,
processing into a Learning issue
that supports a Knowledge proposition
used to take an action
which results in. at least, more Data/Information
and, if captured, new Experience.
Inside the DKR, an information item appears to follow
an orderly flow from
a contributor submitting some item
as an Experience,
to being incorporated into a Learning program,
that supports a Knowledge item
used as basis
for action taken to achieve a goal.
We might take it for granted that exhibition of Wisdom would add some Data/Information to the environment. The actual interactions between information items, between information items and collaborators, and between collaborators as input is processed toward a goal will be complex. First, notice that even if the rule is: "Any new item must be input to the Experience category", its promotion to a Knowledge category may be by immediate concensus or by a long process of establishing context with other items. These paths and relationships must be maintained over the life of the DKR.
The OHS is shown as individual nodes attached to the DKR.
Communication between collaborators may take place using connections
internal to the DKR
and by external connections having no connection with the DKR.
Along with discussion related to sharing of DKR/OHS resources
to provide interactive collaboration,
Lee Iverson introduces
the concept of DDOM,
Distributed DOM.
This gives the OHS access to structures and events
of DKR information items
between DKR users. Status and, where appropriate, content
of any document registered in any DKR can be determined
by communications between collaborators outside the DKR,
or by direct interaction with the DKR.
concept, subject, temporal, inference, flow, attribution, relationship, equivalence maps.
Another reference: Gene Bellinger, OutSights
4/27/00 4/29/00 5/7 11/05