transclusion

Intertwingled: The Work and Influence of Ted Nelson (History of Computing)
by Douglas R. Dechow
Published 2 Jul 2015

Ironically, much of what is actually done in such a hypertext-transclusion world—to expedite the production of knowledge artifacts—can’t be done at all in most systems of today. 15.4 The Value of Transclusion As alluded to above, transclusion is used in many systems, including virtually all hypertext systems [3, 4]. This section addresses a number of issues about transclusion such as examples, benefits, costs, trade offs, and opportunities for expanding the functionality of the concept beyond mere inclusion of original material. Existing examples of transclusion include:Images, scripts, and style sheets for web pages (invariably these are not in the base page of the webpage) Include files (and/or classes) for programs Layers in graphics programs Components stored in and dynamically accessible from a database (many web pages are database-based) 15.4.1 Benefits and Costs of Transclusion The principal benefits of transclusion are reuse of existing material (versus re-inventing the wheel), and currency (access to the latest, greatest version of material).

…

Existing examples of transclusion include:Images, scripts, and style sheets for web pages (invariably these are not in the base page of the webpage) Include files (and/or classes) for programs Layers in graphics programs Components stored in and dynamically accessible from a database (many web pages are database-based) 15.4.1 Benefits and Costs of Transclusion The principal benefits of transclusion are reuse of existing material (versus re-inventing the wheel), and currency (access to the latest, greatest version of material). The principal costs of transclusion include finding desired/appropriate transcludeable material (an instance of “the research problem”), as well as effecting the transclusion, which might involve subsetting existing material, or transforming the transcluded material. To the extent that such subsetting and transforming involves sophisticated knowledge (because the interface mechanisms are complex) the less attractive using transclusion will be.

…

The ability to have “the same content knowably in more than one place,” but with a different presentation each time, is a good example of how separating presentation properties from content is a powerful mechanism for reuse (i.e., by avoiding embedded markup, as Ted has argued for decades [7]). 15.4.6 Making Transclusions Recursive Finally, making the transclusions themselves be constellations of transcludable material further adds to the panoply of material that users can selectively reuse. 15.5 Conclusions In summary, here are some take-home messages about transclusion:Since the fastest way to do something is to not have to do it at all, the ability to reuse an existing, well-crafted, extensively-tested existing artifact (or portion thereof) is one way to avoid having to spend time and money developing that component. Transclusion offers a powerful mechanism for reusing material and thus expanding the volume of material that can be created over time.

Possiplex
by Ted Nelson
Published 2 Jan 2010

.) • interactive text systems (now called ‘word processing’— I did not know that Engelbart was doing it already) • lists of items pointing to a stored original (transclusion, edit decision list) • referential editing (editing by transclusion, now used by Wikipedia) • fine-grained transclusion based on fine-grained referential editing • “mashups” of content from different sources, but each portion connected to its original— a simple use of transclusion • “wikis,” or ever-changeable documents revised by many parties— a simple use of transclusion • links, of course (Engelbart had ‘em already) • VISIBLE links between pages (still not generally accepted) • side-by-side intercomparison of connected pages and documents, with visible connections • version management • version compare side by side • intercomparison of alternatives (now called in part decision support systems) • side-by-side, visibly connected pages as a new literary genre [may not have been in this time frame] • storage of text for permanent referential use (now called in part content management) • compositing of text from various sources (now called wikis and mashups—but always with paths back to the original contexts of each portion; in xanalogical structure, only the one mechanism is needed) • undo and redo • version management with version tree.* Later generalized (and implemented with Ken’ichi Unnai) as hypertime editing, not yet generally accepted. * I have recently heard that Bobrow was working on similar ideas at about the same time

…

I wish I could tell it in a decent electronic document—a Xanadu document of parallel pages with visible connections-- HOW THIS DOCUMENT OUGHT TO LOOK WHEN IT OPENS (links not shown, only transclusions). A proper parallel hypertext in a possible opening view. The reader is able to read the full build (right), corresponding to this assembled book, or separate narratives and threads. Visible beams of transclusion show identical content among separate pages (stories, threads, and full build). Where are the visible beams of connection in Microsoft Word, Adobe Acrobat, the World Wide Web? Unfortunately we have still not got decent documents working and deployed. (Part of the problem is that people don’t understand why they need parallelism, let alone transclusion and multiway links.)

…

But we’ve gone through so many words for it, trying to get the idea across— • quote-window • transquotation •• various others I can’t remember right now, and worst of all, • equolateration. The present definition: content re-use with path back to the original. It has many uses. No conventional document systems (like Microsoft Word or the Web) will support transclusion.* * di Iorio and Lumley have done an excellent technical analysis of alternative methods of transclusion for the World Wide Web, and why they don’t work. See Angelo Di Iorio and John Lumley, "From XML Inclusions to XML Transclusions," Proceedings of conference, ACM. the Hypertext 2009 • Editing by Pointer If you could have a list of pointers to file cards, you could cut it even finer: you could make a list of pointers to individual phrases, and build your document that way— just as pointers that would bring in the contents in the right order.

