[unrev-II] Re: Proj Launch Meeting Review

From: altintdev@webtv.net
Date: Mon Mar 27 2000 - 13:00:58 PST

  • Next message: Henry van Eyken: "[unrev-II] Re: Transcripts of Colloquium sessions (update - March 27))"

    From: altintdev@webtv.net

    Thanks Ron.

    Seeing your notes really brings home the fact of how hard it is to
    capture and organize data and information. I am seeing the picture a lot
    better now. The DKR is has 5 compartments, Experience, Learning,
    Knowledge, Node Map, and Problem(s). A late addition to this model is
    the DKR Problem. The DKR may (should) include a specific (set of)
    problem(s) so the users can focus efforts on what the DKR is intended to
    augment the solution of,!:)

    Each user node of the OHS attaches individually to the DKR inteface, as
    well as having a separate interface directly to other OHS nodes. This
    might look like sphere (the DKR) with 5 divisions, with OHS nodes
    looking like cylinders attached to the sphere at one end and a OHS user
    node sphere at the other, attached all around the surface with a web
    of external connections ouside the DKR connecting all OHS user nodes.

    Using your notes as an example, you would ue the OHS to submit your
    notes along with a list of external references to DKR Experience. The
    DKR adds the node and any connections to the node map, making it
    available to all OHS users. Collaboratively or individually, someone
    interested in design of iteractions with the user may find some
    references there and begin to accumulate snips of text and ideas from
    elsewhere on the WWW and unrev-II list archives. This author may then
    add some observations, maybe even compose a picture, then again submit
    this refinement to DKR Experience.

    Other contributors may add or focus the content until the group decides
    that this information item is complete enough and aligns with a DKR
    Problem sufficiently to warrent moving the item to DKR Learning. If this
    item contributes something that the group feels is adequate to actually
    provide a basis for action on a DKR Problem, then pertainent content is
    added to DKR Knowledge.

    Connections between evolving items are maintained sufficiently for a
    user to find source material. Absolute tracability is provided by the
    links from Knowledge items back through Learning and Experince nodes
    provided in three ways:

    1. By connections defined by contributors during the data/information
    2. By DKR internal associative mapping,
    3. Independent search by OHS tools.

    Since the DKR effort is cooperative, there may be less need to track
    individual contributions with great detail. Besides, any user could
    attach a link with commentary to any element of any item in the
    repository. In general, if the comment is on an Experience or Knowledge
    item, then it would be stored as an Experience node so that a user of
    Learning or Knowledge items could put the commentary in context.

    Best Regards,

    Alternative Interface Devices.
    Improve Accessibility and Utility of the WWW...

    GET A NEXTCARD VISA, in 30 seconds! Get rates as low as 2.9%
    Intro or 9.9% Fixed APR and no hidden fees. Apply NOW!

    Community email addresses:
      Post message: unrev-II@onelist.com
      Subscribe: unrev-II-subscribe@onelist.com
      Unsubscribe: unrev-II-unsubscribe@onelist.com
      List owner: unrev-II-owner@onelist.com

    Shortcut URL to this page:

    This archive was generated by hypermail 2b29 : Mon Mar 27 2000 - 13:08:20 PST