CONTACTS 

SUBJECTS
Difficult KM Hard to Design, Not Understood
Core Capability KM Not Understood, Eric Armstrong
KM Not Understood Secret of SDS
XML OHS Design Ken Holeman New Contributor
Holeman, Ken, Meeting on Using XML for KM Design, Eric Submits Notes
OHS/DKR Meeting at Doug Engelbart's House with Ken Holman on XML
XML -> OHS Browser, Grant Bowman, 000812
XML Data Format
XML Translate from Text, HTML, Multiple Views, 000824
Meeting Notes OHS/DKR on 001114
XML Transcoding Scope Reviewed, Rather than Convert Documents Point t
Transcode Translate, 000405

1814 -    ..
1815 - Summary/Objective
1816 -
181601 - Follow up ref SDS 48 0000, ref SDS 47 0000.
181602 -
181603 - The meeting today considered leaving legacy documents in tact.  Rather
181604 - than translate them into XML documents, the new system would provide
181605 - pointers to the documents, and a viewer would display them.
181606 - ref SDS 0 5Y6G  There was also consideration to modifying definitions
181607 - of components, but the basic objectives of the project are unchanged.
181608 - ref SDS 0 4FYW
181609 -
181610 -     [On 001115 Eric Armstrong submitted notes on the meeting today.
181611 -     ref SDS 49 0001
181612 -
181613 -
181614 -
181615 -
181616 -  ..
1817 -
1818 -
1819 - Progress
1820 -
182001 -  ..
182002 - Transcoding Scope Change Reviewed
182003 - XML Applied for Data Interchange; Use Pointers for Legacy Documents
182004 -
182005 - Follow up ref SDS 48 5Y6G.
182006 -
182007 - In a continuation of Saturday's meeting, Ken Holman met again with
182008 - several members of the OHS design team.
182009 -
182010 - The design focus is shifting from transcoding every document into a
182011 - common XML form.  Current planning is to define functional interfaces,
182012 - then figure out XML for data interchange.  Rather than conceptualize
182013 - OHS as XML-versions of documents, we're thinking of a repository that
182014 - contains pointers to legacy-documents, plus additional data to provide
182015 - OHS services. ref DRP 2 GK5K
182016 -
182017 -     [On 001115 Eric Armstrong submitted notes on the meeting today.
182018 -     ref SDS 49 0001
182019 -
182020 -     [On 001124 Ken submits clarifications on limitations of XML for
182021 -     OHS/DKR development. ref SDS 51 0001
182022 -
182023 - Key advantages...
182024 -
182025 -   1.  Others can innovate on the implementation, using different
182026 -       internal representations to provide the requisite functionality
182027 -       in a way that preserves interoperability. ref DRP 2 WP7F
182028 -
182029 -   2.  "Viewer" for legacy documents. (E.g. word documents
182030 -       spreadsheets, diagrams, etc.) can be developed. People who are
182031 -       close to those formats can build specific viewers, while the OHS
182032 -       provides a common ground for additional data necessary to use
182033 -       them effectively. ref DRP 2 XQ7K
182034 -
182035 -         On 001025 the viewer is a Hyperscope under original Launch
182036 -         Plan, ref SDS 42 T3D8  Below, there is consideration to modify
182037 -         scope for Hyperscope and OHS. ref SDS 0 4FYW
182038 -
182039 -   3.  Views stored in the OHS. Over time, the OHS becomes more and
182040 -       more central, and legacy documents become secondary, the OHS
182041 -       therefore grows "organically" from its legacy-document
182042 -       beginnings. ref DRP 2 00UR
182043 -
182044 -   4.  Defining functionality and structures provides a specification
182045 -       (or anthropolical rediscovery) of Augment's "ontology". (It
182046 -       turns out that the "ontology" defines the functional
182047 -       interactions, as well as an abstraction-tree that leads
182048 -       naturally to an object hierarchy.) Casting the problem in these
182049 -       terms lets us use our ontology gurus (Jack and Howard) to
182050 -       advantage. They intend to start mining Augment documents in
182051 -       order to extract that ontology. (Eugene will use his Augment to
182052 -       HTML converter to make sure they get what they need.),
182053 -       ref DRP 2 KT8N
182054 -
182055 -
182056 -
182057 -
1821 -

SUBJECTS
Phase I Hyperscope - OHS Launch
Hyperscope Web Browser Follow Links in Legacy Files, e.g., Augment
Hyperscope Intermediary Processor Operates Between Browser and Files
Translate HTML into XML+ I-File with Special Structure
Phase II OHS Full Features
Definition OHS, 001025
DKR Difficult to Design, Not Enough Known about Knowledge, KM, 000615
OHS = Augment + Catagories, Eugene Kim, 000622
Knowledge Management, Define
Define DKR
OHS Define Scope, Eugene 001116

4014 -
401401 -  ..
401402 - Hyperscope, OHS, Hyperdocument, Defined; Need Aligment Launch Plan
401403 -
401404 - Follow up ref SDS 42 A5U6.
401405 -
401406 - Ken Holman suggested a better use of the terms "HyperScope",
401407 - "HyperDocument", and "OHS". He intuitively (mis)undestood them to mean
401408 - the viewing engine (HyperScope), the repository (OHS), and the thing
401409 - viewed (HyperDocument). ref DRP 2 00WQ
401410 -
401411 -        [On 001124 Ken Holman confirms Eric's reporting, and adjusts
401412 -        use of terminology to apply DKR. ref SDS 51 L23F
401413 -
401414 - Previously these terms had been something more along the lines of
401415 - HyperScope is a mini-OHS that works with legacy documents, while the
401416 - OHS was the full monty, or words to that effect. But the meanings that
401417 - the terms intrinsically suggested to Ken make a lot of sense. They
401418 - suggest an appropriate division into viewers, entities, and
401419 - repositories. ref DRP 2 TW4L
401420 -
401421 -        [On 001115 Adam Cheyer recommends DKR is the "repository,"
401422 -        rather than OHS; he urges reliance on Doug's documents, but
401423 -        does not cite any writings. ref SDS 49 L87F
401424 -
401425 -        [On 001115 Eric reports having not seen documents that define
401426 -        DKR as a "repository." ref SDS 49 895L On 000614 Eric cited
401427 -        "Technology Template Project" dated 980128 in which Doug
401428 -        discussed Dynamic Knowledge Caputre in a "repository."
401429 -        ref SDS 49 QU5H
401430 -
401431 -        [On 001116 Eric endorses practice to rely on documents for
401432 -        consistent use of terminology. ref SDS 50 0001  Eric proposes
401433 -        OHR as new term for "repository." ref SDS 50 PP3T
401434 -
401435 -        [On 001116 Adam submits explanation of OHS, DKR based on
401436 -        telecon with Doug. ref SDS 50 D3AK
401437 -
401438 -        [On 001124 Ken submits clarifications on limitations of XML for
401439 -        OHS/DKR development. ref SDS 51 0001
401440 -
401441 -
401442 -      ..
401443 -     Linking to Original Sources Helps Set Definitions, Builds DKR
401444 -
401445 -     On 001025 Doug Engelbart submitted an OHS Launch Plan requesting
401446 -     comments linked into the plan. ref SDS 42 00VU  This maintains
401447 -     aligment with definitions, objectives and implemnetation.  While
401448 -     it is hard to create links using traditional methods, making the
401449 -     effort to maintain aligment to original sources is the fastest and
401450 -     easiest way to establishe a culture of settled meanings. as called
401451 -     by ISO criteria for project management, reviewed on 950721.
401452 -
401453 -     Launch Plan says...
401454 -        ..
401455 -        Dynamic Knowledge Repository (DKR) ... could... be taken
401456 -        on by specially trained High-Performance Support Teams. Such a
401457 -        team could for instance be fielded in a university (as a
401458 -        research project into High-Performance Collective Knowledge
401459 -        Work), and take on the "Knowledge Integrator" role for a
401460 -        professional society's DKR. ref DRP 1 04VY,
401461 -
401462 -          On 001025 DKR scope is unclear; Launch Plan needs support
401463 -          from Doug's documents on DKR. ref SDS 42 SN4J  Action Item
401464 -          submitted by letter, ref DIP 1 0001,
401465 -
401466 -     Launch Plan says...
401467 -
401468 -        HyperScope will be a lightly modified web browser supported by
401469 -        an "Intermediary Processor" (IP) which operates between the
401470 -        browser and the files or data bases holding existing working
401471 -        knowledge of a collaborative community.  The HyperScope is not
401472 -        an editor, ref DRP 1 01WX, as reported on 001025. ref SDS 42
401473 -        A5U6
401474 -
401475 -        Hyperscope user will be able to follow links into and between
401476 -        these "legacy" files in a manner similar to using a browser
401477 -        with web-based HTML files. ref SDS 42 MD4M
401478 -
401479 -     Launch Plan calls for adjustments to the initial submission on
401480 -     001025. ref SDS 42 0F5N  Determination to change definitions are
401481 -     easier to assess by providing links to original sources.
401482 -
401483 -
401484 - Rather than having a "HyperScope" that one day evolves into a "OHS"
401485 - (how do we know when it has happened?) we have both a HyperScope and
401486 - an OHS on day one -- where the OHS starts small and grows larger,
401487 - containing more flavors of HyperDocuments over time. ref DRP 2 00YU
401488 -
401489 -     Launch Plan says...
401490 -
401491 -        Phase-2: Maturing/Evolving the Hyperscope into full-feature
401492 -        OHS:, ref DRP 1 ON9K, also, reported on 001025. ref SDS 42 L2D8
401493 -
401494 -
401495 - At the moment, we seem to have factored the problem in a way that lets
401496 - everyone bring their skills to bear simultaneously on different
401497 - aspects of the problem. Odds are good that we'll be able to continue
401498 - down this road for awhile, and potentially make substantial progress
401499 - as a result. ref DRP 2 UI6F
401500 -
401501 -     This planning can be strengthened by submitting a WBS, schedule
401502 -     and budget showing what componentes need to be created, how they
401503 -     fit together, and what skills are needed for each component,
401504 -     perhaps applying the UML discussed on 000324. ref SDS 10 2607
401505 -
401506 -
401507 -
401508 -
401509 -
401510 -
401511 -
401512 -