Click here to comment!
1...Why isn't the issue, not a "real" OHS, but rather....
2...What does the DKR do, as a sub-element of OHS?
3...How does this relate to his ideas on 010223, ref SDS 82 0001,
4...Where are architecture steps for vision, marketing and
5...Where is CPM showing tasks, assignments and completion date?
CONTACTS
SUBJECTS
OHS SDS Core Onion-skin Architecture
Code in Progress, Jack Park
OHS Code Started, Jack Park
Topic Maps Tab in Jack Park's OHS Program, 010316
IBIS Tab in Jack Park's OHS Program, 010316
SDS Tab in Jack Park's OHS Program, 010316
IBIS Conversation Linking on Nodes
Ontology Rule Firings Use Cases Invent OHS Qualitative Process Theory
Jlinda4 DKR Coordinator for OHS, Jack Park, 010316
Topic Map Graphical Map Organize Navigate Record
OHS Code Begun, Jack Park
4813 -
4813 - ..
4814 - Summary/Objective
4815 -
481501 - Follow up ref SDS 82 0000, ref SDS 81 0000.
481502 -
481503 - Jack reports progress on developing code for OHS. Have not seen
481504 - architecture, but doing initial code will reveal ideas for developing
481505 - design.
481507 - ..
481508 - Submitted ref DIT 1 0001 linked to this record congratulating Jack on
481509 - getting started.
481510 -
481511 - [On 010322 Jack submits notice of JTMS available. ref SDS 89 0001
481512 -
481513 -
481515 - ..
4816 -
4817 -
4818 - Progress
4819 -
481901 - Received ref DRT 1 0001 from Jack Park reporting progress developing
481902 - code for OHS.
481904 - ..
481905 - Jack says his OHS project continues. The spirit of the project rests
481906 - on the notion that it is time for many to build variants of an OHS, so
481907 - that we will have lots to compare and discuss once a "real" OHS gets
481908 - off the ground. ref DRT 1 EP6F
481909 -
481910 - Why isn't the issue, not a "real" OHS, but rather....
481911 -
481912 - How will this OHS project improve Jack's "knowledge" work, and
481913 - by extension help others do their work?
481915 - ..
481916 - Will it materially augment intelligence, save time and money,
481917 - etc.?
481919 - ..
481920 - Need typical day scenario showing application, as previously
481921 - requested on....
481922 -
481923 - a. 001130, ref SDS 54 0246
481924 - b. 010223, ref SDS 82 4042 and ref SDS 82 00HQ
481926 - ..
481927 - Jack's version holds everything to be part of an OHS. He separates
481928 - three categories, as described by Lee Iverson:, ref DRT 1 XI6J
481929 -
481930 - 1. Context -- user stuff
481931 -
481932 - 2. Content -- raw data
481934 - ..
481935 - 3. Knowledge -- ontologies, etc
481937 - ..
481938 - Jack says....
481939 -
481940 - I have combined Content and Knowledge into what I call the
481941 -
481942 - DKR: dynamic
481943 -
481944 - ...because everything (in my version) is represented internally as
481945 - topic maps in a relational database. ref DRT 1 UI7G
481947 - ..
481948 - [On 010322 Jack submits JTMS which he says is persistant in
481949 - a relational data base. ref SDS 89 QG4O
481951 - ..
481952 - What does the DKR do, as a sub-element of OHS?
481954 - ..
481955 - DKR = content and knowledge, so what is "knowledge"?
481957 - ..
481958 - How do we know we have "knowledge," rather than more
481959 - information, per analysis of KMI on 010315? ref SDS 88 A45G
481961 - ..
481962 - Context comprises, ref DRT 1 KJ7K,....
481963 -
481964 - • Topic Maps tab, an
481965 -
481966 - • IBIS tab, and an
481968 - ..
481969 - • SDS tab.
481971 - ..
481972 - [On 010329 Jack advises that SDS stands for something like
481973 - "Structured Dialog System." ref SDS 90 XZ4K
481975 - ..
481976 - Later, there will be
481977 -
481978 -
481979 - • TSC,
481980 - • Augment, etc, tabs.
481982 - ..
481983 - The common interlingua between Context and DKR is XML messages,
481984 - with the "cargo" written in XTM format. ref DRT 1 MM7N
481985 -
481986 - How does this relate to his ideas on 010223, ref SDS 82 0001,
481987 - and previously on 001130? ref SDS 54 0001
481989 - ..
481990 - Context, called client, talks to a DKR server, which couples client
481991 - to jLinda4, a Linda-like coordination system. ref DRT 1 FO8H
481992 -
481993 - Where are architecture steps for vision, marketing and
481994 - engineering feasibility, which Jack proposed on 000426 be
481995 - undertaken before writing code. ref SDS 32 0304
481996 -
481997 - On 010313 letter to Eugene Kim, and the OHS/DKR team noted
481998 - that OHS/DKR is proposed for advancing a....
481999 -
482000 - "whole new way of thinking,"
482001 -
482002 - .... ref SDS 87 9T7L, based on review of Doug's BI web site
482003 - on 991222. ref SDS 23 3696
482005 - ..
482006 - How does the work today align with this vision or goal?
482007 -
482009 - ..
482010 - Have these steps been done?
482012 - ..
482013 - Nothing wrong experimenting with initial code to test and
482014 - formulate conceptual framework, if that is what is occurring.
482016 - ..
482017 - Need explanation of correlation between SDS and the other
482018 - elements, including IBIS, Topic Maps. Explain the idea
482019 - like....
482020 -
482021 - Here is an SDS record reviewing development of OHS.
482022 -
482023 - We hit the IBIS tab and do thus and so in relation to the
482024 - SDS record.
482026 - ..
482027 - Then we hit the Topic Maps tab and do such and such to
482028 - the IBIS and to the SDS record.
482030 - ..
482031 - Then we jump back to SDS and discuss IBIS and Topic Maps
482032 - in the following way....
482034 - ..
482035 - Then we.....
482037 - ..
482038 - From there, DKR, which is also a jLinda4 client, process
482039 - persistence and knowledge issues. By coordinating with jLinda4, the
482040 - system can accept many clients, and many DKR servers. In some
482041 - sense, jLinda4 becomes a kind of Von Neumann bottleneck. Film at
482042 - 11...on that one:-)
482043 - ..
482044 - Progress to date, ref DRT 1 IO8O,.....
482045 -
482046 - got client and server to talk to jLinda4.
482047 -
482048 - Client and server (prior to addition of jLinda4) already could
482049 - manipulate topic maps: display them, create and edit them, and
482050 - delete them from the database.
482052 - ..
482053 - Now, to get the tuples working!
482054 -
482055 - Where is CPM showing tasks, assignments and completion date?
482056 -
482058 - ..
482059 - It is my hope that others will begin hacking their own rendition of
482060 - an OHS as soon as possible. ref DRT 1 XO9J
482061 -
482062 - If this does not occur, however, would it affect Jack's
482063 - efforts one way or the other?
482064 -
482065 - Why not just build what we need?
482066 -
482067 -
482068 -
482069 -
482070 -
482071 -
482072 -
4821 -