Memory Machines: The Evolution of Hypertext
by Belinda Barnet
Published 14 Jul 2013

In Wolf ’s defence, the article was written in 1995 – and it was not entirely clear in 1995 that the web would scale. As Mark Bernstein points out (2012), transclusion can also be computationally expensive, arguably outstripping the capabilities of machines from 1995 (though not, I would argue, from 2012). Regardless, history has proven Nelson right; the web has scaled, and our networks are now powerful enough to run distributed databases on numerous machines. Integral to this idea of pointing at bits of a document rather than storing multiple copies of it in memory is the concept of transclusion. An author who wishes to quote uses transclusion to ‘virtually include’ the passage in the author’s own document.

…

Because this would be reuse by reference rather than by copying, you could trace each item back to its original source. This idea – that you should be able to see all the contexts of reuse, and that you should be able to trace items back to their original source – would ‘drive my work to the edge of madness’ (Nelson 2010c, 104). It would later become the kernel of Nelson’s most innovative idea: transclusion.10 Transclusion, and also the ability to visually compare prior or alternative versions of the same document on screen (‘intercomparison’) were integral to the design of Xanadu. Over the next 40 years, Nelson would hone these ideas and experiment with them in various incarnations. In 1960 Nelson announced his term project: a writing system for the IBM 7090, the only computer at Harvard at the time, stored in a big, airconditioned room at the Smithsonian Observatory.

…

It did, however, include facilities to compare versions of a document and reuse elements from these versions. Both of these ideas would make their way into Xanadu in some form, but the zippered list in particular would eventuate in a ‘deliverable’ 30 years later ZigZag. The zippered list essentially became ZigZag, and the transclusion relationship which comes up as an equals sign [in the diagram in that paper] is essentially the xanological transclusion. (Nelson 2010c) THE MAGICAL PLACE OF LITERARY MEMORY: XANADU 73 Vassar College Lecture Invitation, 1965. This was the first time Nelson’s word hypertext (or ‘hypertexts’) appeared in public. Thanks to Ted Nelson for permission to republish.

Pro AngularJS
by Adam Freeman
Published 25 Mar 2014

I’ll add new HTML files to demonstrate features in each section of this chapter. 447 Chapter 17 ■ Advanced Directive Features Using Transclusion The term transclusion means to insert one part of a document into another by reference. In the context of directives, it is useful when you are creating a directive that is a wrapper around arbitrary content. To demonstrate how this works, I have added a new HMTML file called transclude.html to the angularjs folder and used it to define the example application shown in Listing 17-1. Listing 17-1. The Contents of the transclude.html File <!DOCTYPE html> <html ng-app="exampleApp"> <head> <title>Transclusion</title> <script src="angular.js"></script> <link href="bootstrap.css" rel="stylesheet" /> <link href="bootstrap-theme.css" rel="stylesheet" /> <script type="text/ng-template" id="template"> <div class="panel panel-default"> <div class="panel-heading"> <h4>This is the panel</h4> </div> <div class="panel-body" ng-transclude> </div> </div> </script> <script type="text/javascript"> angular.module("exampleApp", []) .directive("panel", function () { return { link: function (scope, element, attrs) { scope.dataSource = "directive"; }, restrict: "E", scope: true, template: function () { return angular.element( document.querySelector("#template")).html(); }, transclude: true } }) .controller("defaultCtrl", function ($scope) { $scope.dataSource = "controller"; }); </script> </head> <body ng-controller="defaultCtrl"> <panel> The data value comes from the: {{dataSource}} </panel> </body> </html> 448 Chapter 17 ■ Advanced Directive Features My goal in this example is to create a directive that can be applied to arbitrary content in order to wrap it in a set of elements that are styled as a Bootstrap panel.

…

I have called my directive panel and used the restrict definition property to specify that it can be applied only as an element (this isn’t a requirement for using transclusion but rather a convention I use when I write directives that wrap other content). I want to take content like this: ... <panel> The data value comes from the: {{dataSource}} </panel> ... and generate markup like this: ... <div class="panel panel-default"> <div class="panel-heading"> <h4>This is the panel</h4> </div> <div class="panel-body"> The data value comes from the: controller </div> </div> ... The term transclusion is used because the content that is inside the panel element will be inserted into the template. Two specific steps are required to apply transclusion. The first is to set the transclude definition property to true when creating the directive, like this: ... transclude: true ...

…

