CONTACTS 
0201 - Armstrong Consulting                 650 845 1782
020101 - Mr. Eric Armstrong
020102 - eric.armstrong@eng.sun.com

SUBJECTS
NODAL Technology for Collaboration OHS/DKR Provides Version Control
NODAL Favorable Reivew for Implementing OHS/DKR, Solves Problems Eric
OHS Problems Solved by NODAL, Eric Armstrong

1605 -    ..
1606 - Summary/Objective
1607 -
160701 - Follow up ref SDS 6 0000, ref SDS 5 0000.
160702 -
160703 - Received ref DRT 1 0001 from Eric Armstrong commenting favorably on
160704 - NODAL which Lee Iverson submitted in a letter, ref DRP 1 0001, that
160705 - included detailed requirements, ref DRP 1 0002, reviewed in the record
160706 - on 010620. ref SDS 6 455M
160707 -
160708 - Two (2) papers were listed....
160709 -
160710 -    1.  NODAL: A System for Ubiquitous Collaboration. ref OF 7 0001
160711 -
160712 -    2.  NODAL: A Network-Oriented Document Abstraction Language,
160713 -        ref OF 9 0001
160714 -
160715 -
160716 -     NODAL Expanded from Submission on 010620
160717 -
160718 - Eric says.....
160719 -
160720 -     I spent a couple of hours with Lee the other day, going over the
160721 -     architecture and capabilities of Nodal. Much of what we discussed
160722 -     has yet to be incorporated into his paper at....
160723 -
160724 -         http://www.ai.sri.com/~leei/OHS/NODAL-WhitePaper.htm
160725 -
160726 -     ...., ref DRT 1 0001, which seems to be ref OF 7 0001
160727 -
160728 -      ..
160729 -     NODAL Solves Design Problems Eric Encountered in OHS/DKR Design
160730 -     Groves, Abstract Modeling Simplify Design for OHS/DKR
160731 -
160732 -
160733 - Eric explains....
160734 -
160735 -     ....I am convinced NODAL is a better design for the KRNL
160736 -     (Knowledge-Repository Node Layer), which I had been trying to
160737 -     construct. I eventually bailed out when the complexity grew
160738 -     overwhelming. But Lee isolated the defects, simplified the thing
160739 -     enormously, and at the same time added drastically new concepts
160740 -     based on Groves and abstract data modeling. ref DRT 1 QF5O
160741 -
160742 -         On 001017 Eric announces release of code soon for OHS/DKR.
160743 -         ref SDS 2 0001
160744 -
160745 -         [On 001106 release of code delayed pending resolution of
160746 -         design problems. ref SDS 3 0001
160747 -
160748 -         [On 001122 Eric disappointed about difficulty creating KM,
160749 -         sent letter suggesting he start with narrow objectives, of
160750 -         simply to link. ref SDS 4 0001
160751 -
160752 - Eric concludes...
160753 -
160754 -     In other words, it is stone-dead killer. ref DRT 1 PJ8F
160755 -
160756 -        He does not address any of the issues in the record on
160757 -        010620. ref SDS 6 AI  For example....
160758 -
160759 -           There is nothing said about a production schedule.
160760 -           ref SDS 6 GN8I and ref SDS 6 R14L
160761 -
160762 -           Audit Trail is not mentioned in Eric's letter, on how NODAL
160763 -           will accomplish this requirement set on 010620. ref SDS 6
160764 -           6Z6N
160765 -
160766 -           Knowledge definition is not mentioned, which is a
160767 -           requirement in NODAL reviewed on 010620. ref SDS 6 IR4O On
160768 -           000503 Eric maintained that not enough is known about
160769 -           "knowledge" to accomplish NODAL's objective. ref SDS 1 5033
160770 -           Did the meeting had on NODAL resolve the problem?
160771 -
160772 -           NODAL seems like Eric's CDR system, how is it different?
160773 -           ref SDS 6 497M
160774 -
160775 -           What mechanism provides "automatic" and seamless integration
160776 -           of everybody, called by NODAL on 010620? ref SDS 6 03HQ
160777 -
160778 -           Where is the evidence that attribution proposed to be
160779 -           provided by NODAL encourages collaboration?  Arn't people
160780 -           afraid of accountability? ref SDS 6 659G
160781 -
160782 -
160783 -
160784 -
160785 -
160786 -
1608 -

SUBJECTS
Nodal Introduction
Granular Interface Allow Navigation Editing Within Document
Nodal Introduction
NODAL New Data Base Language Standard Language Independent API
Document Oriented Data Modeling Language NODAL
Addressable Navigable Object Hierarchy NODAL
Extensible Security Model

2210 -
221001 -  ..
221002 - Node-based File System, Granular Addressability, Versioning
221003 - CDR Solves Check In Out Problem, Similar to CDS
221004 -
221005 - Follow up ref SDS 6 ML5H.
221006 -
221007 - Eric says today....
221008 -
221009 -     The ambitious aim of his undertaking is to create a node-based
221010 -     "file system" that can be used by any application in the same way
221011 -     they use current file systems -- but which provides granular
221012 -     addressability, versioning, and all the rest to smarter
221013 -     applications. ref DRT 1 PW7K
221014 -
221015 -
221016 -
221017 -
221018 -
2211 -

SUBJECTS
Nodal Introduction
File System Traditional Hierarchial
Interoperability Requirement
Legacy Technology Needed Maintain Value Investment Creating Record

3007 -
300701 -      ..
300702 -     Filesystem-Like:
300703 -
300704 -     Follow up ref SDS 6 HS4H.
300705 -
300706 -     See above. ref SDS 0 ML5H
300707 -
300708 -
3008 -

SUBJECTS
Nodal Introduction
Addressable Linkable Reference Reuse Information at Arbitrary Granula
Granular Addressability Requirement

3206 -
320601 -      ..
320602 -     Addressable and Linkable:
320603 -
320604 -     Follow up ref SDS 6 LH5J.
320605 -
320606 -     See above. ref SDS 0 ML5H
320607 -
320608 -
320609 -
3207 -

SUBJECTS
Nodal Introduction
Versioned Attributed Supports Trust Enables Collaboration Communities
Version Control Tracks Change History Integrated into MS Word for Man

3406 -
340601 -      ..
340602 -     Versioned and Attributed:
340603 -     Detailed History of Versions Attribution Builds Trust
340604 -
340605 -     Follow up ref SDS 6 659G.
340606 -
340607 -     See above. ref SDS 0 ML5H
340608 -
340609 -
340610 -
340611 -
340612 -
340613 -