Click here to comment!
1...How far along is the XML engine?
CONTACTS
0201 - CoreTalk Corporation
020101 - Mr. Sanford Klausner
020102 - CEO Founder
SUBJECTS
Alliances Fernhout, Paul, 000601
Ownership Development
Ownership of SDS Record
Find people
Planning Next Version
Development Plan
Investors
Stable Capability Needed Improve Productivity Absorb into Work Practi
1410 -
1410 - ..
1411 - Summary/Objective
1412 -
141201 - Follow up ref SDS 32 0000, ref SDS 31 0000.
141202 -
141203 - Sandy Klausner expressed interest in SDS for a new venture to develop
141204 - and market KM capabilities. He reports having some capital, new
141205 - ideas, methods and tools to use XML technology. Eric Armstrong is
141206 - considering joining Sandy's new venture. Sandy has gained attention
141207 - at Intel on moving KM issues toward silicon. In the PM received a
141208 - business presentation and NDA. Sandy feels he can support SDS, and
141209 - requests response.
141210 -
141211 - [On 040112 received request to suppress confidential information.
141212 - ref SDS 44 5Y7J
141214 - ..
141215 - Submitted ref DIT 1 0001 proposing SDS as "killer" KM application for
141216 - Enterprise Management; request permission to discuss the matter with
141217 - Morris. There was an email delivery problem. ref SDS 0 3965
141218 -
141219 - [On 000609 solved email delivery problem; Sandy called to follow
141220 - up. ref SDS 33 0001
141222 - ..
141223 - [On 000614 received businss plan v10. ref SDS 38 0001
141225 - ..
141226 - [On 000617 received Collabrium requirements. ref SDS 39 0001
141228 - ..
141229 - [On 000621 Sandy met with Morris. ref SDS 40 0001
141231 - ..
141232 - [On 010913 Sandy submitted review of Coretalk developed by Eric
141233 - Armstrong. ref SDS 43 0001
141234 -
141235 -
141237 - ..
1413 -
1414 -
1415 - Discussion
141601 - ..
141602 - CoreTalk Developing Venture to Create Knowledge Management
141603 -
141604 - Sandy advised he is developing a start up, evidently in the KM field.
141605 -
141606 - He has been developing knowledge management capabilities for the past
141607 - 12 years. He is about 49.
141612 - ..
141613 - Sandy asked if I am aware of his work?
141615 - ..
141616 - Sandy submitted a letter to the DKR team on 000424 which seemed to
141617 - present AI solutions for knowledge management. ref SDS 22 0002
141619 - ..
141620 - Sandy said there is a lot of industry interest in moving forward with
141621 - breakthrough technologies in knowledge management.
141627 - ..
141628 - This aligns with the report on 000324 during a DKR meeting at SRI,
141629 - which reported there is a lot of money being invested in knowledge
141630 - management projects, and many have not panned out. ref SDS 17 4877
141631 - Later, on 000330 an SRI KM expert reported that nobody has established
141632 - a solution. ref SDS 18 2627 Previously, on 991213, at a professional
141633 - conference attended by people from around the world, many newly
141634 - appointed to be "Manager of Knowledge Management," everybody wanted an
141635 - application to perform KM, and nobody could explain what that would
141636 - be. ref SDS 15 9030
141637 -
141638 -
141640 - ..
141641 - SDS Core of Knowledge Management, Engine of Enterprise Management
141642 - CoreTalk Technology Based on Binary XML for Atomic Data Structures
141643 -
141644 - Sandy advised that he has reviewed SDS on the web, e.g., POIMS,
141645 - ref OF 1 6221, and found that SDS offers advanced capability that is
141646 - not available from other sources.
141648 - ..
141649 - Sandy mentioned the discussion of ontology that occurred yesterday,
141650 - ref SDS 30 0001, supporting a letter to Jack Park and the DKR team,
141651 - the previous day disclosing lack of evidence for AI type processing.
141652 - ref DIP 8 1640
141653 -
141654 - [...below CoreTalk business presentation mentioned ontology.
141655 - ref SDS 0 8874
141657 - ..
141658 - Sandy has reviewed the record of the meeting with Eric and Morris at
141659 - Intel on 000517, ref SDS 24 0000, which explains a proposal to use SDS
141660 - as the engine of knowledge management that makes possible an effective
141661 - form of Enterprise Management. ref SDS 24 1920
141662 - ..
141663 - Sandy seemed to indicate having met several times with Eric
141664 - Armstrong.
141665 - //
141666 - He feels that Eric is close to joining the CoreTalk project.
141667 - //
141668 -
141669 - [...below, CoreTalk business presentation shows an XML engine
141670 - product idea that seems to align with Eric's CDS requirements.
141671 - ref SDS 0 6248
141672 - ..
141673 - Sandy commented that Atomic Data Structures are the key to
141674 - effective knowledge management.
141675 -
141676 - This may have helped Eric with submission of requirements for data
141677 - structures to support the DKR project, on 000605. ref SDS 29 6984
141679 - ..
141680 - Sandy feels XML may not be a good design path because it is difficult
141681 - to "machine process."
141683 - ..
141684 - He has in mind a "binary XML" methodology to improve XML.
141685 -
141686 - It will be interesting to learn about Sandy's ideas in relation to
141687 - the underlying concept of binary forces in nature cited in the
141688 - NWO... paper, ref OF 3 4346, reviewed on 990716. ref SDS 11 4940
141689 -
141690 - Binary XML is shown in para 7 of the bus. presentation, per below.
141691 - ref SDS 0 8874
141693 - ..
141694 - I commented that SDS and Knowledge Management do not require XML, nor
141695 - any additional, new technologies in order to improve productivity by
141696 - an order of magnitude, as shown by the SDS record on the Internet.
141698 - ..
141699 - This can be seen from the scenario explaining Communication Metrics.
141700 - ref OF 2 0001 On 000227 Dick Karpinski reviewed SDS for the DKR
141701 - project. ref SDS 16 0897
141703 - ..
141704 - It may be that Sandy's capabilities can enhance SDS. That prospect
141705 - justifies investigation. However, the first priority is to settle on
141706 - what constitutes knowledge, set out on 000517, ref SDS 24 5096, and
141707 - again on 000518, ref SDS 25 3528, then think about how to "manage"
141708 - that process, discussed in POIMS, as plan, perform report. ref OF 1
141709 - 1104
141711 - ..
141712 - Sandy feels we are working toward the same objectives at different
141713 - levels. He expressed interest in supporting SDS as the core engine of
141714 - knowledge management, set out in the letter to Jack Park, ref DIP 7
141715 - 0895, on 000605. ref SDS 28 1760
141716 -
141717 - The prospect of an explosion of new methods underscores the need
141718 - to develop fundamentals for augmenting human thinking, so that
141719 - tools can change, but the focus remains on enhancing span of
141720 - attention, memory and reasoning. Did not discuss the need for
141721 - stability that enables people to apply knowledge tools, like the
141722 - alphabet, per meeting with Bill on 960823. ref SDS 6 4747
141723 -
141724 -
141726 - ..
141727 - Driving Core Solution Toward Microprocessor (Silicon)
141728 -
141729 - Sandy related a meeting he had in March with two top execs at Intel.
141730 - The head of EE at UCB also attended the meeting. Sandy presented a
141731 - plan or design for a microprocessor. He feels his idea was well
141732 - received, and that Intel may be interested in his current project.
141733 -
141734 - [On 000610 notified Morris about this point. ref SDS 34 5074
141736 - ..
141737 - [On 000621 Sandy reported discussion with Morris. ref SDS 40 4864
141739 - ..
141740 - It was not clear in our discussion today the correlation between
141741 - design for a microprocessor and KM, but part of it may have been that
141742 - Sandy is thinking about how to process atomic data structures more
141743 - efficiently.
141745 - ..
141746 - Actually, Sandy's business presentation v6 provides some clarification
141747 - discussing in the section on the XML Engine the idea of driving the
141748 - solution toward silicon, per letter, ref DRP 3 1610, and reviewed
141749 - below. ref SDS 0 1551
141750 -
141751 - [On 000610 CoreTalk business presentation v10 modifies the
141752 - explanation on silicon. ref SDS 38 6300
141754 - ..
141755 - I mentioned discussions with Morris about making SDS part of the
141756 - underlying capability in the microprocessor; so, this reflects common
141757 - awareness of need to address Knowledge Management as a core issue.
141758 -
141759 -
141761 - ..
141762 - Paradigm Shift from Documents to Knowledge Space Big Challenge
141763 -
141764 - Sandy commented that paradigm shifts are very difficult to accomplish
141765 - in moving people to a new way of doing things.
141767 - ..
141768 - This is a big challenge in making new technologies successful.
141770 - ..
141771 - Lynn Conway framed the issue well noting the titanic struggle to get
141772 - Intel and others to adopt VLSI technology in the late 70s or early
141773 - 80s, reported on 960612. ref SDS 5 1368 Andy Grove explains the
141774 - challenge as "walking through the valley of death," reviewed on
141775 - 980307. ref SDS 7 4674
141777 - ..
141778 - The record shows success is mostly luck; requires good ideas, good
141779 - implementation; hard work, right mix of people, i.e., effective
141780 - chemistry, enough money to be wrong, and fix things, e.g., design,
141781 - production, marketing, plus favorable market conditions. If the right
141782 - mix of enabling factors happen to converge, it may work, as related in
141783 - the record on 931008. ref SDS 1 6480
141785 - ..
141786 - Favorable market conditions are emerging for KM as a result of the
141787 - "Information Highway," which creates information overload that
141788 - overwhelms people. also on 931008. ref SDS 1 4757 The tools people
141789 - are rushing to buy, e.g., cell phones, email, in an attempt to solve
141790 - the problem, actually makes it worse, as reported in NWO...
141791 - ref OF 3 9449
141793 - ..
141794 - Sandy will review POIMS and other publications on the web...
141795 -
141796 -
141797 - http://www.welchco.com/00601.HTM
141798 -
141799 -
141800 - ...and let me know if he wants to follow up.
141801 -
141802 -
141803 -
141804 -
141805 -
1419 -
SUBJECTS
Alliances
Business Presentation v5, Powerpoint
Non-disclosure Statement
CoreTalk Improve SDS
Trade Secrets - Disclosure
Non-disclosure Agreements
Killer Application
Collaboration People Skills Dialog Listening KM 2 Parts People Skills
Collaboratory Supports KM by Ontology Linking SDS Engines
2511 -
251201 - ..
251202 - Business Presentation, CoreTalk Strategy
251203 - Non-disclosure Statement, CoreTalk IP Protection
251204 - Sandy Feels He Can Transform SDS into High Level Automated Tools
251205 -
251206 -
2513 -
2514 -
2515 - 1948 received letter from Sandy
251601 - ..
251602 - Received ref DRT 1 0001 from Sandy advising he reviewed POIMS, but did
251603 - not gather how SDS works. He feels POIMS reflects awareness of KM
251604 - issues.
251606 - ..
251607 - Based on his initial review, Sandy wants to explore further how
251608 - accumulated knowledge about SDS can be packaged into a high level set
251609 - of automated tools. He reports having expertise doing this type of
251610 - transformation and integration. ref DRT 1 0936
251612 - ..
251613 - Sandy includes in his letter today a business presentation v5,which is
251614 - a Power Point file (did not include this in the record, since received
251615 - updated version the next day). He, also, encloses a non-disclosure
251616 - agreement, intended for signature. ref DRT 1 0002
251617 -
251618 - [On 000609 Sandy called to follow up. ref SDS 33 0001
251620 - ..
251621 - [On 000610 received updated business presentation (v 6),
251622 - ref DRP 3 0002, of Powerpoint file. ref SDS 34 0001
251624 - ..
251625 - [On 000613 letter from Sandy on v8. ref SDS 37 0001
251627 - ..
251628 - [On 000614 received call from Sandy. ref SDS 38 0001
251630 - ..
251631 - Non-disclosure para 3 relates to knowledge management principles...
251632 -
251633 - No copies will be made or retained of any written INFORMATION
251634 - provided under this Agreement. Upon CORETALK's written request,
251635 - or upon termination of this Agreement, RECIPIENT will
251636 - immediately transfer or return to CORETALK all documents in its
251637 - possession which contains the INFORMATION including but not
251638 - limited to written notes, graphics, photographs, spreadsheets,
251639 - contracts, software or memoranda. ref DRT 1 8025
251641 - ..
251642 - [On 000609 Sandy decided to wait until after an initial
251643 - meeting to address matters of non-disclosure. ref SDS 33 0783
251645 - ..
251646 - As shown above, to be aware (also "cognizant") of information in
251647 - Knowledge Space (see POIMS, ref OF 1 6649) requires information be
251648 - connected to support review, as set out in the record on 000601
251649 - reviewing Paul Fernhout's ideas on supporting SDS. ref SDS 26 0798
251651 - ..
251652 - This is part of working out new modalities for transitioning from
251653 - documents to Knowledge Space.
251655 - ..
251656 - Products: Collabrium, XML Engine
251657 -
251658 - CoreTalk seems to identify two products...
251659 -
251660 - 1. XML Collabrium(TM)
251661 -
251662 - Enable collaboration between enterprise business
251663 - professionals to build a broad range of information
251664 - infrastructures, ref DRP 3 1410
251666 - ..
251667 - Comment...
251669 - ..
251670 - There is a graph in point 10, that seems to show some
251671 - hardware arrangements for Internet management. ref DRP 3
251672 - 2860
251674 - ..
251675 - This sounds and looks like a form of the DKR that Doug
251676 - Engelbart and SRI are thinking about to improve email, per
251677 - Eric's Collaborative Document System (CDS), set out on
251678 - 000505. ref SDS 23 4392
251679 -
251680 - [On 000614 Collabrium has e-business focus. ref SDS 38
251681 - 1576 and ref SDS 38 2068
251683 - ..
251684 - [On 000617 reviewed Sandy's Collabrium requirements, show
251685 - strong emphasis on transaction support for e-business
251686 - market. ref SDS 39 0001
251688 - ..
251689 - [On 000623 Jack Park proposes Collaborative Evolutionary
251690 - Epistomology for OHS. ref SDS 41 4752
251692 - ..
251693 - [On 001130 Jack proposes linking SDS with ontology to
251694 - form collaboratory. ref SDS 42 BQ3F
251695 - ..
251696 - In combination with CoreTalk XML engine, discussed
251697 - below, ref SDS 0 3264, the aims of the Collabrium, seems to
251698 - align with Eric Armstrong's initial product objectives for
251699 - improving email explained in the record on 000423,
251700 - ref SDS 21 5943, and described as a Collaborative Document
251701 - System (CDS) in requirements reviewed on 000505. ref SDS 23
251702 - 0001 Requirements were updated recently on 000605.
251703 - ref SDS 29 0782
251705 - ..
251706 - On 000227 Eric reviewed challenge of getting "professional"
251707 - people to adopt a new work practice, ref SDS 16 5810,
251708 - because cost of failure is high. ref SDS 16 5952 He expects
251709 - to win converts by demonstrating the benefits of stronger
251710 - OHS/DKR tools, based on the new reality of the Internet.
251711 - ref SDS 16 0896
251712 -
251713 - May need stronger, proactive, pull to demonstrate cost
251714 - savings from changing to better management, in order to
251715 - gain big movement of customers that sustains revenue
251716 - projections, discussed in para 15, per below.
251717 - ref SDS 0 3478
251719 - ..
251720 - Education is a fruitful area because of desire to pour
251721 - money into this sector, per planning on 951012.
251722 - ref SDS 4 0000
251724 - ..
251725 - Engineering management per proposal to Intel on 990524
251726 - is good prospect. ref SDS 8 0876
251727 - ..
251728 - Medical mistakes are a high profile problem that
251729 - may provide a lever to force application of stronger
251730 - tools for daily management, per letter, ref DIP 5 0001,
251731 - on 990924. ref SDS 12 0001
251732 -
251733 - [On 000611 received letter from Doctor Braddock at
251734 - Univ Washington, asking about progress, sent letter
251735 - explaining what is needed. ref SDS 36 5538
251737 - ..
251738 - Medical practice requires performance of tasks that
251739 - avoid mistakes, which CoreTalk systems may support, but
251740 - which doctors and patients would rather die than
251741 - perform, as reported on 990625. ref SDS 10 4185
251742 -
251743 - [On 000613 sent letter to Sandy citing opportunity.
251744 - ref SDS 37 0990
251746 - ..
251747 - We might be able get support from AARP and other groups
251748 - to force performance of life saving management support
251749 - for doctors and patients, using CoreTalk technology.
251750 - This would demonstrate that better management can help
251751 - the CEO of a cereal company, a railroad company, a
251752 - government agency, a computer company, a college, and so
251753 - on.
251755 - ..
251756 - Government bumbling is probably less than in the private
251757 - sector, but NASA and other high profile agencies might
251758 - be a good target for a contract that would secure
251759 - revenue, so they can report to congress that steps have
251760 - been taken to reduce bumbling, per record on 991001.
251761 - ref SDS 13 0001
251763 - ..
251764 - Another way to encourage people to use intelligence is
251765 - to sell advertising space. Wrap life saving medical
251766 - intelligence around an ad for twinkies for Budwiser, and
251767 - it might reduce the cost enough, to encourage doctors
251768 - and patients to take a chance on improving the work.
251770 - ..
251771 - The same advertising revenue model, might work in other
251772 - businesses.
251774 - ..
251775 - A cognitive laboratory equipped to perform information
251776 - analysis, manage data relationships, & build exchange
251777 - capabilities, ref DRP 3 5478
251779 - ..
251780 - Comment...
251782 - ..
251783 - Seems to align with Jack Park's AI goals, which showed up in
251784 - Eric's specs v0.7, reviewed on 000601. ref SDS 27 4967
251786 - ..
251787 - Sandy commented on 000424. ref SDS 22 2068
251789 - ..
251790 - Need an example of something that might be accomplished with
251791 - this capability. How often would it be used; how much
251792 - effort is required to supplement normal reliance on
251793 - experience for making judgements?
251795 - ..
251796 - A virtual auditorium where professionals meet in real time
251797 - to develop graphical data schemata that directly execute
251798 - without hand coding. ref DRP 3 5082
251800 - ..
251801 - Comment...
251803 - ..
251804 - Seems like this would be useful to have even without
251805 - professionals meeting. A professional or non-professional
251806 - might use this capability to advantage.
251808 - ..
251809 - Need example.
251811 - ..
251812 - 2. XML Engine
251813 -
251814 - Unique operations: tree traverse, edit, read/write, queue, &
251815 - archive, ref DRP 3 3510
251816 -
251817 - Comment...
251819 - ..
251820 - Sounds similar to OHS editor, intended to support
251821 - Collabrium, per above. ref SDS 0 8446
251823 - ..
251824 - How far along is the XML engine?
251825 -
251826 - [On 000616 review of Collabrium Plexus shows strong
251827 - initial requirements. ref SDS 39 0001
251829 - ..
251830 - Is there work product?
251831 - ..
251832 - Binary XML is cited as a CoreTalk innovation in para
251833 - 7. ref DRP 3 0005 How does it contribute to products and
251834 - earnings?
251836 - ..
251837 - Ontology is listed in para 8, explaining Binary XML, to
251838 - provide precise information expression. ref DRP 3 1326
251839 -
251840 - What does this mean; how will it be accomplished, based
251841 - on review reported 000607? ref SDS 30 0001
251842 -
251843 - Who creates and manages the "ontology" specs. What
251844 - happens to somebody who adds something without telling
251845 - anybody?
251847 - ..
251848 - Any examples?
251850 - ..
251851 - Sandy mentioned ontology in our discussion this morning,
251852 - per above. ref SDS 0 5980
251854 - ..
251855 - Is Sandy using the XML engine to develop the CoreTalk
251856 - project, for example to write up the record and correspond?
251858 - ..
251859 - Is there any work product to show proof of concept?
251861 - ..
251862 - Provides API support, data format translations, & schema
251863 - transforms
251865 - ..
251866 - Efficient data structure manipulation in Engine, outside of
251867 - application
251869 - ..
251870 - Virtual architecture targets server, client, & silicon
251871 - deployments
251872 -
251873 - [On 000621 Sandy reported discussion with Morris.
251874 - ref SDS 40 4864
251875 -
251877 - ..
251878 - Revenue and Profitability Not Clearly Supported by Plan
251879 -
251880 - There is a chart in para 15, that seems to anticipate revenues of
251881 - $200M in five years. ref DRP 3 1682
251882 -
251883 - There is no math nor explanation of how this will be achieved.
251884 -
251885 - [On 000611 Morris explains that reliance on metered service
251886 - charges is not an effective revenue model.
251888 - ..
251889 - The business model in para 14 shows revenue is expected from
251890 - royalties, which nominally would be relatively assured, if
251891 - successful in securing such an arrangement. ref DRP 3 4592
251893 - ..
251894 - If royalty idea doesn't happen, or takes longer to establish, how
251895 - will it impact revenue?
251897 - ..
251898 - Need a lot of marketing to develop a secure revenue stream that
251899 - pays the bills, while the team figures out how to deploy what seems
251900 - to be very advanced technology.
251902 - ..
251903 - One idea is medical practice, per above. ref SDS 0 6248
251905 - ..
251906 - Another is a government contract; however, most of these contracts
251907 - get handed out through contacts, girls, liquor, etc, according to
251908 - Howard Hughs. Do we have these resources?
251909 -
251910 -
251912 - ..
251913 - SDS Compelling Application for KM, Enterprise Solutions on Internet
251914 -
251915 - Submitted ref DIT 1 0001 to Sandy explaining SDS can be the "Killer
251916 - Application" essential to make a KM effort successful, per IBM on
251917 - 941114, ref SDS 3 2473, and based on Christensen's explanation of a
251918 - "disruptive technology," reviewed with Morris on 990527. ref SDS 9
251919 - 5258 IBM's presentation to the DKR team at SRI on 000413 cites
251920 - limited capacity of human mental biology that causes information
251921 - overload, leading to need for SDS, ref SDS 20 4822, also explained in
251922 - the NWO... calling for Communication Metrics. ref OF 3 4925
251924 - ..
251925 - Compelling "killer" application was first explained in the record on
251926 - 940615. ref SDS 2 3001
251928 - ..
251929 - On 000403 reviewed business model for adding value to current work
251930 - practice. ref SDS 19 3180 Eric Armstrong reviewed marketing
251931 - challenges. ref SDS 19 5956
251933 - ..
251934 - Cite Christensen's disruptive technology ideas, reviewed on 990527.
251935 - ref SDS 9 5258
251937 - ..
251938 - Explained Communication is biggest risk in enterprise, ref DIT 1 1056,
251939 - from letter to Dave Vannier at Intel on 991007, ref SDS 14 7920, per
251940 - analysis of Morris' comments on letter from Fernhout. ref SDS 31 7208
251942 - ..
251943 - Solution is SDS, ref DIT 1 6231, as further explained in the letter to
251944 - Jack Park, ref DIP 7 0895, on 000605. ref SDS 28 1760
251945 -
251946 -
251947 -
251948 -
251949 -
251950 -
251951 -
251952 -
2520 -
Distribution. . . . See "CONTACTS"