item.complete"> <td>{{$index + 1}}</td> <td>{{item.action}}</td> <td>{{item.complete}}</td> </tr> ... 269 Chapter 11 ■ Using Element and Event Directives Both the ng-repeat and ng-if directives rely on a technique called transclusion, which I describe in Chapter 17 but which essentially means that both directives want to modify the child elements and AngularJS doesn’t know how to allow both to do so. If you try to apply both of these directives to an element, you will see an error similar to this one in the JavaScript console: Error: [$compile:multidir] Multiple directives [ngRepeat, ngIf] asking for transclusion on: <!-- ngRepeat: item in todos --> This is a rare example where you can’t wire up multiple AngularJS features to solve a problem.

AngularJS
by Brad Green and Shyam Seshadri
Published 15 Mar 2013

You’d run a script to concatenate all the templates into a single file, and load it in a new module that you then reference from your main application module. Transclusion In addition to replacing or appending the content, you can also move the original content within the new template through the transclude property. When set to true, the directive will delete the original content, but make it available for reinsertion within your template through a directive called ng-transclude. We could change our example to use transclusion: appModule.directive('hello', function() { return { template: '<div>Hi there <span ng-transclude></span></div>', transclude: true }; }); applying it as: <div hello>Bob</div> We would see: “Hi there Bob.”

…

So, if my-widget needs to modify something in common to all copies (instances) of my-widget, the right place to do this, for efficiency’s sake, is in a compile function. You will also notice that the compile function receives a transclude function as a property. Here, you have an opportunity to write a function that programmatically transcludes content for situations where the simple template-based transclusion won’t suffice. Lastly, compile can return both a preLink and a postLink function, whereas link specifies only a postLink function. preLink, as its name implies, runs after the compile phase, but before directives on the child elements are linked. Similarly, postLink runs after all the child element directives are linked.

…

working example of, The Templates ng-bind, Displaying Text ng-class, CSS Classes and Styles, The Templates ng-click, Form Inputs, A Few Words on Unobtrusive JavaScript ng-controller DOM node association with, Separating UI Responsibilities with Controllers function of, Directives, The Templates ng-dblclick, Form Inputs ng-directive-name syntax, Directives and HTML Validation ng-disabled, Validating User Input, The Templates ng-eventhandler, A Few Words on Unobtrusive JavaScript ng-hide, Hiding and Showing, The Templates ng-href, Considerations for src and href Attributes, The Templates ng-model bi-directional data binding, Publishing Model Data with Scopes binding elements with, Form Inputs function of, Directives in jQuery wrap, ng-model in shopping cart example, An Example: Shopping Cart ng-repeat for lists, Lists, Tables, and Other Repeated Elements, The Repeater function of, An Example: Shopping Cart priority property and, Priorities working example of, The Templates, The Templates, The Templates ng-show, Hiding and Showing, The Templates ng-src, Considerations for src and href Attributes ng-style, CSS Classes and Styles ng-submit, Form Inputs, The Templates, The Templates ng-transclude, Transclusion ng-view, The Templates ngPluralize, Internationalization and Localization ngResource, Unit Test the ngResource number filter, Formatting Data with Filters number localization, Internationalization and Localization O object properties, Observing Model Changes with $watch, Watching multiple things, Working with RESTful Resources Object.observe(), Performance Considerations in watch() onclick, Form Inputs ondblclick, Form Inputs optimization, Compilation optional fields, Validating User Input order-independent arguments, Organizing Dependencies with Modules Origin null…, Templates P pagination service, A Simple Pagination Service–A Simple Pagination Service parameter name matching, Organizing Dependencies with Modules parameterization, The Declaration parent scopes, Scopes parsing complexity, Organizing Dependencies with Modules password requirement, enforcing, The Templates person objects, Working with RESTful Resources PHP, Data Binding plain text cookies, Cookies pluralization support, Internationalization and Localization POST requests, Communicating Over $http, JSON Vulnerability price, sum total, Observing Model Changes with $watch principle of least knowledge, Dependency Injection priority property, API Overview, Priorities production-ready apps, Building Your Project project organization, Project Organization, Integrating AngularJS with RequireJS Promise interface, Communicating Over $http Promise proposal, The $q and the Promise promises, Services propagation, ascertaining full, Performance Considerations in watch() prototypal inheritance, Model View Controller Provider API call, Convenience Methods R radio buttons, Form Inputs Rails, Data Binding, Declaring Angular’s Boundaries with ng-app realtime web apps, Using Socket.IO recipe management applications, The Application Regex patterns, The Templates relative links, HTML5 Mode and Hashbang Mode replace property, API Overview request transformations, Transformations on Requests and Responses requests, configuring, Configuring Your Request Further require property, API Overview, Controllers Requirejs, Integrating AngularJS with RequireJS–Integrating AngularJS with RequireJS reset buttons, Form Inputs response interception, Response Interception response transformations, Transformations on Requests and Responses RESTful resources, Services, Working with RESTful Resources–Unit Test the ngResource RESTful servers, Services restrict property, API Overview, restrict rounding up/down, Formatting Data with Filters routes adding with Yeoman, Adding New Routes, Views, and Controllers alternatives to, $location changing views with, Changing Views with Routes and $location–controllers.js list template and, The Templates rows, highlighting, CSS Classes and Styles Run block, Loading and Dependencies S same origin policy, Templates sample application structure, Project Organization sanitize module, Sanitizing HTML & the Sanitize Module Save buttons, The Templates Scenario Runner, End-to-End/Integration Tests scenario tests, Scenario Tests scope property, API Overview Scope.

