Click here to comment!
1...These capabilities (solving limitations of existing HTML apps)
CONTACTS
SUBJECTS
Editing Core Capability
Specifications
Xanadu Hypertext Editor, 000305
History of Web
Xanadu Web Project, 000305
KM Tools with Same Objectives as OHS/DKR
1108 -
1108 - ..
1109 - Summary/Objective
1110 -
111001 - Follow up ref SDS 85 0000, ref SDS 84 0000.
111002 -
111003 - Xanadu developed by Ted Nelson beginning in 1960, appears to offer
111004 - capabilities for DKR and OHS along the lines being pursued by
111005 - Bootstrap and the Colloquium. It is open source, ref SDS 0 0782, and
111006 - seems to have extensive version control, ref SDS 0 4725, including an
111007 - extended feature of transclusions. ref SDS 0 0786 There is no evident
111008 - body of work demonstrating implementation that shows viability. To
111009 - solve problems of using mainstream web application, Xanadu applies an
111010 - alternative hypertext architecture from HTML and XML. ref SDS 0 1188
111011 - This may conflict with Colloquium objectives and planning, however,
111012 - the overall goal appears to line up with the DKR. Review of Xanadu's
111013 - explicit plan for a single address appears to adopt a centralized
111014 - "mainframe" concept that requires consideration with respect to risk
111015 - management. ref SDS 0 0184
111016 -
111017 - [On 000306 Colloquium v0.2 Editor spec has new section on
111018 - version control. ref SDS 86 4060
111019 -
111020 - [On 001224 Xanadu developed system of attribution to pay for
111021 - use of Internet resources. ref SDS 96 0001
111022 -
111023 -
111024 -
111025 -
1111 -
1112 -
1113 - Progress
111401 - ..
111402 - Xanadu Supports Colloquium Objectives for DKR Editor
111403 -
111404 - Received ref DRT 1 0001 from John Deneen who provides a link to Ted
111405 - Nelson's work on the Xanadu project, and to Ted's virtual editing and
111406 - microversions technology....
111407 -
111408 -
111409 - http://www.sfc.keio.ac.jp/~ted/OSMIC/osmicTime.html
111410 -
111411 -
111412 - ...which is in turn linked to the Xanadu project...
111413 -
111414 - John's letter responds to Joe Williams inquiry, ref DRP 15 0001, on
111415 - 000303, about progress by the Colloquium team on a specification for
111416 - the DKR. ref SDS 84 0001
111417 -
111418 - On 000127 John suggested the Colloquium develop a DKR that provides
111419 - groupware for "virtual," electronic conferencing and collaboration
111420 - using the web. ref SDS 58 8960
111421 -
111422 - [On 000322 received request to coordinate with John on traveling
111423 - for project meeting. ref SDS 89 2332
111424 -
111425 - Xanadu is explained at...
111426 -
111427 -
111428 - http://www.sfc.keio.ac.jp/~ted/XU/XuPageKeio.html
111429 -
111431 - ..
111432 - Nelson Began Work on Hypertext Capabilities in 1960
111433 -
111434 - Xanadu is the name for Ted Nelson's hypertext work since 1960. From
111435 - 1988-92, Xanadu was owned by XOC, Inc., a subsidiary of Autodesk,
111436 - Inc., but is no longer connected officially with XOC, Inc., or with
111437 - the software developed there. ref OF 5 1296
111438 -
111439 - Xanadu Structure web page seeks to dispell...
111440 -
111441 - The myth: Xanadu is the dream of a universal populist publishing
111442 - network, fulfilled by the World Wide Web. ref OF 6 0001
111443 -
111444 - ...and maintains...
111445 -
111446 - The truth: Xanadu is a specific structure which it is important to
111447 - understand, which is PARTICULARLY WELL SUITED to electronic
111448 - publishing networks. ref OF 6 2322
111449 -
111451 - ..
111452 - Xanadu Has Influenced Hypertext Development on Web
111453 -
111454 - Tim Berners-Lee, designer of the original Web protocols, beginning in
111455 - about 1990, was unaware of Xanadu. Evidently he had seen HyperCard,
111456 - and what he created was essentially HyperCard(R) on the Internet,
111457 - ref OF 5 0540, which may have been originally influenced by Xanadu.
111458 - ref SDS 0 5229
111459 -
111460 - Xanadu influenced following products and systems, ref OF 5 4899 ...
111461 -
111462 - Lotus Notes, created by Ray Ozzie
111463 -
111464 - HyperWave(tm), created by Hermann Maurer and team
111465 -
111466 - MicroCosm(tm), created by Wendy Hall and team (and its offspring,
111467 - Multicosm and WebCosm).
111468 -
111469 - ..
111470 - Xanadu maintains it influenced, ref OF 5 1845 ...
111471 -
111472 - HyperCard(tm), created by Bill Atkinson, which formed the basis of
111473 - the web. ref SDS 0 0621
111474 -
111475 - Mosaic(tm), created by Marc Andreessen (under Larry
111476 - Smarr)
111477 -
111478 -
111480 - ..
111481 - OSMIC - Open Standard for Media Interconnection
111482 - Virtual Editing and Microversions
111483 -
111484 - A link from the source for OSMIC versioning cited in Jack Park's
111485 - letter received today, per below, ref SDS 0 3717, goes to...
111486 -
111487 -
111488 - VIRTUAL EDITING AND MICROVERSIONS
111489 - OSMIC
111490 -
111491 -
111492 - ....explains that OSMIC is a different alternative to the way we edit,
111493 - intended to give deeper control of multiple versions and re-uses of
111494 - the same material. ref OF 8 0001 It is located at...
111495 -
111496 -
111497 - ttp://www.sfc.keio.ac.jp/~ted/OSMIC/OSMICpage.html 111498 -
111499 -
111500 - [On 000306 Colloquium v0.2 Editor spec has new section on version
111501 - control. ref SDS 86 4060
111502 -
111503 - The objective of this project is to demonstrate a richer model of
111504 - time, versioning and backtrack (and only for sequential documents,
111505 - which simplifies the problem). ref OF 8 1680
111506 -
111507 - The location of original defining document is at....
111508 -
111509 -
111510 - ttp://www.sfc.keio.ac.jp/~ted/OSMIC/OSMICd1m.html 111511 -
111512 -
111513 - ...which is dated 961217, explains a hypertext environment with
111514 - advantages that exceed HTML and XML, principally in supporting richer
111515 - versioning and links by readers as well as authors. This seems to
111516 - require a single source for a body of information, which raises issues
111517 - of ownership, responsiblity and bumbling of a big super system in the
111518 - sky that maintains everything. see discussion below. ref SDS 0 9718
111519 -
111520 -
111521 -
111522 -
1116 -
SUBJECTS
Market Reduces Usefulness Lowest Common Denominator
Architecture Problems KM Linking Versioning, Eric Armstrong, 001018
Architecture Snag Linking Versioning, 001018 Eric Armstrong
Versioning Problem Design Snag 001018 Eric Armstrong
1506 -
150701 - ..
150702 - Product Upgrades Remove Capability that is Unpopular
150703 - Market Forces Inhibit and Retrack Innovation and Productivity
150704 -
150705 - Nelson explains that versioning and file locking are complex, but
150706 - have been oversimplified by mainstream vendores in order to meet
150707 - market demands for ease of use, with the result that productivity
150708 - and creativity are limited by the lowest common denominator.
150709 - ref OF 8 3456
150710 -
150711 - [On 001018 Eric Armstrong reports complexities in the
150712 - architecture for OHS that relate to linking and
150713 - versioning. ref SDS 94 3X9G and ref SDS 94 V3Y1
150714 -
150715 - This reflects a trend in software of eliminating useful
150716 - features in product upgrades, because they are not widely
150717 - popular.
150718 -
150719 - Pkzip is an example, where the date feature has been removed
150720 - from the Windows version, per the record on 000205.
150721 - ref SDS 62 0001
150722 -
150723 - More recently on 000227 W98 2nd Edition omits attribute from
150724 - file management environment. ref SDS 79 4762
150725 -
150726 - [On 000309 Tom Field complains Internet Explorer lacks
150727 - capability to organize URL listings. ref SDS 88 2142]
150728 -
150729 -
150730 -
150731 -
150732 -
150733 -
150734 -
1508 -
SUBJECTS
Open Source Development Freeware
Hypertext (Linking) Improves Productivity, Too Slow
Open Source Hyper-text Editors
Xanadu Web Project, 000305
OHS Open Hyperdocument System
Permanent URL Addresses, Main Frame Model, 000305
Bumbling Need Redundancy of PC for Dual Control
Permanent Address, Single Source
Mainframe Overtaken by Windows NT
Permanent Web Address Applies Mainframe Model
Dynamic Knowledge Repository (DKR)
Bumbling Knowledge Repository Needs Redundancy
Binary Forces Permeate Human Endeavors, Cause Stress, Conflict
Xanadu Requirements General, 000305
Impossible Track Individual Readers, Xanadu
High Tech Tourism Tools That Fail to Improve Daily Work, 000601, Marc
High Tech Tourism Productivity Less Important Ease of Use
High Tech Tourism Cannot Solve Complexity Issues in KM Versioning, Li
4220 -
422101 - ..
422102 - Open Source Code for Xanadu OHS
422103 - Xanadu Objectives - Open Hyperdocument System
422104 -
422105 - Xanadu's home page says the code sponsored by Autodesk went Open
422106 - Source at the O'Reilly Open Source Convention on 23 August, 1999. The
422107 - code may be found at UDANAX.COM...
422108 -
422109 -
422110 - http://udanax.com/
422111 -
422112 - ..
422113 - Nelson explains objective of Xanadu at following location...
422114 -
422115 -
422116 - http://www.xanadu.com.au/
422117 -
422118 -
422119 - Requirements call for storing information as a connected literature,
422120 - and to create, access and manipulate richly formatted and connected
422121 - information cheaply, reliably and securely from anywhere in the world.
422122 - Documents must remain accessible indefinitely, safe from any kind of
422123 - loss, damage, modification, censorship or removal except by the owner.
422124 - It must be impossible to falsify ownership or track individual readers
422125 - of any document.
422126 -
422127 - On 000120 Eric Armstrong asked what a DKR looks like. ref SDS 55
422128 - 3002
422129 -
422130 - ..
422131 - Objectives of Xanadu project, ref OF 5 1908, include...
422132 -
422133 - (below, Xanadu paper explaining key part of capability on
422134 - "transclusions," is not available to Netscape 4.7 browser.
422135 - ref SDS 0 3819)
422136 -
422137 - 1. High-power hypertext (much richer structures than "pages")
422138 -
422139 - 2. Any number of overlapping, publishable two-way links made by
422140 - any number of people
422141 -
422142 - 3. EVERYTHING ANNOTATABLE (special case of the above)
422143 -
422144 - 4. VERSION MANAGEMENT, with surviving portions viewable side by
422145 - side
422146 -
422147 - (transclusions?? - ref SDS 0 4725)
422148 -
422149 - 5. RIGHTS MANAGEMENT by:
422150 -
422151 - Generalized permission for on-line re-use (now called
422152 - transcopyright)
422153 -
422154 - Payment by each user for any downloaded quotation
422155 -
422156 - All quotations back-followable to their original contexts
422157 -
422158 - 6. EVERYTHING FREELY REPUBLISHABLE
422159 -
422160 - All media contents get permanent addresses, so that they can
422161 - be addressed by anyone independent of their documentary
422162 - context. On-line quotation references these permanent
422163 - addresses. All links reference these permanent
422164 - addresses, so that the same links are always on the same
422165 - content-- wherever that content is re-used.
422166 -
422167 - These objectives appear to align with Colloquium efforts to create an
422168 - Open Hyperdocument System (OHS) that supports a Dynamic Knowledge
422169 - Repository (DKR), per spec submitted by Eric Armstrong on 000210.
422170 - ref SDS 64 3971
422172 - ..
422173 - Design Requirements Xanadu Method
422174 -
422176 - ..
422177 - DKR Provides Permanent Addresses, Aligns Colloquium at Stanford
422178 -
422179 - All media contents get permanent addresses, so that they can be
422180 - addressed by anyone independent of their documentary context.
422181 - On-line quotation references these permanent addresses. All links
422182 - reference these permanent addresses, so that the same links are
422183 - always on the same content-- wherever that content is re-used.
422184 -
422186 - ..
422187 - Bumbling Risk Management
422188 -
422189 - This goal appears to align with objectives for a Dynamic
422190 - Knowledge Repository being pursued by the Colloquium at
422191 - Stanford.
422192 -
422193 - [On 000307 question raised about risks of DKR model.
422194 - ref SDS 87 4928]
422195 -
422196 - [On 000331 review of article published on 000101 seems to
422197 - propose mainframe, single-source model. ref SDS 90 1440
422198 -
422199 - A single source for all documents that is used by everyone
422200 - sounds efficient, and seems to align with visions for the
422201 - network computer reviewed on 960304. ref SDS 22 6008 On
422202 - 970617 Microsoft NT (now called Windows 2000) was reviewed as
422203 - supporting mainframe business settings in competition with
422204 - Network Computers (NC) using fiber optic cables and the
422205 - Internet. ref SDS 27 8442
422206 -
422207 - A single address for everything aligns with Dan Palanza's NSF
422208 - project proposing a system of distributed management based on
422209 - centralized administration of information, reviewed on 990718.
422210 - ref SDS 46 8966
422212 - ..
422213 - Question
422214 -
422215 - How and who maintains this "permanent" record, reviewed on
422216 - 960304. ref SDS 22 9007
422217 -
422218 - What is the method of avoiding impact of continual bumbling
422219 - that occurs in large systems? ref SDS 52 6935
422220 -
422221 - On 000208 reviewed need for personal and organizational
422222 - criteria for organizing and managing informtion, responding to
422223 - question from Colloquium about core design for knowledge
422224 - management. ref SDS 63 1024
422225 -
422226 - Human beings exist as individuals and as members of various
422227 - groups from family, church, school, job, professional and
422228 - hobby affiliations, and so only. This dual existence, as an
422229 - individual and as a member of a community, means there are
422230 - personal and organizational boundaries, and each requires its
422231 - own environment.
422232 -
422233 -
422234 -
422235 -
422236 -
4223 -
SUBJECTS
Xanadu Structure, 000305
XML Limitations, e.g. Xanadu
Web Limitations Solved by Xanadu, 000305
XML Data Format
Versioning Control
XML Limitations, Xanadu, Nelson
5308 -
530901 - ..
530902 - Linking Complex Design KM Architecture
530903 - Limitations of Web Solved by Xanadu Structure???
530904 -
530905 - Xanadu Structure web page, ref OF 6 4189, points out that Nelson's
530906 - work came before the web, and foresaw problems of...
530907 -
530908 - • one-way links
530909 - • links that break (no guaranteed long-term publishing),
530910 - • publishing comments
530911 - • version management (transclusions?? - ref SDS 0 4725)
530912 - • rights management (transclusions??? - ref SDS 0 0786)
530913 -
530914 - These issues are built into the Xanadu design, as related on the main
530915 - web page. ref OF 5 6834
530916 -
530917 - These capabilities (solving limitations of existing HTML apps)
530918 - seem to reflect goals the Colloquium has discussed for a DKR.
530919 - Does Xanadu have a record for inspection showing its design and
530920 - recommendations can be implemented, and that this improves daily
530921 - work? Where can we see it?
530922 -
530923 - [On 000407 listed as agenda item for project meetings.
530924 - ref SDS 92 5893
530925 -
530926 - [On 000601 Marcello Hoffman at SRI cautioned to make technology
530927 - useful, avoid high tech tourism. ref SDS 93 1007
530928 -
530929 - [On 001018 Eric reports complex problems desiging effective
530930 - linking systems. ref SDS 94 3X9G
530931 -
530932 - Nelson maintains the Xanadu structure can enhance usefulness of the
530933 - web. ref OF 5 7920
530935 - ..
530936 - XML Criticized as Lacking Power of Xanalogical Structure
530937 -
530938 - Nelson argues that problems of HTML can be largely solved with
530939 - xanalogical structure. ref SDS 0 1188 He believes efforts toward
530940 - Web standardization -- sequence and hierarchy as embodied in XML--
530941 - will be seen as a temporary aberration. ref OF 6 1768
530942 -
530943 - On 000124 consideration was given to using XML for DKR
530944 - project. ref SDS 56 0612
530945 -
530946 - On 000125 XML explained. ref SDS 57 7568
530947 -
530948 - On 000129 details for XML Open Hyperdocument System submitted
530949 - to Colloquium. ref SDS 59 0957]
530950 -
530951 - On 000130 Eric Armstrong submits design requirements for XML
530952 - editor. ref SDS 60 0866
530953 -
530954 - On 000131 Jack Park submits features of XML editor he is
530955 - creating. ref SDS 61 1224
530956 -
530957 - On 000218 Eric Armstrong proposed DKR might develop XML
530958 - standards for DKR, based on OASIS model. ref SDS 66 0867
530959 -
530960 - [On 000405 Paul Fernhout relates limitations of XML for KM,
530961 - i.e., knowledge representation. ref SDS 91 0005
530962 -
530963 - [On 001124 Ken Holman concurs. ref SDS 95 0001
530964 -
530966 - ..
530967 - Transclusions Accomplish Versioning in Xanadu
530968 - Version Control Accomplished by Transclusions
530969 - Visualization Xanalogical Structure Shows Cross Links of Knowledge
530970 -
530971 - Xanadu shows a diagram of a vertical rectangle with pointers crossing
530972 - at random locations from one side to the other. Headings above the
530973 - vertical lines are labeled "V1" and "V2," ref OF 6 1634 Xanadu
530974 - explains the diagram illustrates...
530975 -
530976 - What is in common between two different versions
530977 -
530978 - One person's overall work and a specific article
530979 -
530980 - All the media in the world, and a specific collection
530981 -
530982 - [On 000306 Colloquium v0.2 Editor spec has new section on
530983 - version control. ref SDS 86 4060
530984 -
530985 - [On 001018 Eric reports complex problems desiging effective
530986 - versioning. ref SDS 94 V3Y1
530988 - ..
530989 - [On 020920 Jack Park associates transclude with cut and paste
530990 - in a Microsoft Windows program. ref SDS 98 OI7H
530991 -
530992 - Each vertical line is a version-- that is, a map of the elements in a
530993 - version. Each dot on the vertical line is an element. ref OF 6 2430
530994 -
530995 - Each line between the two versions shows an element which is the same,
530996 - so the element is actually shown by both the line and the dots at its
530997 - ends. ref OF 6 6278
530998 - ..
530999 - This indicates *transclusion*, the visible identity of an
531000 - element which is in more than one place..
531001 -
531002 - [On 010124 Jack Park explains that BrowseUp processing
531003 - accomplishes tasks that are similar to "transclusion."
531004 - ref SDS 97 007P
531005 -
531006 - Maintaining and showing transclusions is the heart of xanalogical
531007 - structure. ref OF 6 1584
531008 -
531009 - Need some experience observing transclusion to really grasp
531010 - Nelson's idea, but the specific need for two way links to nail
531011 - down sequence which is the indicator of cause and effect, is a
531012 - big part of the SDS design.
531013 -
531014 - In a large-grain xanalogical system, the elements in the illustration
531015 - represent chunks-- paragraphs, sentences or cells. ref OF 6 3036
531016 -
531017 - This is a useful capability to align understandings apart of what
531018 - is entered in a document. Stated another way, documents applying
531019 - tranclusion might be support Communication Metrics.
531020 -
531021 - Seems to reflect work on 990303 reporting Miller's work on memory
531022 - chunks. ref SDS 37 2838
531023 -
531024 - Xanalogical systems still under development (xoc86, xoc92 and OSMIC)
531025 - are fine-grain. In a fine-grain xanalogical system, the elements are
531026 - text characters, individual audio samples and video frames.
531027 - ref OF 6 4446
531029 - ..
531030 - Undo and Revert
531031 - Microversioning and Virtual Versions
531032 - OSMIC Prototype Software Experimenting with Complex Versioning
531033 -
531034 - Jack's letter today, ref DRT 1 0001, links directly the Xanadu
531035 - capability for version control ideas on a DKR specification...
531036 -
531037 -
531038 - http://www.sfc.keio.ac.jp/~ted/OSMIC/osmicTime.html
531039 -
531040 -
531041 - ...which opens a Xanadu web page for...
531042 -
531043 -
531044 - Reasoning behind the OSMIC proposal
531045 - MODELS OF TIME
531046 - BACKTRACK AND GROUPWARE
531047 -
531048 -
531049 - ...to control versioning, ref OF 7 0001, which generally seems to
531050 - explain benefits for maintaining editing changes, using "undo" and
531051 - "reversion" features of popular wordprocessing in Windows and Mac
531052 - OS, also, Unix. The Osmic model seems to increase the number of
531053 - changes, undos (reversions) and, restores to prior states, perhaps
531054 - indefinitely. ref OF 7 3536
531055 -
531056 - This is described as...
531057 -
531058 - Time, backtrack and groupware are very general problems
531059 - We may think of these issues as
531060 -
531061 - 1. ways to think about time; and being gods, how best
531062 - to define it;
531063 -
531064 - 2. models of versioning (especially version states available,
531065 - past and future);
531066 -
531067 - 3. the different undo options to make available;
531068 -
531069 - 4. the issues of file locking-- who has the right to do
531070 - what to which, how and when.
531071 -
531072 - OSMIC prototype software helps experiment with, and think about,
531073 - all of these issues. ref OF 7 3550
531074 -
531075 - Nelson explains current undo and revert or restore changes,
531076 - are limited in the number of changes that can be managed, and
531077 - he proposes advantages of increasing this capability, within
531078 - the framework of version control, ref OF 7 5100
531079 -
531080 - Nelson cites experience among users of Lotus Notes indicates
531081 - that different versions do not need to be resolved; users
531082 - generally find they only need to understand their differences.
531083 - ref OF 7 2600
531084 -
531085 - Existing capability described as "naive" is diagramed. ref OF 7
531086 - 3675
531087 -
531088 - Professional naive time: LINEAR UNDO (sequential model of time)
531089 - allows more states, but still has a destructive model, losing
531090 - different versions depending on the user's choice. ref OF 7 4988
531091 -
531092 - Nelson proposes that previous work (states S6, S7, s8, s9) do
531093 - not have to be lost. There is a good case for preserving all
531094 - possible states of a branching series of edit operations. That
531095 - is what OSMIC demonstrates. ref OF 7 9775
531096 -
531097 -
531099 - ..
531100 - Osmic Supports File Locking for Collaboration with Versioning
531101 - Versioning Supports Collaboration with File Locking
531102 - File Locking for Collaboration Benefits from Version Control
531103 -
531104 - Nelson explains "file locking", where a user checks out a file and
531105 - may change it. This prevents two people from making contradictory
531106 - changes on the file at the same time (in which case whoever
531107 - presses "save" first wins). This forces everyone to accept the
531108 - work that others have previously done in the sequence, and cuts
531109 - off the option of returning to an earlier state. ref OF 7 0714
531110 -
531111 - It prevents working in parallel, where people make different kinds
531112 - of changes on the same material which may contradict each other at
531113 - first, but later be reconciled. ref OF 7 1870
531114 -
531115 - Currently, person a gets a file and works on it.
531116 -
531117 - Persons, b, c, d., also get the file and work on it. They
531118 - meet and review changes, and through whatever protocal is
531119 - established for reconciling the final result, differences are
531120 - reconciled.
531121 -
531122 - By whatever, means at some point final langauge needs to be
531123 - settled for publication. Maybe multiple versions are
531124 - published. An important need that is generally overlooked is
531125 - capturing the reasoning and the alignment of that reasoning
531126 - with sources for any changes that are made.
531127 -
531128 -
531129 - XANADU SOLUTION - Microversioning
531130 -
531131 - "Undo", destructive backtrack and file locking aren't the only
531132 - alternatives. We have a demo showing how any version in a network
531133 - of versions-- a graph structure of versions-- can be easily
531134 - changed, with all changes being kept track of. ref OF 7 3976
531135 -
531136 - A graph is shown to diagram managing alternate versions.
531137 -
531138 - Each separate change creates a new microversion. (For
531139 - convenience, we number the change and the resulting state
531140 - identically: change 2 creates state 2. A branch is given a
531141 - letter, after which new integers begin with 1 again; thus change
531142 - 2a4 creates state 2a4. Unfortunately, you cannot at present give
531143 - more convenient names to the microversions.), ref OF 7 1950
531144 -
531146 - ..
531147 - Prototype Trial Available
531148 -
531149 - Osmic privides an opportunity to download code to test the Xanadu
531150 - microversinoing capability. ref OF 7 2444
531151 -
531152 -
531153 - http://www.sfc.keio.ac.jp/~ted/OSMIC/osmicInstall.html
531154 -
531155 -
531156 - This site provides instructions, and notes that people with
531157 - expertise with Linux are well positioned to implement the
531158 - instructions and perform the trial.
531159 -
531161 - ..
531162 - Scale May Limit Value of Microversioning, Diminishing Returns
531163 -
531164 - Doug Engelbart explains in his paper on Groupware published in
531165 - 1992 and reviewed on 991222 that scale becomes a limiting factor
531166 - in designing to augment human capability.
531167 -
531168 - How is the scale factor applied to Xanadu Microversioning?
531169 -
531170 - This capability will produce a huge number of versions. How are
531171 - they managed? Who does it. The more versions, the greater chance
531172 - that someone will get upset because something is missing that the
531173 - system should have saved, etc. At some point, we have a dog
531174 - chasing its tale.
531175 -
531176 -
531177 -
531178 -
531179 -
531180 -
531181 -
5312 -
SUBJECTS
Xanadu Link Innovation, 000305
Transclusions, Xanadu, 000305
Ownership of SDS Record
Copywrite/Patent
Newton and the Apple, Humor, 000305
6107 -
610801 - ..
610802 - Transclusions Supplement HTML Linking System
610803 - Connective Structure Extremely Different
610804 - Copyright, Payment of Royalties for Use of Content on Web
610805 -
610806 - Tranclusions supported by Xanadu Structure for version control,
610807 - explained above. ref SDS 0 4725
610808 -
610809 - Xanadu connective structure is extremely different from that of
610810 - HTML or any popular system. The Xanadu connective structure
610811 - consists of both links and transclusions. ref SDS 0 4725 If you
610812 - are not willing to understand or acknowledge the simple difference
610813 - between links and transclusions-- many people are not-- then you
610814 - close the door to understanding the Xanadu system.
610815 - ..
610816 - LINKS VERSUS TRANSCLUSIONS
610817 -
610818 - In Xanadu structure, a link is a connection between things which
610819 - are different, and a transclusion is a connection between things
610820 - which are the same. Xanadu Structure shows a diagram to explain
610821 - transclusion and seems largely related to version control.
610822 - ref SDS 0 4725
610823 -
610824 - This is explained in...
610825 -
610826 -
610827 - http://www.sfc.keio.ac.jp/~ted/INFUTscans/INFUT_ExplPage.html
610828 -
610829 -
610830 - Netscape 4.7 browser could not open this source on 000305.
610831 -
610832 - This appears to conflict with Xanadu objective for open
610833 - source code and ideas. The key part of the story is missing.
610834 - ref SDS 0 3762
610835 -
610836 - The Future of Information by T. Nelson, and in various articles to
610837 - be found in our archive at...
610838 -
610839 - http://www.xanadu.com.au/
610840 -
610841 - This address has the following statement...
610842 -
610843 - Xanadu system allows people to create copies ("transclusions") of
610844 - information regardless of ownership. In order to make this
610845 - possible, the system must guarantee that the owner of any
610846 - information will be paid their chosen royalties on any portions of
610847 - their documents, no matter how small, whenever and wherever they
610848 - are used.
610849 -
610850 - Thus, transclusions may relate in part to managing ownership and
610851 - payment of royalties for information.
610853 - ..
610854 - Newton and the Apple, Scene 1 Take 3
610855 -
610856 - A thorny issue in a connected environment is if person a develops
610857 - an idea based on information from persons b, c, d..., then recasts
610858 - it in different language, do persons b, c, d..., get royalties,
610859 - and how much do they get?
610860 -
610861 - Suppose Newton used the DKR to read Copernicus, and Galileo, and,
610862 - also, to read up on picking apples for a job interview he had
610863 - coming up, since no one was buying his "new math" so far, and he
610864 - had to pay the rent. There wasn't enough bandwidth for anyone to
610865 - think about how calculus might be helpful; it sounded strange and
610866 - off-the-wall. On the job his mind was not overly taxed by
610867 - handling daily working information on picking apples, so he had
610868 - time to think about his DKR research on Copernicus and Galileo,
610869 - which eventually lead to a new way of putting two and two
610870 - together. He was lucky in finding someone to publish his theory
610871 - of gravitation, since books on math are not often big sellers.
610872 - Somehow, though his book and work catches on and he gains wealth
610873 - and fame. Then he becomes a target for those seeking a piece of
610874 - the action, notably Copernicus and Galileo.
610875 -
610876 - At trial Newton falsely says the idea on gravity came solely from
610877 - watching apples fall to the ground while on the job. He pointed
610878 - to records of the DKR showing he spent several hours reading
610879 - Anderson's complete works on apple picking, but only looked at
610880 - Galileo's work for a minute or so, and there is no record of him
610881 - looking at the deep and narrow work of Copernicus. Newton argued
610882 - this showed the primary source of his ideas was apples, and
610883 - contended that Copernicus and Galelio, while certainly brilliant
610884 - and deserving of appreciation for important contributions, should
610885 - not participate in rewards from Newton's discoveries.
610886 -
610887 - Galelio and Copernicus were undeterred in pursuing their claims.
610888 -
610889 - They produced evidence showing that the DKR had computer problems
610890 - when they upgraded their systems. Some accounts were lost and
610891 - others mixed up. They hired an expert to re-construct the record
610892 - and it showed that Newton spent several days reviewing Victoria's
610893 - Secrets and Sports Illustrated's February swimsuit issue.
610894 -
610895 - Newton testified that the DKR had indeed mixed up the records, and
610896 - recalled spending considerable time, not on the February issue of
610897 - Sports Illustrated, but on the March issue of Scientific American
610898 - featuring humming patterns of the yellow throated robin, which
610899 - contributed to advanced formulas for wave theory. He produced
610900 - calculation sheets with references to bird flight patterns, and
610901 - testified he just forgot to mention the many hours he researched
610902 - the Scientific American web site on the DKR.
610903 -
610904 - How should the proceeds from royalties for Newton's theory of
610905 - gravity be apportioned to Copernicus, Galileo, Anderson, and the
610906 - apple farmer who hired Newton, and claimed entitlement by virtue
610907 - of an intellectual property rights contract Newton signed in order
610908 - to get the job? Neither Victoria's Secrets nor Sports Illustrated
610909 - entered a claim. Several well endowed models, who appeared in
610910 - those publications, did file claims on the grounds that their
610911 - "apples" were more inspiring than those Newton was claiming led to
610912 - his great discovery.
610913 -
610914 - Well, history shows that the apple story was polished up and
610915 - passed along. But, the "real story" indicates the path of
610916 - discovery is rarely as simple and direct as the pundits suggest in
610917 - the homile about "build a better mouse trap, and the world will
610918 - beat a path to your door." Life is much more complicated, and
610919 - certainly more fun, if the records of the DKR are to be believed
610920 - at this remove.
610921 -
610922 - This issue was part of the bookkeeping project supported by NSF
610923 - for Dan Palanza, reviewed on 990710. ref SDS 44 0864
610924 -
610925 - This is a big issue using SDS, as to who owns the record.
610926 -
610927 - A search of the entire web structure produced only a single use
610928 - of transclusions, and so it is not really clear what this means.
610929 -
610930 -
610931 -
610932 -
610933 -
610934 -
610935 -
610936 -
610937 -
610938 -