CONTACTS 
0201 - Science Applications                 619 546 6000
020101 - Mr. Roy Roebuck, Ph.D.

SUBJECTS
GEM Roy Roebuck
Sel -evident Benefits
Unique Character of Communication Metrics
Marketing SDS, Communication Metrics
Anytime, Anywhere Intelligence
Virtual Office, Paperless Office
Graphics Showing Program Flow
Copywrite/Patent
Reverse Engineering
Writing Skills and Tips
Breakthroughs are difficult to Understand
Scenario Typical Day Using SDS

1614 -    ..
1615 - Summary/Objective
1616 -
161601 - Follow up ref SDS 51 0000, ref SDS 49 0000.
161602 -
161603 - Roy explains product development opportunities, and provides sources
161604 - on the NSF research proposal.  Are these related?  Would all of this
161605 - be part of the research effort? ref SDS 0 0084
161606 -
161607 - He credits SDS with solving "unstated needs" which is a marketing
161608 - advantage that must be exploited in time to avoid others from catching
161609 - up and gaining market share with a viable substitute. ref SDS 0 9614
161610 -
161611 - Roy sees I am having difficulty "selling" these ideas and suggests
161612 - writing skills for marketing.  I welcome this help. ref SDS 0 9952
161613 -
161614 -     [On 990315 sent response. ref SDS 51]
161615 -
161616 -
1617 -
1618 -
1619 - Progress
1620 -
162001 -  ..
162002 - SDS Scenario Can Be Improved with UML Graphics, Better Narrative
162003 -
162004 - Received letter from Roy, ref DRT 1 0001, responding to my letter on
162005 - 990310, ref SDS 49 2880, and previously on 990301, ref SDS 44 9503,
162006 - sending ref DIP 5.
162007 - ..
162008 - Roy has reviewed the SDS scenario, ref OF 1 3066, sent on
162009 - 990225... ref SDS 41 5062.  He offers ideas to improve the
162010 - presentation, and to provide assistance. ref DRT 1 3381
162011 -
162012 - He does not comment on "integrating" time and information management,
162013 - such that we do not have a schedule program and an information data
162014 - base program.  It is a single environment with features that work
162015 - together smoothly like the human mind. ref OF 3 8559  Roy does not
162016 - mention using TQM for management by adding "metrics" to
162017 - communications, as related in the scenario. ref OF 1 6205
162018 -
162019 - I reviewed the web site on Unified Modeling Language (UML) suggested
162020 - at ref DRT 1 4080 for creating a graphical model of SDS "use case."
162021 -
162022 -          http://www.omg.org/techprocess/meetings/schedule/
162023 -          Technology_Adoptions.html#tbl_UML_Specification
162024 -
162025 - I guess I need help on how UML resources can be applied.  Is there an
162026 - example?
162027 -
162028 -       [Roy did not respond.]
162029 -
162030 -
162031 -      ..
162032 -     Scenario, Marketing Need Language from Standard Technologies
162033 -
162034 -     Roy suggests Communication Metrics be explained using terminology
162035 -     from accepted technologies, specifically...
162036 -
162037 -            XML tagging,
162038 -            XLL as XML Extended Linking -XLink
162039 -            XML Extended Pointer - XPointer
162040 -            iCalendar.
162041 -
162042 -     ...which follows up his letter on 990301. ref SDS 44 9528
162043 -
162044 -         [On 000124 XML proposed for Dynamic Knowledge Repository (DKR)
162045 -         proposed by Doug Engelbart. ref SDS 59 3551]
162046 -
162047 -     A cross-referenced table may be helpful; is Roy doing this for his
162048 -     own work. ref DRT 1 5360
162049 -
162050 -     Could Roy provide an example of how the SDS scenario could be
162051 -     explained with these tools?  Not sure what he has in mind.
162052 -
162053 -       [Roy did not respond.]
162054 -
162055 -      ..
162056 -     Com Metrics and SDS Explanations Need Better Writing
162057 -
162058 -     Welch and Roebuck writing style is too complex...
162059 -
162060 -         Too many modifiers in phrases, clauses, and sentences.
162061 -
162062 -         Esoteric terms are used too frequently.
162063 -
162064 -         Common terms are used differently that reflect contextual, and
162065 -         personal history not widely shared.
162066 -
162067 -     These characteristics can be effective for specialists and peers.
162068 -     ref DRT 1 6625
162069 -
162070 -     Marketing to a broader public requires different writing style.
162071 -     ref DRT 1 6890
162072 -
162073 -     Roy has proofreading and editing support. ref DRT 1 3118
162074 -
162075 -     "Selling" new ideas requires special skills, and time for people
162076 -     to catch up.  It took 15 years for Postits to take off, reviewed
162077 -     on 970526. ref SDS 19 8333  More complicated things may take time
162078 -     as well.  HQUSACE just recently used "intelligence" in a document
162079 -     as a work role or business process. see 990304, ref SDS 47 1070
162080 -
162081 -     On 990305, Max Wideman worried that it took 40 years for ideas to
162082 -     find useful application in Communication Metrics. ref SDS 48 1836
162083 -
162084 -     On 990225 Roy's view of SDS was clear and concise. ref SDS 41 6956
162085 -     see also on 990301 ref SDS 45 0772   His understanding and talent
162086 -     can help others reach a "shared meaning," explained on 990312 in
162087 -     connection with Max's glossary project. ref SDS 50 6740  We need
162088 -     an audience and opportunity to tell the story over and over and
162089 -     over, and to enable others to experience and discover "meaning"
162090 -     through actual work.
162091 -
162092 -     Communication is a tough job.  Good editing for effective writing
162093 -     is a big help.
162094 -
162095 -
162096 -  ..
162097 - Communication Metrics Accomplishes Critical Management Needs
162098 - Marketing Identifies Path to Exploit Solution to Unstated Needs
162099 -
162100 - Roy credits SDS with powerful functionality in Communication Metrics
162101 - on the web, that satisfies a broad yet unstated need, ref DRT 1 0360,
162102 - providing significant capability for time-stamped and source-stamped
162103 - tags. ref DRT 1 6435
162104 -
162105 - Solving "unstated needs" provides a marketing advantage under Empathic
162106 - design criteria reviewed on 940508. ref SDS 3 6930
162107 - ..
162108 - How can this accomplishment be commercially exploited?  At some
162109 - point, "unstated needs" have to become clearly recognized needs, also
162110 - called "self-evident benefits."
162111 -
162112 -           [On 990427 Roy proposes to NSF deploying freeware for a web
162113 -           app that generates revenue from consulting. ref SDS 55 9522]
162114 -
162115 -       On 980803 Communication Metrics on the Internet provided
162116 -       "self-evident benefits." ref SDS 25 5141
162117 -
162118 -       On 981104 Communication Metrics on the Internet is "pretty neat"
162119 -       expresses solution to "unstated needs." ref SDS 28 4320
162120 -
162121 -       HQUSACE cited self-evident benefits on 981119, ref SDS 29 2272,
162122 -       affirmed on 990304. ref SDS 47 1362
162123 - ..
162124 - Roy suggests packaging SDS as a standards Draft Submission to
162125 - ISO, IEEE, EIA, ANSI, IETF, or W3C, unless we want to keep it
162126 - proprietary. ref DRT 1 0360
162127 -
162128 -           [On 990427 Roy proposes to NSF funding for preparing
162129 -           standards. ref SDS 55 9522]
162130 -
162131 -       SDS supports ISO criteria for traceability to original sources,
162132 -       reviewed on 950721. ref SDS 11 1740  This leads to "alignment"
162133 -       as a key part of "intelligence." ref OF 3 0582
162134 -
162135 -       More broadly, SDS provides an over-arching organizing scheme for
162136 -       everything that can be implemented by anyone at all organization
162137 -       levels for daily management and real-time decision making.
162138 -
162139 -   How would Standards Submission benefit Welch and those who help with
162140 -   this effort?
162141 -
162142 -       [Roy did not respond.]
162143 -
162144 -   How do we initiate action on this idea?
162145 -
162146 -           [On 990427 Roy proposes to NSF deploying freeware for a web
162147 -           app that generates revenue from consulting. ref SDS 55 9522]
162148 -
162149 - Roy lists risks of maintaining SDS as a proprietary product...
162150 -
162151 -   a.  Finance is needed to create this market and "lock" in a steady
162152 -       sales base. ref DRT 1 2720
162153 -
162154 -       Can finance be solved to exploit powerful self-evident benefits?
162155 -       ref SDS 0 9614
162156 -
162157 -       [Roy did not respond.]
162158 -       ..
162159 -   b.  SDS might be reverse engineered and offered as "new"
162160 -       capability under another name by someone else. ref DRT 1 7161
162161 -
162162 -       This is certainly a concern.  On 980722 Morris indicated SDS is
162163 -       difficult to reverse engineer. ref SDS 24 3280  More recently on
162164 -       990301 he cited this risk. ref SDS 45 9315
162165 -
162166 -       On 941114 IBM found that SDS is a new and more useful approach.
162167 -       They later paid $3.5B for Lotus Notes hoping it could do SDS
162168 -       stuff, but it can't. ref SDS 4 2473
162169 -       ..
162170 -   c.  SDS cannot be patented because functionality is "obvious"
162171 -       once the idea is presented; copyright provides some protection.
162172 -       ref DRT 1 3774
162173 -
162174 -       We might argue that patent is appropriate because the "obvious"
162175 -       functionality has not been discovered by anyone else.  Assuming
162176 -       that fails, the next level of protection is providing a better
162177 -       implementation by being first with a strong product and the
162178 -       support that makes it useful:  Communication Metrics.
162179 -
162180 -       Roy notes that SDS time and source tagging, and linking are
162181 -       explicit and visible as data, while most others hide constructs
162182 -       as metadata or system data. ref DRT 1 7392
162183 -
162184 -       Communication Metrics maintains that people need a lot of help
162185 -       with constant reminders of where they are in "knowledge space."
162186 -       Time identification is critical to provide orientation on cause
162187 -       and effect, per analysis on 990218. ref SDS 37 2972
162188 -
162189 -       Can Roy provide an example of an approach to time and source
162190 -       tagging that has hidden constructs?
162191 -
162192 -       [Roy did not respond.]
162193 -
162194 -
162195 - What are the opportunities and risks of giving up proprietary rights?
162196 -
162197 -   a.  ?
162198 -
162199 -   b.  ?
162200 -
162201 -   c.  ?
162202 -
162203 -
162204 -
162205 -
1623 -