The Transhumanist Reader
by Max More and Natasha Vita-More
Published 4 Mar 2013

Conclusion Part VI Enhanced Decision-Making 25 Idea Futures Introduction Concept Scenario Scope Procedures Advantages Criticisms Related Work An Appeal Conclusion 26 The Proactionary Principle The Origin of the Proactionary Principle The Wisdom of Structure The Failure of the Precautionary Principle The Proactionary Principle Preamble to the Proactionary Principle Be Objective and Comprehensive Prioritize Natural and Human Risks Embrace Diverse Input Make Response and Restitution Proportionate Revisit and Revise 27 The Open Society and Its Media Improving Society Media Matter Xanadu Links Hyperlinks Emergent Properties Transclusion Remembering the Past: Historical Trails Preparing for the Future: Detectors The WidgetPerfect Saga Permissions Reputation-Based Filtering Hypertext + Multimedia = Hypermedia External Transclusion Conclusions Part VII Biopolitics and Policy 28 Performance Enhancement and Legal Theory 29 Justifying Human Enhancement Rationalizing Medical Interventions on a Slippery Slope Life as a Commodity The Accumulation of Biocultural Capital Counterpoint: Reducing Human Diversity?

…

We planned on and anticipate other features, some of which will be mentioned in the future plans discussion, but the body of this presentation will only cover what is implemented and running. First, I will discuss the four fundamental features – links, transclusion, versioning, and ­detectors. Marc Stiegler will then present an example using them. Then I will describe the remaining four features – permissions, reputation-based filtering, multimedia, and external transclusion, followed by some concluding remarks. Links Hypertext links are directly inspired by literary practice. Literature has many different kinds of links connecting documents into a vast web.

…

It all applies equally well to a variety of other media (such as sound, engineering drawings, Postscript images, and ­compressed video). In all cases, one can make fine-grained links, edits, transclusions, and version compares (even if the data is block-compressed or block-encrypted). Although the implementation has some optimizations targeted at text, in no way does the architecture make any special cases for text. Documents can, of course, be composite arrangements in which several media are mixed together. External Transclusion No software system is an island. We do not imagine that once the product is available, everyone will instantly take all information to which they want access and transfer it into Xanadu.

Intertwingled: Information Changes Everything
by Peter Morville
Published 14 May 2014

This simple, modular approach helped the Web to spread like wildfire, yet it also ruled out core features of earlier visions. Ted Nelson imagined a vertically integrated system that managed everything from code and interface to copyright and micropayment. Xanadu’s transpointing windows would support bidirectional links, transclusion, and side-by-side comparison. It would elevate the work of scholars and advance Doug Englebart’s dream to augment human intellect, so we might understand and resolve the world’s seemingly insoluble problems. In the eulogy, Ted Nelson makes clear the heights of their ambition and their depth of disappointment.

…

The service evidence of folded toilet paper is but a sign of things to come. As discrete products shift into service ecosystems, our information shadows grow, and so do complexity and confusion. We will need the limits of paths, the myths of maps, and the serendipity of ourselves to make sense. We will also need a remembrance of things past, from transclusion to transpointing windows, since meaning is lost in translation, and memory isn’t nearly as reliable as seeing connections side by side. In the futures of user experience and service design, the architecture of cross-channel links is critical. The boxes still matter, but it’s the arrows that amplify their consequence.

The Future of the Internet: And How to Stop It
by Jonathan Zittrain
Published 27 May 2009

An example is Miguel Mora’s Identity Protection System, which would allow a sticker or badge to function as a signal for surveillance cameras to block an individual from their recording. See Miguel.Mora.Design, http://www.miquelmora.com/idps.html (last visited July 28, 2007). 124. TED NELSON, LITERARY MACHINES (1981); Wikipedia, Transclusion, http://en.wikipedia.org/wiki/Transclusion (as of June 1, 2007, 10:30 GMT). 125. Consider, for example, the Internet Archive. Proprietor Brewster Kahle has thus far avoided what one would think to be an inevitable copyright lawsuit as he archives and makes available historical snapshots of the Web. He has avoided such lawsuits by respecting Web owners’ wishes to be excluded as soon as he is notified.

…

