CONTACTS 

SUBJECTS
SDS Medit Original DOS Program Correct Problems on Morris Computer G

2103 -
2103 -    ..
2104 - Summary/Objective
2105 -
210501 - Follow up ref SDS 89 0000. ref SDS 88 0000.
210502 -
210503 -
210504 -
210505 -
210506 -            [On 080611 submitted this record to Morris for use cases.
210507 -            ref SDS 91 0Z6L
210508 -
210509 -
210511 -  ..
2106 -
2107 -
2108 - Progress
2109 -
210901 - Configure SDS on Morris' Computer and Set Up Records Transfer
210902 -
210903 - Follow up ref SDS 89 MI6K, ref SDS 83 164I.
210904 -
210905 - On 080527 discussed installing SDS on Morris' computer so he can learn
210906 - how the program works. ref SDS 83 164I  A week later on 080531
210907 - installed SDS for Morris, ref SDS 89 FE7H, however, we noticed a
210908 - number of error messages flash quickly on the screen, during the
210909 - archive process.  This may be related to the backup operation that
210910 - runs when SDS is first opened each day.  Initial analysis points to
210911 - problems with interim backup. ref SDS 89 HR6M
210913 -  ..
210914 - The trick this morning is to rig debug on Morris' code running the
210915 - program only on the c drive.  There is a test debug command in 04702
210916 - on line 410
210918 -  ..
210919 - Line 1100, ref OF 2 FJ8M, -label Exectv in 04702
210921 -  ..
210922 - Another thing needed is ability to update my records on Morris'
210923 - computer, and his on mine to develop collaboration.
210925 -  ..
210926 - We can use a modified version of the code that transfers my records
210927 - to Gary.  This needs to avoid sending SDS program code.
210929 -  ..
210930 - Turned out was never able to work on this today because could not
210931 - access SDS on Morris' computer.  Stephen entered the password this
210932 - morning before Morris was up, but there is also a switch to open the
210933 - Windows XP screen.  Did not learn about the switch until Morris got
210934 - up, and then we were working on other matters.
210935 -
210936 -        [On 081114 discovered and corrected the problem converting SDS
210937 -        development code to c drive version, backupi.cmd /d: date
210938 -        switch is being changed to /c: which is an invalid switch for
210939 -        xcopy. ref SDS 94 YV7Q
210940 -
210941 -
210942 -
210943 -
2110 -

SUBJECTS
SRS SDS Software Requirements Specification Morris Demonstrate Code

3503 -
350401 -  ..
350402 - SDS Record Software Requirements Specification (SRS)
350403 - SRS SDS Record Software Requirements Specification
350404 - Requirements SDS Record Software Specification (SRS)
350405 - Specification SDS Record Software Requirements (SRS)
350406 -
350407 - Follow up ref SDS 89 LW7O, ref SDS 83 KI6J.
350408 -
350409 - Morris showed initial results today working on a new editor to read
350410 - SDS records that implements the requirements specification he prepared
350411 - last week on 080531. ref SDS 89 LW7O
350412 -
350413 -
350415 -  ..
350416 - Citations Links Changed to HTML Inline Format
350417 - References Eliminated Document Log Replaced by External Program
350418 -
350419 - Morris seemed to discuss eliminating references listed in SDS records.
350421 -  ..
350422 - Morris further seemed to indicate the document log in SDS records can
350423 - be replaced by systems he has used at Intel, and which he feels are
350424 - more comprehensive than SDS.
350426 -  ..
350427 - Sounds like the format of citations in SDS records would be similar to
350428 - HTML links, rather than display reference types, numbers, and anchors.
350430 -  ..
350431 - This requires deliberation showing experience of people using other
350432 - methods to accomplish work illustrated by this record.  On 010924
350433 - Morris indicated nobody uses other tools the way SDS is used for
350434 - intelligence support. ref SDS 37 XT5F
350435 -
350436 -
350437 -
350438 -
3505 -

SUBJECTS
SRS SDS Software Requirements Specification Morris Demonstrate Code

4903 -
490401 -  ..
490402 - 2-Worlds Wordprocessing and Intelligence Complementary
490403 - Thinking through Writing Different World from Attractive Writing
490404 - Shallow Outline Distinguishes SDS Knowledge Management from Wordprocessing
490405 - Line Numbers Visible Aid Writing Record and Collaboration New Way Working
490406 -
490407 - Follow up ref SDS 89 MN5F.
490408 -
490409 - Morris indicated today he plans to enable reading SDS records, and
490410 - writing records to the disk, applying work on 080531 preparing a
490411 - specification for the line numbers. ref SDS 89 MN5F
490413 -  ..
490414 - We went for a hike, about 2 miles to the local library.  On the way
490415 - back he said that line numbers would not display in the new SDS
490416 - program.
490418 -  ..
490419 - We called Gary and he seemed to concur that line numbers can and/or
490420 - should be avoided in SDS Windows application.
490422 -  ..
490423 - This aligned with the proposal Morris made to use a popular commercial
490424 - editor that does not have capabilities of the SDS editor Morris
490425 - created, which supports Knowledge Management, including line numbers,
490426 - presented during the meeting on 080206. ref SDS 72 RT49
490428 -  ..
490429 - On 080426 Gary submitted a letter transmitting a record the day before
490430 - on 080425 that says line numbers are clearly not needed for flexible
490431 - structure, because a tagging system would be easier to maintain.
490432 - ref SDS 82 PE5H
490433 -
490434 -            [On 080831 Morris reported plans for software to implement
490435 -            the spirit of SDS, ref SDS 93 928Q, and noted line numbers
490436 -            cannot be supported, which provide flexible structures for
490437 -            Control Fields, Subjects, References, links, document log,
490438 -            i.e., all of the elements that integrate personal and
490439 -            organizational memory for effective management. ref SDS 93
490440 -            O37U
490441 -
490443 -  ..
490444 - Line Numbers Flexible Structure Well Ordered Record for Knowledge Space
490445 -
490446 - Morris asked today how line numbers are used?
490448 -  ..
490449 - Morris; letter on 080425 cited benefits of line numbers providing
490450 - structure for SDS records. ref SDS 81 R14H
490451 -
490452 -        [On 080611 letter to Morris offers help understanding
490453 -        requirements for well ordered record. ref SDS 91 0Z9V
490455 -  ..
490456 - Gary's letter on 001220 described requirements to capture information
490457 - as it arises without form or organization, ref SDS 31 DR6I, and add
490458 - structure to manage associations that make information useful for easy
490459 - reference when needed. ref SDS 31 IX3Y  Experience over many years
490460 - shows line numbers help quickly navigate complex information using
490461 - orientation from rough approximation of context associated with
490462 - shallow outline structure, explained on 890523, ref SDS 1 5C6L, and
490463 - cited more recently on 080426. ref SDS 82 9O67
490464 -
490465 -            [On 080831 Morris letter reports frustration trying to
490466 -            understand line numbers and difficulty programming this
490467 -            feature using Java programming platform. ref SDS 93
490468 -            O37U
490469 -
490471 -  ..
490472 - Gary mentioned today that legal practice uses line numbers to uniquely
490473 - address lines in the record for accuracy specifying citations.  This
490474 - has proven effective for thousands of years, as a complement to
490475 - non-legal writing without line numbers.  Gary mentioned this point in
490476 - his record on 080425, ref SDS 80 7K6X, received with his letter on
490477 - 080426. ref SDS 82 ZX6H  Requirements for flexible structure to create
490478 - a well ordered record that gives people command and control of the
490479 - work is explained in NWO, describing legal practice. ref OF 24 E75I
490480 - Intelligence support requires a "well ordered record." ref OF 26 07SR
490481 - On 960620 Knowledge Space was framed to describe SDS design that
490482 - explands traditional legal practice using a "well ordered record."
490483 - ref SDS 16 3516
490485 -  ..
490486 - An example is Jack Park's letter on 071220 using SDS line numbers for
490487 - precision access, ref SDS 69 PK5J  Other examples using line numbers
490488 - for command and control of the work are listed in the record on
490489 - 080426. ref SDS 82 XK4J
490490 -
490491 -            [On 080611 Morris' letter to the team illustrates how a
490492 -            well ordered record using line numbers for flexible
490493 -            structure orients communication. ref SDS 92 M38T
490495 -  ..
490496 - Application of line numbers for flexible structure is explained in the
490497 - record on 890523, ref SDS 1 T1VQ
490499 -  ..
490500 - There was discussion today that anchors for explicit links support
490501 - citations without line numbers.  This aligns with Gary's record on
490502 - 080425 describing "tagging systems" that would be easier to maintain
490503 - than line numbers. ref SDS 80 7K65  Review on 080426 cites
490504 - requirements for line numbers to provide flexible structure that
490505 - supports scalable knowledge, ref SDS 82 S19M, and cites the record on
490506 - 080523 setting out benefits of line numbers. ref SDS 1 T1VQ
490508 -  ..
490509 - Gary and Morris indicated line numbers do not work well with a
490510 - wordwrap design Morris has in mind, perhaps using Java code.  This
490511 - makes paragraphs the minimum text element, rather than the current
490512 - design identifying each line of text, as shown in this record.
490513 - Concern today about designing line numbering for flexible structure
490514 - aligns with Morris' letter to Jack Park on 080425 explaining that
490515 - engineering code to apply line numbers for wordprocessing software
490516 - designed to make publishing documents fast and easy is difficult,
490517 - i.e., a "headache." ref SDS 81 R14H  The next day, Gary's letter cited
490518 - his record also on 080425 saying that line numbers cause "pain."
490519 - ref SDS 82 ZX6M
490521 -  ..
490522 - There was discussion of using outlining to replace SDS line numbers.
490524 -  ..
490525 - Since line numbers are a shallow outline scheme, retaining the current
490526 - design meets this criteria.  Gary may have commented that paragraphs
490527 - could be numbered, but not the lines.  Morris mentioned before the
490528 - call with Gary that he has seen legal pleading paper with numbers on
490529 - every 5th line of text.  These schemes seem awkward compared to the
490530 - simple rule to number every line for a well ordered record called out
490531 - in SDS analysis on 890523. ref SDS 1 T1VQ
490533 -  ..
490534 - Gary or Morris may have said that figuring out the line numbering code
490535 - is difficult.  This reflects difficulty at Microsoft, IBM, Oracle,
490536 - SRI, Harvard, MIT, everywhere people have difficulty developing
490537 - software code for Knowledege Management, because the design is
490538 - complex, cited by Gary in his record on 080422, ref SDS 78 0001,
490539 - reviewed at that time. ref SDS 79 MQ4L
490541 -  ..
490542 - Comprehending complexity of intelligence support for Knowledge
490543 - Management takes time and experience, noted for example in the record
490544 - on 910315 that expanded the line numbering system. ref SDS 4 XM88  The
490545 - importance of experience using line numbers to design the system for a
490546 - well ordered record is further illustrated by the record day before on
490547 - 910314. ref SDS 3 T45O
490548 -
490549 -            [On 081120 Gary raised concerns about difficulty designing
490550 -            SDS line numbers for flexible record structure, ref SDS 95
490551 -            5O67, reflecting difficulty creating Knowledge Management
490552 -            at Microsfot, IBM, Oracle -- SDS advantage arises from
490553 -            having solved this difficulty, essential to advance from
490554 -            information to a culture of knowledge to integrate
490555 -            personal and organizational memory and management (POIMS).
490556 -            ref SDS 95 PV6F
490558 -  ..
490559 - The advantage of SDS is having 30 years experience.  Macro 0 shows how
490560 - line numbers are created for SDS, ref OF 5 1H5L, explains concept,
490561 - ref OF 5 AL5I, including macro 202 that integrates letters and
490562 - numbers. ref OF 5 3171
490564 -  ..
490565 - Line numbers maintain a well ordered record with flexible structure
490566 - using a shallow outline for command and control of complex daily work,
490567 - like that shown on 070524. ref SDS 62 075H  Medit shows the cursor
490568 - column, zone, margin.  The command window shows the actual line number
490569 - distinct from SDS line numbering.  Another example in the same record
490570 - further shows requirements for controlling content of lines.
490571 - ref SDS 62 AW4L  As well, the record on 080417 integrates narrative
490572 - with tables. ref SDS 76 DX3I  These common use cases controlling
490573 - content of lines, may present problems with everything controlled by
490574 - wordwrap algorithms that float with the width of the window, which
490575 - seemed to be proposed today.
490577 -  ..
490578 - Maintaining order in the record enables control for intelligence
490579 - support under the locality principle, cited on 080523. ref SDS 1 DS5H
490580 - The fact that this is difficult to accomplish provides an advantage of
490581 - SDS having already accomplished this design.
490583 -  ..
490584 - Morris asked about using book marks rather than line numbers?
490586 -  ..
490587 - Shallow outline supports collaboration enabling everyone to quickly
490588 - find the same place for discussion.
490590 -  ..
490591 - SDS has 5 or 6 marks and return to marks.  Bookmarks are very useful,
490592 - like anchors, discussed above. ref SDS 0 MI5I,
490594 -  ..
490595 - Line numbers complement anchors, marks and returns for quickly
490596 - navigating between areas of the record that are being crafted, edited,
490597 - and compared.  Line numbers identify an "area" of the record
490598 - associated with a particular contextual framework, while marks go only
490599 - to a specific spot.  When discussing the record, people use anchors to
490600 - find a particular spot, but attention needs to be directed to a
490601 - particualr line within a long paragraph, or table, illustrated by the
490602 - record on 070524. ref SDS 62 075H  When discussion centers on text
490603 - that is not linked, then anchors become irrelevant, whereas people can
490604 - be directed to a particular line.  Complementarity in order, control,
490605 - and navigation increases efficient usability, essential for using
490606 - tools all day to write, construct, consult, and discuss a continually
490607 - expanding record of personal and organizational memory.
490609 -  ..
490610 - Line numbers provide presentation distinct from traditional writing in
490611 - books, reports, correspondence, etc, that signals flexible structure
490612 - to manage a "spreadsheet for knowledge," explained in the record on
490613 - 890523. ref SDS 1 T1VQ  Giving up the power of knowledge to control
490614 - lower levels of organic structure should be carefully considered.
490616 -  ..
490617 - An alternate display mode might be developed that applies paragraph
490618 - wordprocessing features along the lines Gary and Morris propose today,
490619 - rather than flexible structure at the line level, and which has
490620 - enabled SDS productivity for 20 years.  It is possible a "new" and
490621 - "modern" design can improve SDS productivity.
490623 -  ..
490624 - Productivity entails trade-offs.
490626 -  ..
490627 - The current version of SDS provides minimal formatting - essentially a
490628 - fixed column editor for legible text and efficient movements to create
490629 - structure.  Wordprocessing design provides much greater formatting,
490630 - including extensive structure, but requires a cost of time for setup
490631 - navigating complex menus for executing commands, noted by Bill Gates
490632 - at Microsoft on 021108. ref SDS 51 EFBE  Morris mentioned on 020110
490633 - that most people use only use 5% of Microsoft wordprocessing commands.
490634 - ref SDS 43 CK4K  This was illustrated last week on 080531 when Morris
490635 - helped configure tables for a newsletter.  He provided assistance for
490636 - someone to use more than the 5% of wordprocessing commands familiar to
490637 - most users, and this took a lot of time. ref SDS 89 HR51
490639 -  ..
490640 - We need tools for constructing context with connections associated
490641 - with chronology to understand correlations, implications, and nuance
490642 - by quickly capturing the record on a greater share of daily work,
490643 - without investing time formatting documents with publishing quality
490644 - display.
490646 -  ..
490647 - Larry Ellison with Oracle noted on 970222 that computers should do
490648 - more than wordprocessing that makes documents attractive. ref SDS 18
490649 - 3967  SDS applies Morris' insight on 951228 that ordinary editing with
490650 - fixed columns aids management better than wordprocessing for
490651 - publishing attractive documents. ref SDS 14 S47O  There is a place in
490652 - the world for wordprocessing that makes creating attractive documents
490653 - fast and easy, and there is a place in the world for intelligence
490654 - support that makes creating and discovering structure of cause and
490655 - effect fast and easy.  These are two different worlds.
490656 -
490657 -
4907 -

SUBJECTS
Use Cases SDS Functions Features Schedule Diary Plan Perform Report

5003 -
500401 -  ..
500402 - Use Cases SDS Windows Application
500403 - Think Remember Communicate SDS Program Use Cases
500404 -
500405 - Follow up ref SDS 71 OM6G, ref SDS 70 6P9J.
500406 -
500407 - Morris asked today for a list of SDS "use cases" to begin coding
500408 - functionality of the new Windows application.  This follows up Morris'
500409 - letter on 071222 asking about SDS "features." ref SDS 70 PX5H
500411 -  ..
500412 - SDS functions listed in the record on 071222 provide "use cases"
500413 - performing primary tasks. ref SDS 70 6P9J
500414 -
500415 -            [On 080611 submitted this record to Morris for use cases.
500416 -            ref SDS 91 0Z6L
500417 -
500418 -            [On 080831 difficulty remembering the record of personal
500419 -            and organizational memory cited by Jack Park re-submitting
500420 -            information forgotten in the record. ref SDS 93 H68I
500421 -
500422 -
500424 -  ..
500425 - Editor Medit Based on Experience Using IBM Full Screen Line Editors
500426 -
500427 - Medit was created in 1981-1983 based on Morris' experience using full
500428 - screen editors in the IBM world during the 1970s.  Medit was enhanced
500429 - beginning in 1985 creating commands to develop SDS for performing "use
500430 - cases" discovered from daily experience using SDS, noted by Morris on
500431 - 010924. ref SDS 37 NK4J  This presents a challenge associating words
500432 - to explain work product that is disconneced from experience.  Without
500433 - experience using SDS, words describing SDS "use cases" seem hollow,
500434 - shallow, unnecessary, and conflicting with experience using other
500435 - methods that are familiar.
500437 -  ..
500438 - Primary SDS use cases include...
500439 -
500440 -        1.  Schedule - planning
500441 -        2.  Diary - reporting
500443 -  ..
500444 - SDS primary uses cases are complemented by...
500445 -
500446 -        3.  Editor - open files as ascii to fix problems
500447 -        4.  Directory and File management
500448 -        5.  Subjects - context management
500449 -        6.  Contacts - people and organizations
500451 -  ..
500452 - Use cases are reflected by the profile management system controlled by
500453 - counter 47...
500454 -
500455 -        47 = 1.................. Editor
500456 -        47 = 2.................. SDS records
500457 -        47 = 3.................. Directory maintenance
500458 -        47 = 31................. Subject index
500459 -        47 = 4.................. Contacts
500460 -        47 = 41................. Contacts Summary
500461 -        47 = 50................. Schedule
500462 -        47 = 51................. Diary Summary
500464 -  ..
500465 - Think, remember, and communicate are basic use cases for intelligence
500466 - support, noted by Morris during the meeting last week on 080531,
500467 - ref SDS 89 1J4L, from strengthening alphabet technology with a process
500468 - of thinking through writing, explained in POIMS. ref OF 20 3742
500470 -  ..
500471 - Chronology, context, and connection reflect mental use cases that
500472 - integrate time and information management, explained in POIMS.
500473 - ref OF 19 1105
500475 -  ..
500476 - "Plan, perform, report" use cases are integrated into an intelligence
500477 - support process for understanding cause and effect that enables
500478 - "command and control of the record," explained in POIMS. ref OF 20
500479 - 1113  Whatever pops into the mind, commonly described as remembering
500480 - the "gist of the story," these fragmentary memories, though incomplete
500481 - and inaccurate, can be used to find the actual story, as explained in
500482 - POIMS. ref OF 19 6M5H  On 911123 Morris described this as a "new way
500483 - of working," i.e., a new use case. ref SDS 6 4930
500485 -  ..
500486 - Line numbers provide shallow outlining for flexible structure to
500487 - maintain a well ordered record, per above. ref SDS 0 2C5I
500489 -  ..
500490 - "Use cases" for a wide range of daily work are listed on 020708 with
500491 - links to examples showing usage. ref SDS 48 MZ6O
500493 -  ..
500494 - Health care and medical practice have been significant uses for SDS
500495 - the past few years.  An example is a recent record showing complexity
500496 - of case management easily causes confusion and error which SDS helps
500497 - avoid. ref SDS 90 TZ8I
500499 -  ..
500500 - Morris seemed to relate today that a few years ago Intel considered
500501 - developing technology to improve health care.  But this effort was
500502 - abandoned because lawyers issued an opinion that HIPAA regulations to
500503 - protect privacy prevent patients from using technology and services
500504 - that improve quality care.  Requirements and opportunities to improve
500505 - care for quality of life by balancing privacy and productivity is
500506 - reviewed in POIMS. ref OF 17 V8P1  An example occurred recently at
500507 - UCSF on 080531. ref SDS 87 H66I  Patients are entitled to exercise
500508 - discretion giving up some privacy in order to strengthen care and
500509 - quality of life. ref SDS 87 C38H
500510 -
500511 -        [On 080611 Morris sent a letter confirming understandings, and
500512 -        objected to presenting effects of abandoning work to improve
500513 -        technology for health care based on interpretation of medical
500514 -        regulations to protect privacy, denies patients better care.
500515 -        ref SDS 92 M38W
500517 -  ..
500518 - Communication Metrics lists 8-steps comprising subsidiary uses cases
500519 - for primary uses of SDS.  On 950204 Morris asked what's a metric for
500520 - communication. ref SDS 10 5468  At that time "accuracy" was listed as a
500521 - useful metric for communication. ref SDS 10 8A4G  NWO lists 12 common
500522 - information units for useful metrics of daily communication.
500523 - ref OF 26 FT9G
500525 -  ..
500526 - "Reporting" is the first use case step.  This enhances the journalist
500527 - role by writing the story of daily work within a framework of flexible
500528 - structure, which empowers command and control of the record, listed in
500529 - POIMS. ref OF 19 685K
500531 -  ..
500532 - We discussed today the use case of outlining, which Morris plans to
500533 - enhance, reported on 080527. ref SDS 83 I53F
500535 -  ..
500536 - SDS functionality is supported by Medit commands for many "use cases,"
500537 - including zone, change, locate, up, down, setcnt, addcnt, mulcnt,
500538 - inscnt, target, move, copy, split, join, get, delete, etc., as listed
500539 - in the command file. ref OF 11 0001
500541 -  ..
500542 - Since all of this has been submitted previously, we need examples of
500543 - additional "use cases" in order to target further work to needs of
500544 - the programming effort.
500545 -
500546 -
500547 -
500548 -
500549 -
500550 -
500551 -
500552 -
500553 -
5006 -