SUBJECTS
Context Management
Context Traceability Support Understanding
Knowledge Management
Context Management
Context Linking Analysis Intelligence Adds Value

2108 -
210801 -  ..
210802 - Send link to GEM "Object to Fact flow" Diagram??
210803 -
210804 - Roy seems to suggest that I link to GEM, but it is not clear how to do
210805 - this or what will be linked. ref DRT 1 5328
210806 -
210807 - Need help on linking to GEM "Object to Fact flow" Diagram
210808 -
210809 -             http://www.one-world-is.com/rer/dem/img111.gif
210810 -
210811 -       [Roy did not respond.]
210812 -
210813 - His team working on a DOD project has done this for an "Enterprise
210814 - Management" improvement effort.
210815 -
210816 - How would this be accomplished?
210817 - ..
210818 - What is the objective?
210819 -
210820 - Based on Roy's understanding of SDS, ref SDS 0 9614, possibly he could
210821 - suggest some detail on what he has in mind.  Might SDS merely use the
210822 - "Object, Profile, Context, History" environment as a resource, as it
210823 - does other resources?
210824 -
210825 - Dynamic Object scheme provides interesting structure.
210826 -
210827 -             http://www.one-world-is.com/rer/dem/img033.gif
210828 -
210829 -      Some thought is needed on how a busy executive would use it.
210830 -
210831 -      Possibly a system applies it for him.  SDS is about giving the
210832 -      busy executive a way to handle a lot of information accurately
210833 -      and quickly.  There cannot be 4 or 5 more things to do, because
210834 -      then the guy will not have enough time.
210835 -
210836 -  ..
210837 - Management Context structure seems similar to SDS methods
210838 -
210839 -             http://www.one-world-is.com/rer/bei/img064.gif
210840 -
210841 -      This is a type of organic structure that SDS applies to
210842 -      everything, essentially with unlimited depth and cross
210843 -      relationships.
210844 -
210845 -      Yesterday, Max Wideman's paper used Context Maps. ref SDS 50 0360
210846 -
210847 -        [On 990427 Roy's NSF proposal is to deploy Context Management
210848 -        on the web as freeware to support Enterprise Management.....
210849 -        ref SDS 55 3360
210850 -
210851 -
210852 -
2109 -

SUBJECTS
Voice Data Entry
Speech Recognition Long Way in Future
Definition - Management Science

2606 -
260601 -  ..
260602 - Voice Recognition Vendors Market Channel for SDS
260603 -
260604 - Follow up ref SDS 44 9503, ref SDS 41 4758.
260605 -
260606 - Roy suggests SDS can provide Voice Recognition vendors the means to
260607 - use their product as "Knowledge" recording devices, with their
260608 - technologies at the front end, SDS in the middle, and appropriate
260609 - storing/linking technologies in the back end. ref DRT 1 2703
260610 -
260611 - On 990225 reviewed application of voice data entry. ref SDS 41 4758
260612 -
260613 -      [On 990404 Roy sent article on audio mining. ref SDS 52 1270]
260614 -
260615 - I reviewed the GEM slide "Information Technology Recycling," dated
260616 - 990314, to see how SDS as middle-ware would apply to other recorded
260617 - textual, seminstructured information systems...
260618 -
260619 -          http://www.one-world-is.com/rer/dem/slides/img089.gif
260620 - ..
260621 - There is a lot here on components of information processing,
260622 - including a definition of "management" presented previously on 990215.
260623 - ref SDS 34 3510 ...
260624 -
260625 -      The resolution of complexity and diversity in science and society
260626 -      into a system of controlled order, citing the encyclopedia of
260627 -      management
260628 -
260629 - Does Roy have a source for the "encyclopedia of management"?
260630 -
260631 -    Who publishes it?  Can we get it on the web?
260632 -
260633 -
260634 - Need help to see where Communication Metrics fits in the GEM slide.
260635 -
260636 - How in particular does voice recognition fit.  It might be useful, but
260637 - does not seem necessary to accomplish the objective of GEM.
260638 -
260639 - Seems like this could be part of NSF research effort, to evaluate how
260640 - well this concept might be implemented in the real world.
260641 -
260642 -
260643 -
260644 -
260645 -
2607 -

SUBJECTS
Subject Indexing
Distinguished from Other Systems/Methods
Organic Subject Structure
Objectives, Identifying, Correlating
Repository of Experience

4208 -
420801 -  ..
420802 - Other Vendors Working on Catagorization Systems
420803 -
420804 - Roy cites one of several possible competitors to the SDS method of
420805 - categorization, indexing, tagging, at...
420806 -
420807 -                   http://www.autonomy.com.
420808 -
420809 -    ... ref DRT 1 7224
420810 -
420811 - Autonomy Publishing Corp seems to support Knowledge Management with
420812 - tools to handle a lot of information automatically.
420813 -
420814 -            Catagorize
420815 -            Hyperlink
420816 -            Search
420817 -            Deliver
420818 -            Alert
420819 -        *   Fusion
420820 -            Personalization
420821 -            Profiling
420822 -            Visualization
420823 -
420824 -   *  Fusion seems to be a search engine across software programs,
420825 -      e.g., LN, Word, Powerpoint (is there "knowledge" in a Powerpoint
420826 -      file that contributes to anything?), the web, etc.
420827 -
420828 - Autonomy says that when a piece of information comes in, the system
420829 - will read it, determine what it is about, catagorize it, tag it, or
420830 - put it in the right place, automatically.
420831 -
420832 - Question:
420833 -
420834 -    Who is relying on this "system" to do their thinking for them?
420835 -
420836 -    How long have they been doing it?
420837 -
420838 -    Give an example of how the system would "read" the one sentence
420839 -    letter from USACE received on 990303, and decide what it is about?
420840 -    ref SDS 46 9499
420841 -
420842 -    How about a multi-sentence letter?
420843 -
420844 -    How about an SDS record?
420845 -
420846 -
420847 -
4209 -

SUBJECTS
XML
Schedule Calendar Software
IETF Calendar Schedule Working Group CALSH

4606 -
460601 -  ..
460602 - Schedule Development (Calsch) - Solving 3 Problems
460603 -
460604 - Follow up ref SDS 44 8492.
460605 -
460606 - Roy seems to be completing the letter he began on 990301,
460607 - recommending review of IETF Calendaring and Scheduling standards...
460608 -
460609 -               http://www.imc.org/ietf-calendar
460610 -
460611 - It appears that I looked at this on 990301. ref SDS 44 5400
460612 -
460613 - Today, he says the iCalender DTD at...
460614 -
460615 -               http://www.imc.org/draft-dawson-ical-xml-dtd
460616 -
460617 - ...used in conjunction with XLL provides a good foundation for
460618 - building SDS as an XML application on top of XML-enabled Application
460619 - and Database Server(s). ref DRT 1 5160
460620 -
460621 - I agree that these "standards" may help SDS become a broad and simpler
460622 - implementation, and this would be useful for many reasons.  We need to
460623 - see how they can be integrated with a diary and all other information
460624 - forms.
460625 -
460626 - Is this a component of NSF research?  It seems useful apart from the
460627 - research effort.
460628 -
460629 - Has Roy worked with these methods or worked with people who could
460630 - support the effort he has in mind?
460631 -
460632 -     [Roy did not respond.]
460633 -
460634 -
460635 -
4607 -

SUBJECTS
Requirements
Ownership Work Product/Research
Technical Objectives, Research Goals

4906 -
490601 -  ..
490602 - NSF terms of grant content ownership
490603 -
490604 - Follow up ref SDS 41 3839.
490605 -
490606 - Are Roy's ideas for SDS part of the NSF research grant?
490607 -
490608 -      e.g., XML, calendaring, speech recognition, etc.?
490609 -
490610 -     [Roy did not respond.]
490611 -
490612 -        [On 990427 Roy explains Com Metrics fits in Context Management
490613 -        per ref SDS 55 0204]
490614 -
490615 -        [On 990427 Roy proposes to NSF deploying freeware for a web app
490616 -        that generates revenue from consulting. ref SDS 55 9522]
490617 -
490618 - NSF Info relevant to us is at...
490619 -
490620 -
490621 -                http://www.eng.nsf.gov/sbir/index.htm
490622 -
490623 -
490624 - ... ref DRT 1 2610
490625 -
490626 - I reviewed the introduction and it seems to me that Communication
490627 - Metrics is "cutting edge" technology that meets the criteria for
490628 - applying multi-discipline knowledge.
490629 -
490630 - This may be a way to do the education study discussed with University
490631 - of Santa Clara on 951012. ref SDS 13 7477
490632 -
490633 - What is Roy's take on these provisions relative to our objectives?
490634 -
490635 - I looked at section 3 on the format.  The links to samples return
490636 - blank pages.
490637 - ..
490638 - We need to develop a program and schedule to meet NSF 990609
490639 - submission deadline. ref OF 11 0603
490640 -
490641 -     [On 990609 submitted proposal. ref SDS 56 0001]
490642 -
490643 -     [On 990616 re-submitted proposal. ref SDS 58 0001]
490644 -
490645 - He cites Chapter 1 of the SBIR/STTR guide for 99. ref DRT 1 2610
490646 -
490647 -                http://www.nsf.gov/pubs/1999/nsf9957/Chapt-1.htm
490648 -
490649 -                http://www.nsf.gov/pubs/1999/nsf9957/Chapt-8.htm#IT
490650 -
490651 - ...to see where both our efforts, singly and jointly, would apply.
490652 -
490653 - Retention of ownership of the resultant research and data, and the
490654 - government's rights to it, is at...
490655 -
490656 -               http://www.nsf.gov/pubs/1999/nsf9957/Chapt-5.htm#BM5_5
490657 -
490658 - ...through Section 5.8.
490659 -
490660 -
490661 -      ..
490662 -     Study Concepts - Technical Objectives
490663 -
490664 -     On 980328 reviewed study issues. ref SDS 23 5426
490665 -
490666 -     On 990225 developed possible objectives for NSF research project
490667 -     on Com Metrics. ref SDS 41 0788
490668 -
490669 -     Melding macro and micro management systems from work on 990218.
490670 -     ref SDS 36 2808
490671 -
490672 -     Technology for daily management to increase use of mental capacity
490673 -     above 2%.
490674 -
490675 -     Rework theory based on limited span of attention.
490676 -
490677 -         Management is essentially bumbling, or more politely called
490678 -         "problem handling" and "expediting."
490679 -
490680 -         [On 990423 completed review NSF requirements. ref SDS 53 3460]
490681 -
490682 -         [On 990425 Morris proposed similar subject. ref SDS 54 6410]
490683 -
490684 -         [On 990427 Roy submits initial proposal. ref SDS 55 9522]
490685 -
490686 -     Subject Identification and Management
490687 -
490688 -     Clear, Concise, Complete Communication via Internet
490689 -
490690 -     Intelligence organize, anlayse, align, summarize and deliver via
490691 -     Internet.
490692 -
490693 -         [On 990427 Roy's NSF proposal does not seem to contemplate a
490694 -         study or research. ref SDS 55 9522]
490695 -
490696 -         [On 990615 Phase I Technical Objectives identified in proposal
490697 -         to NSF. ref SDS 57 3844]
490698 -
490699 -
490700 -
490701 -
4908 -
4909 -