Yet a Google search intentionally smoothes over this complexity; each linked search result is placed into a standard format to give the act of searching structure and order. Search engines and other aggregators can and should do more to enrich users’ understanding of where the information they see is coming from. This approach would shadow the way that Theodor Nelson, coiner of the word “hypertext,” envisioned “transclusion”—a means not to simply copy text, but also to reference it to its original source.124 Nelson’s vision was drastic in its simplicity: information would repose primarily at its source, and any quotes to it would simply frame that source. If it were deleted from the original source, it would disappear from its subsequent uses.

…

See also AT&T Texas Instruments TI-99/4A, 13 theories of the commons, 78–79 Ticketmaster.com, 207 Timex/Sinclair Z-1000, 13 TiVo, 59, 64, 71, 77, 101, 123, 162, 184; and preemption, 108; and regulator control, 107; and surveillance, 109 TiVo v. EchoStar, 103–4, 107, 108 tolerated uses, 119–22, 190–91 traffic lights: cameras at, 116–17; and verkeersbordvrij, 127–28 tragedies of the commons, 158 transclusion, use of term, 226–27 transferability, 73 transmission speed, irregularity of, 32 trial and error, learning by, 236 Trumpet Winsock, 29 trust: assumptions of, 20–21, 30–32, 39–40, 134, 135, 147; trade-offs with, 33 trusted systems, 105 Tushman, Michael, 24 Twain, Mark (Samuel Clemens), 212, 213 two-factor authentication, 53 typewriters, “smart,” 15, 19, 20, 34 unitary rights holder, 189 United States v.

The Inevitable: Understanding the 12 Technological Forces That Will Shape Our Future
by Kevin Kelly
Published 6 Jun 2016

He was certain that every document in the world should be a footnote to some other document, and computers could make the links between them visible and permanent. This was a new idea at the time. But that was just the beginning. Scribbling on index cards, he sketched out complicated notions of transferring authorship back to creators and tracking payments as readers hopped along networks of documents, in what he called the “docuverse.” He spoke of “transclusion” and “intertwingularity” as he described the grand utopian benefits of his embedded structure. It was going to save the world from stupidity! I believed him. Despite his quirks, it was clear to me that a hyperlinked world was inevitable—someday. But as I look back now, after 30 years of living online, what surprises me about the genesis of the web is how much was missing from Vannevar Bush’s vision, and even Nelson’s docuverse, and especially my own expectations.

…

At that time, anyone silly enough to trumpet the above list as a vision of the near future would have been confronted by the evidence: There wasn’t enough money in all the investment firms in the entire world to fund such bounty. The success of the web at this scale was impossible. But if we have learned anything in the past three decades, it is that the impossible is more plausible than it appears. Nowhere in Ted Nelson’s convoluted sketches of hypertext transclusion did the fantasy of a virtual flea market appear. Nelson hoped to franchise his Xanadu hypertext systems in the physical world at the scale of mom-and-pop cafés—you would go to a Xanadu store to do your hypertexting. Instead, the web erupted into open global flea markets like eBay, Craigslist, or Alibaba that handle several billion transactions every year and operate right into your bedroom.

…

Bush outlined the web’s core idea: Vannevar Bush, “As We May Think,” Atlantic, July 1945. Nelson, who envisioned his own scheme: Theodor H. Nelson, “Complex Information Processing: A File Structure for the Complex, the Changing and the Indeterminate,” in ACM ’65: Proceedings of the 1965 20th National Conference (New York: ACM, 1965), 84–100. “transclusion”: Theodor H. Nelson, Literary Machines (South Bend, IN: Mindful Press, 1980). “intertwingularity”: Theodor H. Nelson, Computer Lib: You Can and Must Understand Computers Now (South Bend, IN: Nelson, 1974). total number of web pages: “How Search Works,” Inside Search, Google, 2013, accessed April 26, 2015. 90 billion searches a month: Steven Levy, “How Google Search Dealt with Mobile,” Medium, Backchannel, January 15, 2015. 50 million blogs in the early 2000s: David Sifry, “State of the Blogosphere, August 2006,” Sifry’s Alerts, August 7, 2006. 65,000 per day are posted: “YouTube Serves Up 100 Million Videos a Day Online,” Reuters, July 16, 2006. 300 video hours every minute, in 2015: “Statistics,” YouTube, April 2015, https://goo.gl/RVb7oz.

This Is for Everyone: The Captivating Memoir From the Inventor of the World Wide Web
by Tim Berners-Lee
Published 8 Sep 2025

The Writer could write whatever they wanted to, without constraint. The Reader could read whatever they wanted to, or not read anything. Literature is a battle between these two. Ted’s proposed Xanadu technology would create a new relationship between the Reader and the Writer. It included a property he called ‘transclusion’: every time you quoted one document in another document, there should be a bidirectional link between the original and the quotation, allowing you to switch between the two. Xanadu also included ‘micropayments’ (a term Ted coined) to support artists and creators. Click on a link in Xanadu, and the person (or persons) who’d designed the page you visited would receive a small amount of money you could explicitly pay.

