THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: July 26, 2000 04:11 PM Wednesday; Rod Welch

Jack Park's letter on SDS business entity.

1...Summary/Objective
2...Opportunity Commercial Development Core Engine Knowledge Management
....................Towards an SDS Enterprise
3...Knowledge Management = Information Management + Time Management
..............Communication + Meaning + Inference
4...Ownership, Patents, Licensing Require Review


..............
Click here to comment!

CONTACTS 
0201 - SRI International                                                                                                                                                  O-00000103 0701
020101 - Mr. Pat Lincoln; 650 859 5454                                                                                                                                    O-00000103 0701
0202 - Intel Corporation                                                                                                                                                  O-00000704 0201
020201 - Mr. Morris E. Jones; Business Unit Manager
020203 - Cable Network Operation                                                                                                                                          O-00000704 0201

SUBJECTS
Planning; Alliances
Knowledge Management Development Based on SDS
SRI DKR Project, 000503
Park, Jack at VerticalNet
Market Created by Others
Help Preparing Business Plans
Business Plan Model Alliance on Open Source Project with SDS Proposal

1309 -
1309 -    ..
1310 - Summary/Objective
1311 -
131101 - Follow up ref SDS 40 0000, ref SDS 35 0000.
131102 -
131103 - Jack submits a constructive first draft of a business model for SDS
131104 - to be both a commercial product and support open source community.
131105 - His approach is different from what was discussed previously, and so
131106 - requires more thought.  Morris has some questions, but has not been
131107 - able to review Jack's draft.  He will take a look in the morning, and
131108 - we can discuss.
131110 -  ..
131111 - Submitted ref DIP 4 0001 sending Jack's letter, ref DRT 1 0001, to
131112 - Morris, and linked to this record.  Decided not to put this on the
131113 - web, so incorporated into the email.  Hope Morris can read it.
131115 -  ..
131116 - In a discussion the next morning, Jack said he didn't mind having this
131117 - record and his proposed business model on the web, so I went ahead and
131118 - put it out there.  This record is also linked in the letter,
131119 - ref DIP 3 0001, to Pat Lincoln, on 000725. ref SDS 40 0001
131120 -
131121 -     [On 000727 discussed with Jack. ref SDS 42 0001
131123 -      ..
131124 -     [...talked to Morris. ref SDS 42 6804
131126 -      ..
131127 -     [...received letter with ideas from Pat Lincoln. ref SDS 43 0001
131129 -      ..
131130 -     [On 000802 began business plan. ref SDS 44 0001
131131 -
131132 -
131134 -  ..
1312 -
1313 -
1314 - Progress
1315 -
131501 - Opportunity Commercial Development Core Engine Knowledge Management
131502 -
131503 - Follow up ref SDS 40 0050, ref SDS 32 0050.
131504 -
131505 - Received ref DRT 1 0001 from Jack transmitting a draft version 0.1
131506 - for a business model to create an entity to produce SDS.  This first
131507 - draft is titled...
131508 -
131510 -                     ..
131511 -                    Towards an SDS Enterprise
131512 -
131514 -  ..
131515 - It is submitted as a Word document.  For convenience I attached it to
131516 - Jack's letter in HTML. ref DRT 1 0002
131518 -  ..
131519 - Sent an ordinary email thanking Jack for getting the ball rolling with
131520 - an initial framework for thinking about issues.
131522 -  ..
131523 - The proposed business model implements ideas discussed with Jack on
131524 - 000503, ref SDS 22 6903, and again with Jack and Howard Liu yesterday
131525 - during lunch, following the meeting with Pat Lincoln at SRI on 000725
131526 - 0930. ref SDS 40 0050  The licensing approach needs some thought.
131527 - ref SDS 0 1222
131528 -
131529 -     [On 000727 letter from Pat recommends developing business model.
131530 -     ref SDS 43 5112
131531 -
131532 -        [On 010201 Jack submits ideas for open source SDS project.
131533 -        ref SDS 48 0001
131535 -      ..
131536 -     [On 000802 developed initial business plan. ref SDS 44 0001
131538 -      ..
131539 -     [On 000804 submitted draft business planning for comments.
131540 -     ref SDS 46 0001
131542 -      ..
131543 -     [On 000929 called Doug Engelbart on this. ref SDS 47 6S9H
131544 - ..
131545 - At the meeting yesterday, on 000725, Jack related that he and
131546 - Howard had dinner with Cliff Joslyn the prior evening, on 000724,
131547 - following up my call to Jack leting him know Cliff's hotel and phone
131548 - number in Palo Alto.  Jack advised that Cliff seemed favorably
131549 - impressed by the SDS demonstration on Sunday, 000723. ref SDS 38 1444
131551 -  ..
131552 - Jack feels that if there was an entity to develop SDS, LANL might
131553 - contribute support of some kind under terms of some sort.
131555 -  ..
131556 - Jack mentioned that my letter to Joe Ransdell yesterday explaining how
131557 - SDS is used, ref SDS 39 0008, helped him understand the process of
131558 - Communication Metrics, more commonely called Knowledge Management. In
131559 - our discussion yesterday, Jack mapped out on his marking board a
131560 - simplified concept...
131561 -
131563 -  ..
131565 -  ..
131566 - Knowledge Management  =  Information Management  +  Time Management
131567 -
131568 -
131569 - Since time and information (including "subjects) are the ingredients
131570 - the human mind uses for reasoning, this formula represents a way for
131571 - technology to augment human intelligence; what Eric Armstrong calls
131572 - the simplified "elevator" version to help people grasp foundational
131573 - concepts, build interest based on association with familiar words, and
131574 - facilitates discusison under a unified subject, which he proposed on
131575 - 000423. ref SDS 17 5096
131577 -  ..
131578 - It reflects analysis on 000425. ref SDS 19 1904
131579 - ..
131580 - Semiotics discussed on 000713, ref SDS 34 4176, is another easy
131581 - way to explain KM as integrating...
131582 -
131584 -  ..
131585 -
131586 -              Communication + Meaning + Inference
131587 -
131588 -
131589 - Jack wants to discuss his draft buisiness model, ref DRT 1 0002, with
131590 - Pat and Cliff tomorrow. ref DRT 1 3960
131592 -  ..
131593 - Would be helpful if Morris could attend.
131595 -  ..
131596 - These ideas are very important to maintain focus on the big picture
131597 - that distiguishes the SDS KM effort from others, as a rationale for
131598 - participating.  We can deliver something others cannot, demonstrated
131599 - by the SDS record on the web.
131600 - ..
131601 - Yesterday, Jack got a little exasperated hearing again that SDS
131602 - improves the alphabet.  He feels this is more of a metaphor than an
131603 - actual assessment of what SDS is doing.  Jack cited constant use of
131604 - "flat tax" as a dogmatic prescription for change that arises in the
131605 - political arena, as a similar annoyance to hearing Rod harp on the
131606 - alphabet.
131608 -  ..
131609 - The reason this seems like a good approach is that enhancing alphabet
131610 - technology focuses attention on the sea change we are thinking about
131611 - undertaking.
131613 -  ..
131614 - Nobody has done this for 2000 years.
131615 - ..
131616 - Jack is proposing XML editor. ref DRT 1 3450
131617 -
131618 -     This supports Eric's specs reviewed on 000505. ref SDS 24 4951 and
131619 -     also, ref SDS 24 5002  Eric first proposed XML editor on 000129.
131620 -     ref SDS 8 0957
131621 -
131622 -     On 000425 Sandy Klausner proposes SGML for segmenting formatting
131623 -     from text. ref SDS 18 3051
131625 -        ..
131626 -       [On 000802 XML is mentioned in business plan. ref SDS 44 2809
131627 -
131628 -
131629 -
131631 -  ..
1317 -
1318 -
1319 - 2028 called Morris
1320 -   ..
132001 - He recieved the letter at work, but did not have time to review.
132002 - While we talked he tried to some system maintenance, so he can read
132003 - the letter forwarded to him, but there was a snag of some kind.
132005 -  ..
132006 - I read some of the letter discussing him attending tomorrow.
132008 -  ..
132009 - Morris is pretty sure his schedule will not permit him to attend.
132011 -  ..
132012 - He raised a number of questions about Jack's plan, based on a general
132013 - understanding from my reading.
132015 -  ..
132016 - Obviously, this is the time to sort out these matters, so it would be
132017 - ideal for Morris to attend tomorrow to explore things with SRI and
132018 - LANL, and of course Jack.
132019 - ..
132020 - I am better as a listener at this point.  But if Morris cannot
132021 - attend, then I will procede.  He will review Jack's letter in the
132022 - morning, and we can talk about his ideas for guidance on the meeting
132023 - with Jack and the guys later in the afternoon.
132024 - ..
132025 - Another possibility might be for Morris to stop by SRI after he
132026 - finishes at work, since we will not start these discussions until
132027 - after 1800.  He will miss Cliff's presentation, but the more important
132028 - discussion will be with a smaller group.
132030 -  ..
132031 - We could also just talk on the speaker phone, so he doesn't have to
132032 - battle traffic.
132033 -
132034 -
132035 -
132036 -
132037 -
132038 -
1321 -

SUBJECTS
Debugging by Many People
Ownership Investment Lost
Product Design, Control Lost
Management Cannot Make Assignments
API Open Source Proposed for SDS Project

1907 -
190801 -  ..
190802 - Ownership, Patents, Licensing Require Review
190803 -
190804 - Follow up ref SDS 40 1222, ref SDS 32 1222.
190805 -
190806 - Commercial entity to produce SDS for KM...
190807 -
190808 -       As discussed yesterday, Jack proposes under "Relationships" a
190809 -       composite entity where Welch develops and owns SDS engine.
190810 -       ref DRT 1 5562
190812 -        ..
190813 -       VC provides funds to accomplish development for ownership stake
190814 -       in entity and future profits.  Initially, VC will get 5% of
190815 -       Entity.
190817 -  ..
190818 - Open Source API
190819 -
190820 -       Jack proposes that the Entity licenses to SRI and others under
190821 -       open source criteria something which would enable others to
190822 -       develop competing versions of SDS.
190823 -
190824 -         [On 000802 incorporated into business plan. ref SDS 44 2376
190826 -          ..
190827 -         [On 000803 Jack submits sample license. ref SDS 45 0001
190829 -          ..
190830 -         [On 010323 Jack proposes that API is first task for developing
190831 -         OHS. ref SDS 49 IT6M
190833 -        ..
190834 -       This goes beyond objective to create a single stantard on which
190835 -       others can build applications. that support e-business and
190836 -       Enterprise Management, discussed with Jack on 000503.
190837 -       ref SDS 22 6903
190838 -       ..
190839 -       It therefore seems to conflict with Pat's comment
190840 -       yesterday that the Welch investment of 15+ years to create SDS,
190841 -       set out in the record on 000723 in the meeting with Cliff,
190842 -       ref SDS 38 2583, cannot reasonably be given away. ref SDS 40
190843 -       5530  Maybe we should give some of it away, but under what
190844 -       terms?   A VC gets some ownership in exchange for money.  What
190845 -       is the consideration from Open Source folks?
190847 -        ..
190848 -       Why should VC finance development of SDS, and if SDS is
190849 -       successful in providing development path, but for one reason or
190850 -       another is not successful in marketing; yet an open source
190851 -       entity using SDS product specs financed by VC is successful with
190852 -       an implementation for various reasons, then VC would not
190853 -       benefit???
190854 -       ..
190855 -       Morris asked this evening what benefit entity gets from
190856 -       giving out the API information for open source to develop
190857 -       competing products????
190858 -       ..
190859 -       One benefit might be advertising for SDS.
190861 -        ..
190862 -       Though not in Jack's proposed license, we might add a provision
190863 -       that requires all products, advertising and work product
190864 -       produced under the Open Source license to implement SDS in any
190865 -       form, must include notice of...
190866 -
190867 -
190868 -                  Complies with Welch standards for SDS
190869 -
190871 -        ..
190872 -       If folks are then able to start putting SDS records on the web,
190873 -       and people encounter those records, this will grow awarenss of
190874 -       SDS and grow the market, as Morris and I discussed previously.
190875 -
190876 -           [On 000726 Jack sent a letter seeming to concur in principle
190877 -           with this point. ref SDS 42 1222
190878 -       ..
190879 -       A key question will be when requirements have to be
190880 -       released to open source?
190882 -        ..
190883 -       Do we release preliminary development versions, which is a sort
190884 -       of concurrent release procedure?  Or, do we release after we
190885 -       have completed the first version and are satisfied it is ready
190886 -       for distribution to the market, at which point we have a 2 year
190887 -       lead, and could stay ahead of the other ponies on the race track
190888 -       that we build, per Eric's analysis on 000403. ref SDS 13 5956
190889 -       and ref SDS 13 0702
190891 -        ..
190892 -       Another idea would be that entity receives a royalty of $10 for
190893 -       every product sold that uses SDS stuff.  In that setting, we
190894 -       might prefer to just let the market stampede to sell the thing,
190895 -       and simply collect royalties.
190896 -       ..
190897 -       If SDS flies, it could spread rapidly, because people will
190898 -       quickly catch on to the power.  There will be a prestige thing,
190899 -       then it will become a necessity.
190901 -        ..
190902 -       On the other hand, this might conflict with the spirit of Open
190903 -       Source.  We need to discuss with Jack and others their thinking
190904 -       on how to address this stuff.
190905 -
190906 -
190907 -
190908 -
190909 -
190910 -
190911 -
190912 -
190913 -
190914 -
1910 -
Distribution. . . . See "CONTACTS"