…

R. ref1 MasterCard ref1 Mastodon ref1, ref2 mathematics ref1, ref2, ref3, ref4 Matrix ref1 media industry ref1 mental health and social media ref1, ref2, ref3 ‘Mesh’ memo ref1 Meta ref1, ref2, ref3 see also Facebook metadata ref1 metasystems ref1 Metaverse ref1 Metcalf, Bob ref1 MeWe ref1 micropayments ref1 microprocessors ref1, ref2 Microsoft ActiveX ref1 Clippy ref1 Copilot ref1 copyright infringement ref1 early lack of browser ref1 Internet Explorer ref1, ref2, ref3, ref4, ref5 MS-DOS ref1 Office ref1 standards ref1, ref2 Teams ref1 XML ref1 Microsoft Exchange Server ref1 microtargeting ref1, ref2 Middle Earth ref1 Middle Earth map ref1 military applications ref1 Millennium Technology Prize ref1 Miller, Kaia ref1 Minnesota, University of ref1, ref2 misinformation ref1, ref2 MIT Center for Constructive Communication ref1 Computer Science and Artificial Intelligence Lab (CSAIL) ref1, ref2 speaking tours ref1 Tim Berners-Lee’s arrival ref1 Tim Berners-Lee’s early visits ref1, ref2 World Wide Web Consortium (W3C) ref1, ref2, ref3 mobile phones CSS (cascading style sheets) ref1 licences legislation ref1 touchscreens ref1 see also smartphones model railway ref1 modems broadband ref1 dial-up ref1, ref2 download speeds ref1, ref2 Moffat, John ref1, ref2, ref3 monopolization ref1, ref2, ref3, ref4, ref5, ref6 Montulli, Lou ref1 moon landings ref1 Moore’s Law ref1 Morsi, Mohammed ref1 Mosaic browser ref1, ref2, ref3, ref4 ‘The Mother of all Demos’ (Engelbart) ref1 motivation-hygiene theory ref1 Motorola ref1 Mount Stromlo Observatory ref1 Mozilla foundation ref1, ref2, ref3 MP3s ref1 Mubarak, Hosni ref1 multimedia ref1, ref2 Murthy, Vivek ref1 music collaboration ref1 copyright ref1 illuminated Italian Renaissance website ref1 MP3s ref1 recommendation services ref1, ref2 Tim Berners-Lee’s interest ref1 Musk, Elon ref1, ref2 MyData ref1 MySpace ref1 Myst (game) ref1 narrowcasting ref1, ref2, ref3 National Science Foundation ref1 National Theatre, London ref1 Naver Maps ref1 NCSA (National Center for Supercomputing Applications) ref1, ref2, ref3, ref4, ref5, ref6 Nelson, Ted ref1, ref2 neoliberalism ref1 net neutrality ref1, ref2, ref3 Netflix ref1, ref2 netiquette ref1 Netscape ref1, ref2, ref3, ref4, ref5, ref6 networking fractal ref1 humans as social animals ref1 neural networks ref1, ref2, ref3, ref4 URLs ref1 New York Times, The ref1, ref2, ref3 Newmark, Craig ref1 news organizations ref1 newsgroups ref1, ref2 NeXT ref1, ref2, ref3, ref4, ref5, ref6, ref7, ref8 NFT of original WWW code ref1 Ng, Andrew ref1 NHS ref1, ref2 Nigeria ref1 Nilekani, Nandan ref1 9/11 attacks ref1, ref2 Nix, Alexander ref1 Nobel Prize ref1, ref2, ref3, ref4 Nokia ref1 nuclear weapons ref1 Nupedia ref1 Nvidia ref1, ref2 Objective-C code ref1 Olympics, 2012 London ref1, ref2 Ong, Jonathan Corpus ref1 Open Data Institute (ODI) ref1, ref2, ref3, ref4 see also Solid open-source software ref1, ref2, ref3, ref4, ref5, ref6 Open Systems Interconnection (OSI) ref1 OpenAI ref1, ref2, ref3, ref4, ref5 OpenStreetMap ref1, ref2 Opera browser ref1, ref2, ref3, ref4 Opzoomer, Indi (Leith) ref1 Opzoomer, Jamie (Leith) ref1 Opzoomer, Lyssie (Leith) ref1 Order of Merit of the British Empire ref1, ref2 O’Reilly ref1, ref2, ref3 Oxford University ref1, ref2, ref3, ref4 PACER ref1 packet-switching ref1 Page, Larry ref1, ref2 PageRank ref1 pantomime ref1 ‘paperclip maximizer’ ref1 paradigm shift, artificial intelligence (AI) ref1 passkeys ref1 passwords ref1 patents ref1 peace ref1 Pellow, Nicola ref1 Penrose, Roger ref1 Pentagon ref1, ref2, ref3 Pets.com ref1 philanthropy ref1 Philippines ref1 photographs, metadata ref1 physics ref1, ref2 pi.ai ref1 Pinterest ref1, ref2 Pioch, Nicolas ref1 plagiary ref1 Plessey ref1, ref2, ref3 Plewe, Brandon ref1 PNG (Portable Network Graphics) ref1 podcasts ref1 PODS (Personal Online Data Stores) ref1, ref2, ref3, ref4, ref5, ref6 polarization ref1, ref2, ref3, ref4, ref5, ref6 Polis ref1 Pollerman, Bernd ref1 Polly, Jean Armour ref1 Poole ref1 Pordes, Ruth ref1 Postel, Jon ref1 Postscript language ref1 Priceline ref1 printers, dot-matrix ref1 printing presses ref1, ref2 privacy apps ref1 Contract for the Web ref1, ref2 data sovereignty ref1, ref2, ref3, ref4, ref5, ref6, ref7, ref8 location data ref1 MyData ref1 principle ref1, ref2 regulations ref1 RSA system ref1 Solid ref1, ref2 Prodigy ref1 programming languages ECMAScript ref1 HTML5 ref1 Java ref1 Objective-C ref1 Python ref1, ref2 Timpl ref1 Unix ref1 see also HTML Project Liberty ref1 protein-folding ref1, ref2 protocols CERN ref1 internet ref1, ref2 open ref1 see also HTTP; Solid provenance ref1 Prud’hommeaux, Eric ref1 public-key encryption ref1, ref2, ref3 punting ref1 Purnell, ‘Daffy’ ref1 Putz, Steve ref1 Python ref1, ref2, ref3, ref4, ref5 quantum mechanics 151n queuing theory ref1, ref2 Quicken ref1 Quint, Vincent ref1 Raggett, Dave ref1, ref2 RAGs (Retrieval-Augmented Generation systems) ref1 railway, model ref1 The Ranch ref1 Raytheon ref1 RDF (Resource Description Format) ref1, ref2 read–write web ref1 Readers ref1, ref2 RECAP ref1 Reddit ref1, ref2, ref3 religion ref1, ref2, ref3 retail sites ref1, ref2 Richmond Park ref1 Rimmer, Peggie ref1, ref2, ref3, ref4, ref5, ref6 Rivest, Ron ref1, ref2 Rogers, Kevin ref1, ref2 Rouse, Paul ref1, ref2 Royal Society ref1 RSA system ref1, ref2, ref3, ref4 RSS (Really Simple Syndication) ref1, ref2 running ref1, ref2 Rwanda ref1 Safari ref1, ref2 Sahel ref1 sailing ref1, ref2 Sainsbury’s ref1 Sandberg, Sheryl ref1 Sanger, Larry ref1 Sawadogo, Yacouba ref1 Scheifler, Bob 118n Schneier, Bruce ref1 schools ref1, ref2, ref3 science fiction ref1, ref2, ref3 Science Museum, London ref1 search engines ref1, ref2, ref3, ref4, ref5 see also Google Searls, Doc ref1 Second Life ref1 secure systems ref1 Segal, Ben ref1, ref2 semantic web Applied Semantics ref1 initial concept ref1 ‘layer cake’ ref1 machine learning ref1 PODS (Personal Online Data Stores) ref1 RDF (Resource Description Format) ref1 semantic winter ref1 Semantic Web Institute ref1 Sendall, Mike ref1, ref2, ref3, ref4, ref5, ref6 Seoul Peace Prize ref1, ref2 server software ref1, ref2 Sesri, Rudina ref1, ref2, ref3, ref4 SGML (Standard Generalized Markup Language) ref1, ref2 Shadbolt, Nigel ref1, ref2 Shamir, Adi ref1 Sheen Mount school ref1 Silicon Valley ref1, ref2 silos ref1, ref2, ref3, ref4 simplified text ref1 singularity ref1 Siri ref1, ref2 skiing ref1, ref2, ref3 Slack ref1 Slashdot ref1 slashdotting ref1 Smarr, Larry ref1 smartphones apps ref1, ref2 children ref1 global growth ref1, ref2 interoperability ref1 Smith, Adam ref1, ref2 Social Dilemma, The (film, 2020) ref1 social media addiction ref1, ref2, ref3, ref4 advertisements ref1, ref2, ref3 algorithms ref1, ref2, ref3, ref4, ref5, ref6 Arab Spring ref1 attention economy ref1, ref2 collaborative filtering and polarization ref1 early development ref1 Institute for Rebooting Social Media ref1 liability of hosts ref1 mental health ref1 mental health issues ref1, ref2 MeWe ref1 silos ref1 social graph ownership ref1 users as the product ref1, ref2 social trust ref1 software copyright development ref1 open-source ref1, ref2, ref3, ref4, ref5, ref6 Solid (Social Linked Data protocol) adoption ref1, ref2, ref3, ref4, ref5 Charlie ref1, ref2 development ref1, ref2 functionality ref1, ref2, ref3 Inrupt ref1 organization and structure ref1 potential ref1 Seoul Peace Prize ref1 server protocol ref1 trust ref1 see also PODS; data wallets Sollins, Karen ref1 Sony ref1 South Korea ref1, ref2 spiders ref1 Spotify ref1, ref2, ref3 Spyglass ref1 standards ref1, ref2, ref3, ref4, ref5 see also protocols; World Wide Web Consortium Stanford Linear Accelerator Center (SLAC) ref1, ref2, ref3 stock brokers ref1, ref2 Stoppard, Tom ref1 Stover, Mr (music teacher) ref1 style sheets ref1, ref2, ref3 Suleyman, Mustafa ref1, ref2, ref3 Sun Microsystems ref1 Sunak, Rishi ref1 superintelligence ref1 surveillance ref1, ref2, ref3, ref4, ref5, ref6 Swick, Ralph ref1 Switzerland ref1, ref2, ref3 T-Mobile ref1 tabulator ref1 tags ref1 Tahrir Square ref1 Taiwan ref1 TCP/IP ref1, ref2 TED talks ref1, ref2, ref3 teleconferencing ref1, ref2, ref3 teletypes ref1 television cathode-ray tubes ref1 closed captioning ref1 Telnet ref1 Tencent ref1 Texas Instruments ref1 text-to-speech services ref1 third-party distribution networks ref1, ref2 This Is For Everyone ref1, ref2 TikTok ref1, ref2 timbl ref1 Time magazine ref1 Timpl ref1 Tolkein, J. R. R. ref1 touchscreens ref1 toxicity of the web ref1, ref2, ref3, ref4 TPAC (Technical Plenary Advisory Committee) conferences ref1 trains ref1 Transactions on Computer Systems (journal) ref1 transatlantic cables ref1 transclusion ref1 transformers ref1 transistors ref1 travel agencies ref1, ref2 tree structures ref1, ref2, ref3, ref4 trust ref1, ref2, ref3 TTL chips ref1 Tunisia ref1, ref2 Turdean, Timea ref1 Turing, Alan ref1, ref2, ref3 Turing Prize ref1, ref2 Turing Test ref1, ref2 23andMe ref1 Twitter ref1, ref2, ref3 2001: A Space Odyssey (film, 1968) ref1 U2 ref1 Uber ref1, ref2 Uganda ref1 UK Brexit ref1 Data Use and Access Bill ref1 trust ref1 Unitarian Universalists ref1 United Nations (UN) ref1, ref2 universal access ref1, ref2, ref3, ref4, ref5, ref6, ref7 universality ref1, ref2 Unix ref1, ref2, 118n, ref1 Unix X Windows ref1 urban design ref1 URLs (Uniform Resource Locators) ref1, ref2, ref3 USA 2016 election ref1 data regulation ref1 open data legislation ref1 PACER ref1 Telecommunications Act 1996 ref1 trust ref1 Usenet ref1, ref2, ref3, ref4 van der Hiel, Amy ref1 van Rossum, Guido ref1, ref2 Vatican ref1, ref2 Verisign ref1 Vezza, Al ref1, ref2, ref3 videoconferencing ref1, ref2, ref3, ref4 videos ref1 ViolaWWW ref1, ref2 viral content ref1 Virtual Library ref1 virtual reality ref1 Visual Display Units ref1 VRML (Virtual Reality Markup Language) ref1 W3C see World Wide Web Consortium Wales ref1 Wales, Jimmy ref1 wallets ref1 see also data wallets; PODS Wanamaker, John ref1 Wayback Machine ref1 Wayve ref1 wearables ref1 web see World Wide Web ‘web 2.0’ ref1 web applications ref1 web clients ref1, ref2 Web Foundation Africa ref1, ref2 closure ref1 Contract for the Web ref1, ref2, ref3 foundation ref1 fundraising ref1 mission ref1, ref2, ref3, ref4 strategy ref1 structures ref1 web anniversary ref1 Web Index ref1 Web Index ref1 Web Science Trust ref1 Web Summit conference, Lisbon ref1, ref2 Web3 ref1 webrings ref1 WebRTC (Web Real-Time Communication) ref1 webs ref1, ref2, ref3 websites early development ref1 first ref1 Wei, Pei-Yuan ref1, ref2 Weigant, Dietrich ref1 Weinstein, Mark ref1 Weitzner, Danny ref1, ref2, ref3 Wells, Pete ref1, ref2 Wequassett Resort, Cape Cod ref1 WHATWG (Web Hypertext Application Technology Working Group) ref1 White, E.