Search: in
World Wide Web
World Wide Web in Encyclopedia Encyclopedia
  Tutorials     Encyclopedia     Videos     Books     Software     DVDs  

World Wide Web

The World Wide Web (abbreviated as WWW or W3,[1] commonly known as the Web, or the "Information Superhighway"), is a system of interlinked hypertext documents accessed via the Internet. With a web browser, one can view web pages that may contain text, images, videos, and other multimedia, and navigate between them via hyperlinks.

Using concepts from his earlier hypertext systems like ENQUIRE, British engineer and computer scientist Sir Tim Berners-Lee, now Director of the World Wide Web Consortium (W3C), wrote a proposal in March 1989 for what would eventually become the World Wide Web.[2] At CERN, a European research organization near Geneva situated on Swiss and French soil,[3] Berners-Lee and Belgian computer scientist Robert Cailliau proposed in 1990 to use hypertext "... to link and access information of various kinds as a web of nodes in which the user can browse at will",[4] and they publicly introduced the project in December.[5]



The NeXT Computer used by Berners-Lee. The handwritten label declares, "This machine is a server. DO NOT POWER IT DOWN!!" In the May 1970 issue of Popular Science magazine Arthur C. Clarke was reported to have predicted that satellites would one day "bring the accumulated knowledge of the world to your fingertips" using a console that would combine the functionality of the Xerox, telephone, television and a small computer, allowing data transfer and video conferencing around the globe.[6] Clarke also determined that geosyncronous orbit would be possible at the altitude of 22,000 miles, which is why that region is called the Clarke Belt.

In March 1989, Tim Berners-Lee wrote a proposal that referenced ENQUIRE, a database and software project he had built in 1980, and described a more elaborate information management system.[7]

With help from Robert Cailliau, he published a more formal proposal (on November 12, 1990) to build a "Hypertext project" called "WorldWideWeb" (one word, also "W3") as a "web" of "hypertext documents" to be viewed by "browsers" using a client server architecture.[4] This proposal estimated that a read-only web would be developed within three months and that it would take six months to achieve "the creation of new links and new material by readers, [so that] authorship becomes universal" as well as "the automatic notification of a reader when new material of interest to him/her has become available." While the read-only goal was met, accessible authorship of web content took longer to mature, with the wiki concept, blogs, Web 2.0 and RSS/Atom.[8]

The proposal was modeled after the Dynatext SGML reader by Electronic Book Technology, a spin-off from the Institute for Research in Information and Scholarship at Brown University. The Dynatext system, licensed by CERN, was technically advanced and was a key player in the extension of SGML ISO 8879:1986 to Hypermedia within HyTime, but it was considered too expensive and had an inappropriate licensing policy for use in the general high energy physics community, namely a fee for each document and each document alteration.

The CERN datacenter in 2010 housing some WWW servers

A NeXT Computer was used by Berners-Lee as the world's first web server and also to write the first web browser, WorldWideWeb, in 1990. By Christmas 1990, Berners-Lee had built all the tools necessary for a working Web:[9] the first web browser (which was a web editor as well); the first web server; and the first web pages,[10] which described the project itself. On August 6, 1991, he posted a short summary of the World Wide Web project on the alt.hypertext newsgroup.[11] This date also marked the debut of the Web as a publicly available service on the Internet. The first photo on the web was uploaded by Berners-Lee in 1992, an image of the CERN house band Les Horribles Cernettes.

The first server outside Europe was set up at SLAC to host the SPIRES-HEP database. Accounts differ substantially as to the date of this event. The World Wide Web Consortium says December 1992,[12] whereas SLAC itself claims 1991.[13][14] This is supported by a W3C document entitled A Little History of the World Wide Web.[15]

The crucial underlying concept of hypertext originated with older projects from the 1960s, such as the Hypertext Editing System (HES) at Brown University, Ted Nelson's Project Xanadu, and Douglas Engelbart's oN-Line System (NLS). Both Nelson and Engelbart were in turn inspired by Vannevar Bush's microfilm-based "memex", which was described in the 1945 essay "As We May Think".


Berners-Lee's breakthrough was to marry hypertext to the Internet. In his book Weaving The Web, he explains that he had repeatedly suggested that a marriage between the two technologies was possible to members of both technical communities, but when no one took up his invitation, he finally tackled the project himself. In the process, he developed three essential technologies:

  1. a system of globally unique identifiers for resources on the Web and elsewhere, the Universal Document Identifier (UDI), later known as Uniform Resource Locator (URL) and Uniform Resource Identifier (URI);
  2. the publishing language HyperText Markup Language (HTML);
  3. the Hypertext Transfer Protocol (HTTP).[17]

The World Wide Web had a number of differences from other hypertext systems that were then available. The Web required only unidirectional links rather than bidirectional ones. This made it possible for someone to link to another resource without action by the owner of that resource. It also significantly reduced the difficulty of implementing web servers and browsers (in comparison to earlier systems), but in turn presented the chronic problem of link rot. Unlike predecessors such as HyperCard, the World Wide Web was non-proprietary, making it possible to develop servers and clients independently and to add extensions without licensing restrictions. On April 30, 1993, CERN announced that the World Wide Web would be free to anyone, with no fees due.[18] Coming two months after the announcement that the server implementation of the Gopher protocol was no longer free to use, this produced a rapid shift away from Gopher and towards the Web. An early popular web browser was ViolaWWW for Unix and the X Windowing System.

Robert Cailliau, Jean-Fran ois Abramatic of IBM, and Tim Berners-Lee at the 10th anniversary of the World Wide Web Consortium.
Robert Cailliau, Jean-Fran ois Abramatic of IBM, and Tim Berners-Lee at the 10th anniversary of the World Wide Web Consortium.
Scholars generally agree that a turning point for the World Wide Web began with the introduction[19] of the Mosaic web browser[20] in 1993, a graphical browser developed by a team at the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign (NCSA-UIUC), led by Marc Andreessen. Funding for Mosaic came from the U.S. High-Performance Computing and Communications Initiative and the High Performance Computing and Communication Act of 1991, one of several computing developments initiated by U.S. Senator Al Gore.[21] Prior to the release of Mosaic, graphics were not commonly mixed with text in web pages and the Web's popularity was less than older protocols in use over the Internet, such as Gopher and Wide Area Information Servers (WAIS). Mosaic's graphical user interface allowed the Web to become, by far, the most popular Internet protocol.

The World Wide Web Consortium (W3C) was founded by Tim Berners-Lee after he left the European Organization for Nuclear Research (CERN) in October 1994. It was founded at the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) with support from the Defense Advanced Research Projects Agency (DARPA), which had pioneered the Internet; a year later, a second site was founded at INRIA (a French national computer research lab) with support from the European Commission DG InfSo; and in 1996, a third continental site was created in Japan at Keio University. By the end of 1994, while the total number of websites was still minute compared to present standards, quite a number of notable websites were already active, many of which are the precursors or inspiration for today's most popular services.

Connected by the existing Internet, other websites were created around the world, adding international standards for domain names and HTML. Since then, Berners-Lee has played an active role in guiding the development of web standards (such as the markup languages in which web pages are composed), and in recent years has advocated his vision of a Semantic Web. The World Wide Web enabled the spread of information over the Internet through an easy-to-use and flexible format. It thus played an important role in popularizing use of the Internet.[22] Although the two terms are sometimes conflated in popular use, World Wide Web is not synonymous with Internet.[23] The Web is a collection of documents and both client and server software using Internet protocols such as TCP/IP and HTTP.


The terms Internet and World Wide Web are often used in everyday speech without much distinction. However, the Internet and the World Wide Web are not one and the same. The Internet is a global system of interconnected computer networks. In contrast, the Web is one of the services that runs on the Internet. It is a collection of text documents and other resources, linked by hyperlinks and URLs, usually accessed by web browsers from web servers. In short, the Web can be thought of as an application "running" on the Internet.[24]

Viewing a web page on the World Wide Web normally begins either by typing the URL of the page into a web browser or by following a hyperlink to that page or resource. The web browser then initiates a series of communication messages, behind the scenes, in order to fetch and display it. As an example, consider accessing a page with the URL .

First, the browser resolves the server-name portion of the URL ( into an Internet Protocol address using the globally distributed database known as the Domain Name System (DNS); this lookup returns an IP address such as The browser then requests the resource by sending an HTTP request across the Internet to the computer at that particular address. It makes the request to a particular application port in the underlying Internet Protocol Suite so that the computer receiving the request can distinguish an HTTP request from other network protocols it may be servicing such as e-mail delivery; the HTTP protocol normally uses port 80. The content of the HTTP request can be as simple as the two lines of text GET /wiki/World_Wide_Web HTTP/1.1 Host:

The computer receiving the HTTP request delivers it to web server software listening for requests on port 80. If the web server can fulfill the request it sends an HTTP response back to the browser indicating success, which can be as simple as /1.0 200 OK Content-Type: text/html; charset=UTF-8 followed by the content of the requested page. The Hypertext Markup Language for a basic web page looks like The World Wide Web

The World Wide Web, abbreviated as WWW and commonly known ...

The web browser parses the HTML, interpreting the markup (</tt>, <tt><p></tt> for paragraph, and such) that surrounds the words in order to draw the text on the screen.</p> <p>Many web pages use HTML to reference the URLs of other resources such as images, other embedded media, <a href="/ed/JavaScript" id="w">scripts</a> that affect page behavior, and <a href="/ed/Cascading_Style_Sheets" id="w">Cascading Style Sheets</a> that affect page layout. The browser will make additional HTTP requests to the web server for these other <a href="/ed/Internet_media_type" id="w">Internet media types</a>. As it receives their content from the web server, the browser progressively <a href="/ed/Layout_engine" id="w">renders</a> the page onto the screen as specified by its HTML and these additional resources.</p> <a id="Linking" name="Linking"></a> <h3>Linking</h3> <p>Most web pages contain <a href="/ed/Hyperlinks" id="w">hyperlinks</a> to other related pages and perhaps to downloadable files, source documents, definitions and other web resources. In the underlying HTML, a hyperlink looks like <a href="<i></i>"><i>, a free encyclopedia</i></a> <a href="/ed/File:WorldWideWebAroundWikipedia.png%7Cthumb" id="w">Graphic representation of a minute fraction of the WWW, demonstrating</a> <a href="/ed/Hyperlink" id="w">hyperlink</a>s Such a collection of useful, related resources, interconnected via hypertext links is dubbed a <i>web</i> of information. Publication on the Internet created what <a href="/ed/Tim_Berners-Lee" id="w">Tim Berners-Lee</a> first called the <i>WorldWideWeb</i> (in its original <a href="/ed/CamelCase" id="w">CamelCase</a>, which was subsequently discarded) in November 1990.<sup id="_ref-W90_c" class="reference"><a href="#_note-W90" title="">[4]</a></sup></p> <p>The hyperlink structure of the WWW is described by the <a href="/ed/Webgraph" id="w">webgraph</a>: the nodes of the <a href="/ed/Webgraph" id="w">webgraph</a> correspond to the web pages (or URLs) the directed edges between them to the <a href="/ed/Hyperlink" id="w">hyperlinks</a>.</p> <p>Over time, many web resources pointed to by hyperlinks disappear, relocate, or are replaced with different content. This makes hyperlinks obsolete, a phenomenon referred to in some circles as <a href="/ed/Link_rot" id="w">link rot</a> and the hyperlinks affected by it are often called <a href="/ed/Dead_link" id="w">dead links</a>. The ephemeral nature of the Web has prompted many efforts to archive web sites. The <a href="/ed/Internet_Archive" id="w">Internet Archive</a>, active since 1996, is one of the best-known efforts.</p> <a id="Dynamic_updates_of_web_pages" name="Dynamic_updates_of_web_pages"></a> <h3>Dynamic updates of web pages</h3> <p><a href="/ed/JavaScript" id="w">JavaScript</a> is a <a href="/ed/Scripting_programming_language" id="w">scripting language</a> that was initially developed in 1995 by <a href="/ed/Brendan_Eich" id="w">Brendan Eich</a>, then of <a href="/ed/Netscape" id="w">Netscape</a>, for use within web pages.<sup id="_ref-Hamilton_a" class="reference"><a href="#_note-Hamilton" title="">[25]</a></sup> The standardized version is <a href="/ed/ECMAScript" id="w">ECMAScript</a>.<sup id="_ref-Hamilton_b" class="reference"><a href="#_note-Hamilton" title="">[25]</a></sup> To overcome some of the limitations of the page-by-page model described above, some web applications also use <a href="/ed/Ajax_(programming)" id="w">Ajax</a> (<a href="/ed/Asynchronous_I/O" id="w">asynchronous</a> JavaScript and <a href="/ed/XML" id="w">XML</a>). JavaScript is delivered with the page that can make additional HTTP requests to the server, either in response to user actions such as mouse-clicks or based on lapsed time. The server's responses are used to modify the current page rather than creating a new page with each response. Thus, the server must provide only limited, incremental information. Since multiple Ajax requests can be handled at the same time, users can interact with a page even while data is being retrieved. Some web applications regularly <a href="/ed/Polling_(computer_science)" id="w">poll</a> the server to ask whether new information is available.<sup id="_ref-26" class="reference"><a href="#_note-26" title="">[26]</a></sup></p> <a id="WWW_prefix" name="WWW_prefix"></a> <h3>WWW prefix</h3> <p>Many domain names used for the World Wide Web begin with <i>www</i> because of the long-standing practice of naming Internet hosts (servers) according to the services they provide. The <a href="/ed/Hostname" id="w">hostname</a> for a <a href="/ed/Web_server" id="w">web server</a> is often <i>www</i>, in the same way that it may be <i>ftp'' for an <a href="/ed/FTP_server" id="w">FTP server</a>, and</i> news <i>or</i> nntp <i>for a <a href="/ed/USENET" id="w">USENET</a> <a href="/ed/News_server" id="w">news server</a>. These host names appear as <a href="/ed/Domain_Name_System" id="w">Domain Name System</a> or [domain name server](DNS) <a href="/ed/Subdomain" id="w">subdomain</a> names, as in <tt></tt>. The use of 'www' as a subdomain name is not required by any technical or policy standard; indeed, the first ever web server was called <tt></tt>,<sup id="_ref-27" class="reference"><a href="#_note-27" title="">[27]</a></sup> and many web sites exist without it. According to Paolo Palazzi,<sup id="_ref-28" class="reference"><a href="#_note-28" title="">[28]</a></sup> who worked at CERN along with Tim Berners-Lee, the popular use of 'www' subdomain was accidental; the World Wide Web project page was intended to be published at while was intended to be the CERN home page, however the dns records were never switched, and the practice of prepending 'www' to an institution's website domain name was subsequently copied. Many established websites still use 'www', or they invent other subdomain names such as 'www2', 'secure', etc. Many such web servers are set up such that both the domain root (e.g., and the</i> www <i>subdomain (e.g., refer to the same site; others require one form or the other, or they may map to different web sites. The use of a subdomain name is useful for <a href="/ed/Load_balancing_(computing)" id="w">load balancing</a> incoming web traffic by creating a <a href="/ed/CNAME_record" id="w">CNAME record</a> that points to a cluster of web servers. Since, currently, only a subdomain can be used in a CNAME, the same result cannot be achieved by using the bare domain root. When a user submits an incomplete domain name to a web browser in its address bar input field, some web browsers automatically try adding the prefix "www" to the beginning of it and possibly ".com", ".org" and ".net" at the end, depending on what might be missing. For example, entering '' may be transformed to</i> <i>and 'openoffice' to</i><i>. This feature started appearing in early versions of Mozilla <a href="/ed/Firefox" id="w">Firefox</a>, when it still had the working title 'Firebird' in early 2003, from an earlier practice in browsers such as <a href="/ed/Lynx_(web_browser)" id="w">Lynx</a>.<sup id="_ref-29" class="reference"><a href="#_note-29" title="">[29]</a></sup> It is reported that Microsoft was granted a US patent for the same idea in 2008, but only for mobile devices.<sup id="_ref-30" class="reference"><a href="#_note-30" title="">[30]</a></sup> In English, <a href="/ed/Pronunciation_of_%26quot%3Bwww%26quot%3B" id="w"><i>www</i> is pronounced</a> by individually pronouncing the name of characters (</i>double-u double-u double-u<i>) or by saying the phrase <b>"triple double-u"</b>. Although some technical users pronounce it</i> dub-dub-dub<i>, this is not widespread (although is commonly used by the general public in New Zealand). The English writer <a href="/ed/Douglas_Adams" id="w">Douglas Adams</a> once quipped in <a href="/ed/The_Independent" id="w">The Independent on Sunday</a> (1999): "The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it's short for," with Stephen Fry later pronouncing it in his "Podgrammes" series of podcasts as "wuh wuh wuh." In Mandarin Chinese,</i> World Wide Web <i>is commonly translated via a <a href="/ed/Phono-semantic_matching" id="w">phono-semantic matching</a> to</i> w n w i w ng <i>(), which satisfies</i> www <i>and literally means "myriad dimensional net",<sup id="_ref-31" class="reference"><a href="#_note-31" title="">[31]</a></sup> a translation that very appropriately reflects the design concept and proliferation of the World Wide Web. Tim Berners-Lee's web-space states that</i> World Wide Web <i>is officially spelled as three separate words, each capitalized, with no intervening hyphens.<sup id="_ref-32" class="reference"><a href="#_note-32" title="">[32]</a></sup> Use of the www prefix is declining as <a href="/ed/Web_2.0" id="w">Web 2.0</a> <a href="/ed/Web_application" id="w">web applications</a> seek to <a href="/ed/Brand" id="w">brand</a> their domain names and make them easily pronounceable.<sup id="_ref-33" class="reference"><a href="#_note-33" title="">[33]</a></sup> As the <a href="/ed/Mobile_web" id="w">mobile web</a> grows in popularity, services like <a href="/ed/Google_Mail" id="w">Gmail</a>.com, <a href="/ed/MySpace" id="w">MySpace</a>.com, <a href="/ed/Facebook" id="w">Facebook</a>.com, <a href="/ed/Bebo" id="w">Bebo</a>.com and <a href="/ed/Twitter" id="w">Twitter</a>.com are most often discussed without adding the www to the domain (or the .com).</i></p> <a id="Specifiers:_http_and_https" name="Specifiers:_http_and_https"></a> <h3>Specifiers: http and https</h3> <p>The scheme specifiers (<i>http://</i> or <i>https://</i>) in <a href="/ed/Uniform_Resource_Identifier" id="w">URIs</a> refer to the <a href="/ed/Hypertext_Transfer_Protocol" id="w">Hypertext Transfer Protocol</a> and to <a href="/ed/HTTP_Secure" id="w">HTTP Secure</a>, respectively, and so define the communication protocol to be used for the request and response. The HTTP protocol is fundamental to the operation of the World Wide Web; the added encryption layer in HTTPS is essential when confidential information such as passwords or banking information are to be exchanged over the public Internet. Web browsers usually prepend the scheme to URLs too, if omitted.</p> <a id="Web_Servers" name="Web_Servers"></a> <h2>Web Servers</h2> <p></p> <p>The primary function of a web server is to deliver web pages on the request to clients. This means delivery of HTML documents and any additional content that may be included by a document, such as images, style sheets and scripts.</p> <a id="Privacy" name="Privacy"></a> <h2>Privacy</h2> <p>It is possible that average computer users who use the World Wide Web mainly for things like entertainment may have surrendered their right to privacy in exchange for using a number of services available on the World Wide Web.<sup id="_ref-Bits_a" class="reference"><a href="#_note-Bits" title="">[34]</a></sup> For example: more than half a billion people worldwide have used a <a href="/ed/Social_network_service" id="w">social network service</a>,<sup id="_ref-35" class="reference"><a href="#_note-35" title="">[35]</a></sup> and of the generations of people within the United States who have had access to the internet from a young age, half have some form of Social Networking presence<sup id="_ref-36" class="reference"><a href="#_note-36" title="">[36]</a></sup> and are part of a generational shift that could be changing norms.<sup id="_ref-37" class="reference"><a href="#_note-37" title="">[37]</a></sup><sup id="_ref-38" class="reference"><a href="#_note-38" title="">[38]</a></sup> The social network Facebook progressed from U.S. college students to a 70% non-U.S. audience, but in 2009 estimated that only 20% of its members use privacy settings.<sup id="_ref-39" class="reference"><a href="#_note-39" title="">[39]</a></sup> In 2010 (six years after co-founding the company), <a href="/ed/Mark_Zuckerberg" id="w">Mark Zuckerberg</a> wrote, "we will add privacy controls that are much simpler to use".<sup id="_ref-40" class="reference"><a href="#_note-40" title="">[40]</a></sup></p> <p>Privacy representatives from 60 countries have resolved to ask for laws to complement industry self-regulation, for education for children and other minors who use the Web, and for default protections for users of social networks.<sup id="_ref-conference_a" class="reference"><a href="#_note-conference" title="">[41]</a></sup> They also believe data protection for <a href="/ed/Personally_identifiable_information" id="w">personally identifiable information</a> benefits business more than the sale of that information.<sup id="_ref-conference_b" class="reference"><a href="#_note-conference" title="">[41]</a></sup> Users can opt-in to features in browsers to clear their personal histories locally and block some <a href="/ed/HTTP_cookie" id="w">cookies</a> and <a href="/ed/Advertising_network" id="w">advertising networks</a><sup id="_ref-42" class="reference"><a href="#_note-42" title="">[42]</a></sup> but they are still tracked in websites' <a href="/ed/Server_log" id="w">server logs</a>, and in particular <a href="/ed/Web_beacons" id="w">web beacons</a>.<sup id="_ref-43" class="reference"><a href="#_note-43" title="">[43]</a></sup> Berners-Lee and colleagues see hope in accountability and appropriate use achieved by extending the Web's architecture to policy awareness, perhaps with audit logging, reasoners and appliances.<sup id="_ref-Weitzner_a" class="reference"><a href="#_note-Weitzner" title="">[44]</a></sup></p> <p>In exchange for providing free content, vendors hire advertisers who spy on Web users and base their business model on tracking them.<sup id="_ref-Angwin_a" class="reference"><a href="#_note-Angwin" title="">[45]</a></sup> Since 2009, they buy and sell consumer data on exchanges (lacking a few details that could make it possible to de-anonymize, or identify an individual).<sup id="_ref-Angwin_b" class="reference"><a href="#_note-Angwin" title="">[45]</a></sup><sup id="_ref-46" class="reference"><a href="#_note-46" title="">[46]</a></sup> Hundreds of millions of times per day, Lotame Solutions captures what users are typing in real time, and sends that text to OpenAmplify who then tries to determine, to quote a writer at <i><a href="/ed/The_Wall_Street_Journal" id="w">The Wall Street Journal</a></i>, "what topics are being discussed, how the author feels about those topics, and what the person is going to do about them".<sup id="_ref-47" class="reference"><a href="#_note-47" title="">[47]</a></sup><sup id="_ref-48" class="reference"><a href="#_note-48" title="">[48]</a></sup></p> <p><a href="/ed/Microsoft" id="w">Microsoft</a> backed away in 2008 from its plans for strong privacy features in Internet Explorer,<sup id="_ref-49" class="reference"><a href="#_note-49" title="">[49]</a></sup> leaving its users (50% of the world's Web users) open to advertisers who may make assumptions about them based on only one click when they visit a website.<sup id="_ref-50" class="reference"><a href="#_note-50" title="">[50]</a></sup> Among services paid for by advertising, <a href="/ed/Yahoo!" id="w">Yahoo!</a> could collect the most data about users of commercial websites, about 2,500 bits of information per month about each typical user of its site and its affiliated advertising network sites. Yahoo! was followed by MySpace with about half that potential and then by <a href="/ed/AOL" id="w">AOL</a> <a href="/ed/TimeWarner" id="w">TimeWarner</a>, <a href="/ed/Google" id="w">Google</a>, Facebook, Microsoft, and <a href="/ed/EBay" id="w">eBay</a>.<sup id="_ref-51" class="reference"><a href="#_note-51" title="">[51]</a></sup></p> <a id="Security" name="Security"></a> <h2>Security</h2> <p>The Web has become criminals' preferred pathway for spreading <a href="/ed/Malware" id="w">malware</a>. Cybercrime carried out on the Web can include <a href="/ed/Identity_theft" id="w">identity theft</a>, <a href="/ed/Fraud" id="w">fraud</a>, espionage and <a href="/ed/Intelligence_gathering" id="w">intelligence gathering</a>.<sup id="_ref-Ben-Itzhak_a" class="reference"><a href="#_note-Ben-Itzhak" title="">[52]</a></sup> Web-based <a href="/ed/Vulnerability_(computing)" id="w">vulnerabilities</a> now outnumber traditional computer security concerns,<sup id="_ref-53" class="reference"><a href="#_note-53" title="">[53]</a></sup><sup id="_ref-54" class="reference"><a href="#_note-54" title="">[54]</a></sup> and as measured by <a href="/ed/Google" id="w">Google</a>, about one in ten web pages may contain malicious code.<sup id="_ref-55" class="reference"><a href="#_note-55" title="">[55]</a></sup> Most Web-based <a href="/ed/Attack_(computing)" id="w">attacks</a> take place on legitimate websites, and most, as measured by <a href="/ed/Sophos" id="w">Sophos</a>, are hosted in the United States, China and Russia.<sup id="_ref-Sophos-Q1-2008_a" class="reference"><a href="#_note-Sophos-Q1-2008" title="">[56]</a></sup> The most common of all malware <a href="/ed/Threat_(computer)" id="w">threats</a> is <a href="/ed/SQL_injection" id="w">SQL injection</a> attacks against websites.<sup id="_ref-57" class="reference"><a href="#_note-57" title="">[57]</a></sup> Through HTML and URIs the Web was vulnerable to attacks like <a href="/ed/Cross-site_scripting" id="w">cross-site scripting</a> (XSS) that came with the introduction of JavaScript<sup id="_ref-FGHR_a" class="reference"><a href="#_note-FGHR" title="">[58]</a></sup> and were exacerbated to some degree by Web 2.0 and Ajax <a href="/ed/Web_design" id="w">web design</a> that favors the use of scripts.<sup id="_ref-59" class="reference"><a href="#_note-59" title="">[59]</a></sup> Today by one estimate, 70% of all websites are open to XSS attacks on their users.<sup id="_ref-60" class="reference"><a href="#_note-60" title="">[60]</a></sup></p> <p>Proposed solutions vary to extremes. Large security vendors like <a href="/ed/McAfee" id="w">McAfee</a> already design governance and compliance suites to meet post-9/11 regulations,<sup id="_ref-61" class="reference"><a href="#_note-61" title="">[61]</a></sup> and some, like <a href="/ed/Finjan" id="w">Finjan</a> have recommended active real-time inspection of code and all content regardless of its source.<sup id="_ref-Ben-Itzhak_b" class="reference"><a href="#_note-Ben-Itzhak" title="">[52]</a></sup> Some have argued that for enterprise to see security as a business opportunity rather than a cost center,<sup id="_ref-62" class="reference"><a href="#_note-62" title="">[62]</a></sup> "ubiquitous, always-on digital rights management" enforced in the infrastructure by a handful of organizations must replace the hundreds of companies that today secure data and networks.<sup id="_ref-63" class="reference"><a href="#_note-63" title="">[63]</a></sup> <a href="/ed/Jonathan_Zittrain" id="w">Jonathan Zittrain</a> has said users sharing responsibility for computing safety is far preferable to locking down the Internet.<sup id="_ref-64" class="reference"><a href="#_note-64" title="">[64]</a></sup></p> <a id="Standards" name="Standards"></a> <h2>Standards</h2> <p></p> <p>Many formal standards and other technical specifications and software define the operation of different aspects of the World Wide Web, the Internet, and computer information exchange. Many of the documents are the work of the World Wide Web Consortium (W3C), headed by Berners-Lee, but some are produced by the <a href="/ed/Internet_Engineering_Task_Force" id="w">Internet Engineering Task Force</a> (IETF) and other organizations.</p> <p>Usually, when web standards are discussed, the following publications are seen as foundational:</p> <ul> <li>Recommendations for <a href="/ed/Markup_languages" id="w">markup languages</a>, especially <a href="/ed/HTML" id="w">HTML</a> and <a href="/ed/XHTML" id="w">XHTML</a>, from the W3C. These define the structure and interpretation of <a href="/ed/Hypertext" id="w">hypertext</a> documents.</li> <li>Recommendations for <a href="/ed/Style_sheet_(web_development)" id="w">stylesheets</a>, especially <a href="/ed/Cascading_Style_Sheets" id="w">CSS</a>, from the W3C.</li> <li>Standards for <a href="/ed/ECMAScript" id="w">ECMAScript</a> (usually in the form of <a href="/ed/JavaScript" id="w">JavaScript</a>), from <a href="/ed/Ecma_International" id="w">Ecma International</a>.</li> <li>Recommendations for the <a href="/ed/Document_Object_Model" id="w">Document Object Model</a>, from W3C.</li> </ul> <p>Additional publications provide definitions of other essential technologies for the World Wide Web, including, but not limited to, the following:</p> <ul> <li> <i>Uniform Resource Identifier</i> (<a href="/ed/Uniform_Resource_Identifier" id="w">URI</a>), which is a universal system for referencing resources on the Internet, such as hypertext documents and images. URIs, often called URLs, are defined by the IETF's RFC 3986 / STD 66: <i>Uniform Resource Identifier (URI): Generic Syntax</i>, as well as its predecessors and numerous <a href="/ed/URI_scheme" id="w">URI scheme</a>-defining <a href="/ed/Request_For_Comments" id="w">RFCs</a>;</li> <li> <i>HyperText Transfer Protocol (HTTP)</i>, especially as defined by RFC 2616: <i>HTTP/1.1</i> and RFC 2617: <i>HTTP Authentication</i>, which specify how the browser and server authenticate each other.</li> </ul> <a id="Accessibility" name="Accessibility"></a> <h2>Accessibility</h2> <p></p> <p>Access to the Web is for everyone regardless of disability including visual, auditory, physical, speech, cognitive, and neurological. Accessibility features also help others with temporary disabilities like a broken arm or the aging population as their abilities change.<sup id="_ref-WAI_a" class="reference"><a href="#_note-WAI" title="">[65]</a></sup> The Web is used for receiving information as well as providing information and interacting with society, making it essential that the Web be accessible in order to provide equal access and <a href="/ed/Equal_opportunity" id="w">equal opportunity</a> to people with disabilities.<sup id="_ref-66" class="reference"><a href="#_note-66" title="">[66]</a></sup> Tim Berners-Lee once noted, "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."<sup id="_ref-WAI_b" class="reference"><a href="#_note-WAI" title="">[65]</a></sup> Many countries regulate <a href="/ed/Web_accessibility" id="w">web accessibility</a> as a requirement for websites.<sup id="_ref-67" class="reference"><a href="#_note-67" title="">[67]</a></sup> International cooperation in the W3C <a href="/ed/Web_Accessibility_Initiative" id="w">Web Accessibility Initiative</a> led to simple guidelines that web content authors as well as software developers can use to make the Web accessible to persons who may or may not be using <a href="/ed/Assistive_technology" id="w">assistive technology</a>.<sup id="_ref-WAI_c" class="reference"><a href="#_note-WAI" title="">[65]</a></sup><sup id="_ref-68" class="reference"><a href="#_note-68" title="">[68]</a></sup></p> <a id="Internationalization" name="Internationalization"></a> <h2>Internationalization</h2> <p>The W3C <a href="/ed/Internationalization_and_localization" id="w">Internationalization</a> Activity assures that web technology will work in all languages, scripts, and cultures.<sup id="_ref-69" class="reference"><a href="#_note-69" title="">[69]</a></sup> Beginning in 2004 or 2005, <a href="/ed/Unicode" id="w">Unicode</a> gained ground and eventually in December 2007 surpassed both <a href="/ed/ASCII" id="w">ASCII</a> and Western European as the Web's most frequently used <a href="/ed/Character_encoding" id="w">character encoding</a>.<sup id="_ref-70" class="reference"><a href="#_note-70" title="">[70]</a></sup> Originally RFC 3986 allowed resources to be identified by <a href="/ed/URI" id="w">URI</a> in a subset of US-ASCII. RFC 3987 allows more characters any character in the <a href="/ed/Universal_Character_Set" id="w">Universal Character Set</a> and now a resource can be identified by <a href="/ed/Internationalized_Resource_Identifier" id="w">IRI</a> in any language.<sup id="_ref-71" class="reference"><a href="#_note-71" title="">[71]</a></sup></p> <a id="Statistics" name="Statistics"></a> <h2>Statistics</h2> <p>Between 2005 and 2010, the number of Web users doubled, and was expected to surpass two billion in 2010.<sup id="_ref-72" class="reference"><a href="#_note-72" title="">[72]</a></sup> Early studies in 1998 and 1999 estimating the size of the web using capture/recapture methods showed that much of the web was not indexed by search engines and the web was much larger than expected<sup id="_ref-73" class="reference"><a href="#_note-73" title="">[73]</a></sup><sup id="_ref-74" class="reference"><a href="#_note-74" title="">[74]</a></sup>. According to a 2001 study, there were a massive number, over 550 billion, of documents on the Web, mostly in the invisible Web, or <a href="/ed/Deep_Web" id="w">Deep Web</a>.<sup id="_ref-75" class="reference"><a href="#_note-75" title="">[75]</a></sup> A 2002 survey of 2,024 million Web pages<sup id="_ref-76" class="reference"><a href="#_note-76" title="">[76]</a></sup> determined that by far the most Web content was in English: 56.4%; next were pages in German (7.7%), French (5.6%), and Japanese (4.9%). A more recent study, which used Web searches in 75 different languages to sample the Web, determined that there were over 11.5 billion Web pages in the <a href="/ed/Surface_Web" id="w">publicly indexable Web</a> as of the end of January 2005.<sup id="_ref-77" class="reference"><a href="#_note-77" title="">[77]</a></sup> , the indexable web contains at least 25.21 billion pages.<sup id="_ref-78" class="reference"><a href="#_note-78" title="">[78]</a></sup> On July 25, 2008, Google software engineers Jesse Alpert and Nissan Hajaj announced that <a href="/ed/Google_Search" id="w">Google Search</a> had discovered one trillion unique URLs.<sup id="_ref-79" class="reference"><a href="#_note-79" title="">[79]</a></sup> , over 109.5 million domains operated.<sup id="_ref-NI_a" class="reference"><a href="#_note-NI" title="">[80]</a></sup> Of these 74% were commercial or other sites operating in the <code>.com</code> <a href="/ed/Generic_top-level_domain" id="w">generic top-level domain</a>.<sup id="_ref-NI_b" class="reference"><a href="#_note-NI" title="">[80]</a></sup></p> <p>Statistics measuring a website's popularity are usually based either on the number of <a href="/ed/Page_view" id="w">page views</a> or on associated server '<a href="/ed/Hit_(internet)" id="w">hits</a>' (file requests) that it receives.</p> <a id="Speed_issues" name="Speed_issues"></a> <h2>Speed issues</h2> <p>Frustration over <a href="/ed/Network_congestion" id="w">congestion</a> issues in the Internet infrastructure and the high <a href="/ed/Latency_(engineering)" id="w">latency</a> that results in slow browsing has led to a pejorative name for the World Wide Web: the <i>World Wide Wait</i>.<sup id="_ref-81" class="reference"><a href="#_note-81" title="">[81]</a></sup> Speeding up the Internet is an ongoing discussion over the use of <a href="/ed/Peering" id="w">peering</a> and <a href="/ed/Quality_of_service" id="w">QoS</a> technologies. Other solutions to reduce the congestion can be found at <a href="/ed/W3C" id="w">W3C</a>.<sup id="_ref-82" class="reference"><a href="#_note-82" title="">[82]</a></sup> <a href="/ed/Guideline" id="w">Guidelines</a> for Web response times are:<sup id="_ref-83" class="reference"><a href="#_note-83" title="">[83]</a></sup></p> <ul> <li>0.1 second (one tenth of a second). Ideal response time. The user does not sense any interruption.</li> <li>1 second. Highest acceptable response time. Download times above 1 second interrupt the user experience.</li> <li>10 seconds. Unacceptable response time. The user experience is interrupted and the user is likely to leave the site or system.</li> </ul> <a id="Caching" name="Caching"></a> <h2>Caching</h2> <p>If a user revisits a Web page after only a short interval, the page data may not need to be re-obtained from the source Web server. Almost all web browsers <a href="/ed/Browser_cache" id="w">cache</a> recently obtained data, usually on the local hard drive. HTTP requests sent by a browser will usually ask only for data that has changed since the last download. If the locally cached data are still current, it will be reused. Caching helps reduce the amount of Web traffic on the Internet. The decision about expiration is made independently for each downloaded file, whether image, <a href="/ed/Cascading_Style_Sheets" id="w">stylesheet</a>, <a href="/ed/JavaScript" id="w">JavaScript</a>, HTML, or whatever other content the site may provide. Thus even on sites with highly dynamic content, many of the basic resources need to be refreshed only occasionally. Web site designers find it worthwhile to collate resources such as CSS data and JavaScript into a few site-wide files so that they can be cached efficiently. This helps reduce page download times and lowers demands on the Web server.</p> <p>There are other components of the Internet that can cache Web content. Corporate and academic <a href="/ed/Firewall_(networking)" id="w">firewalls</a> often cache Web resources requested by one user for the benefit of all. (See also <a href="/ed/Web_proxy#Caching%20proxy%20servers" id="w">Caching proxy server</a>.) Some <a href="/ed/Search_engines" id="w">search engines</a> also store cached content from websites. Apart from the facilities built into Web servers that can determine when files have been updated and so need to be re-sent, designers of dynamically generated Web pages can control the HTTP headers sent back to requesting users, so that transient or sensitive pages are not cached. <a href="/ed/Online_banking" id="w">Internet banking</a> and news sites frequently use this facility. Data requested with an <a href="/ed/Hypertext_Transfer_Protocol" id="w">HTTP</a> 'GET' is likely to be cached if other conditions are met; data obtained in response to a 'POST' is assumed to depend on the data that was POSTed and so is not cached.</p> <a id="See_also" name="See_also"></a> <h2>See also</h2> <p></p> <ul> <li><a href="/ed/Electronic_publishing" id="w">Electronic publishing</a></li> <li><a href="/ed/Lists_of_websites" id="w">Lists of websites</a></li> <li><a href="/ed/Prestel" id="w">Prestel</a></li> <li><a href="/ed/Streaming_media" id="w">Streaming media</a></li> <li><a href="/ed/Web_1.0" id="w">Web 1.0</a></li> <li><a href="/ed/Webgraph" id="w">Webgraph</a></li> </ul> <a id="References" name="References"></a> <h2>References</h2> <p></p> <a id="Further_reading" name="Further_reading"></a> <h2>Further reading</h2> <ul> <li>Niels Br gger, ed. <i>Web History</i> (2010) 362 pages; Historical perspective on the World Wide Web, including issues of culture, content, and preservation.</li> <li> <li> <li> <li> </ul> <a id="External_links" name="External_links"></a> <h2>External links</h2> <p></p> <ul> <li><a class="externallink" href="" rel="nofollow" title="">Early archive of the first Web site</a></li> <li><a class="externallink" href="" rel="nofollow" title="">Internet Statistics: Growth and Usage of the Web and the Internet</a></li> <li> <a class="externallink" href="" rel="nofollow" title="">Living Internet</a> A comprehensive history of the Internet, including the World Wide Web.</li> <li> <li><a class="externallink" href="" rel="nofollow" title="">World Wide Web Consortium (W3C)</a></li> <li><a class="externallink" href="" rel="nofollow" title="">W3C Recommendations Reduce "World Wide Wait"</a></li> <li> <a class="externallink" href="" rel="nofollow" title="">World Wide Web Size</a> Daily estimated size of the World Wide Web.</li> <li><a class="externallink" href="" rel="nofollow" title="">Antonio A. Casilli, Some Elements for a Sociology of Online Interactions</a></li> <li> <a class="externallink" href="" rel="nofollow" title="">The Erd s Webgraph Server</a> offers weekly updated graph representation of a constantly increasing fraction of the WWW.</li> </ul> <p></p> <p></p> <p></p> <p><a href="" rel="nofollow">als:World Wide Web</a> <a href="" rel="nofollow">ang:Woruldw d Webb</a> <a href="" rel="nofollow">ar:</a> <a href="" rel="nofollow">an:World Wide Web</a> <a href="" rel="nofollow">as:</a> <a href="" rel="nofollow">ast:Web</a> <a href="" rel="nofollow">az: mumd nya h r m k toru</a> <a href="" rel="nofollow">bn:</a> <a href="" rel="nofollow">ba:</a> <a href="" rel="nofollow">be:World Wide Web</a> <a href="" rel="nofollow">be-x-old:</a> <a href="" rel="nofollow">bg:World Wide Web</a> <a href="" rel="nofollow">bs:World Wide Web</a> <a href="" rel="nofollow">br:World Wide Web</a> <a href="" rel="nofollow">ca:World Wide Web</a> <a href="" rel="nofollow">cs:World Wide Web</a> <a href="" rel="nofollow">cy:Gwe fyd-eang</a> <a href="" rel="nofollow">da:World Wide Web</a> <a href="/ed/Pdc:Weltweit_Gewebb" id="w">pdc:Weltweit Gewebb</a> <a href="" rel="nofollow">de:World Wide Web</a> <a href="" rel="nofollow">et:Veeb</a> <a href="" rel="nofollow">el:</a> <a href="/ed/Eml:Gran_Tlar%C3%A8_mundi%C3%A8l" id="w">eml:Gran Tlar mundi l</a> <a href="" rel="nofollow">es:World Wide Web</a> <a href="" rel="nofollow">eo:TTT</a> <a href="" rel="nofollow">eu:World Wide Web</a> <a href="" rel="nofollow">fa:</a> <a href="" rel="nofollow">fo:Heimsvevur</a> <a href="" rel="nofollow">fr:World Wide Web</a> <a href="" rel="nofollow">ga:Gr as n Domhanda</a> <a href="" rel="nofollow">gl:World Wide Web</a> <a href="/ed/Gan:%E8%90%AC%E7%B6%AD%E7%B6%B2" id="w">gan:</a> <a href="" rel="nofollow">gu:</a> <a href="" rel="nofollow">ko:</a> <a href="" rel="nofollow">hy:</a> <a href="" rel="nofollow">hi:</a> <a href="" rel="nofollow">hr:World Wide Web</a> <a href="/ed/Ilo:Web" id="w">ilo:Web</a> <a href="" rel="nofollow">id:World Wide Web</a> <a href="" rel="nofollow">ia:World Wide Web</a> <a href="" rel="nofollow">is:Veraldarvefurinn</a> <a href="" rel="nofollow">it:World Wide Web</a> <a href="" rel="nofollow">he:World Wide Web</a> <a href="" rel="nofollow">kn:</a> <a href="" rel="nofollow">kk:</a> <a href="" rel="nofollow">ku:World Wide Web</a> <a href="/ed/Lad:Web" id="w">lad:Web</a> <a href="" rel="nofollow">la:Tela totius terrae</a> <a href="" rel="nofollow">lv:Vispasaules t meklis</a> <a href="" rel="nofollow">lb:World Wide Web</a> <a href="" rel="nofollow">lt:Saitynas</a> <a href="" rel="nofollow">hu:Vil gh l</a> <a href="" rel="nofollow">mk:</a> <a href="" rel="nofollow">mg:Tranonkala</a> <a href="" rel="nofollow">ml:</a> <a href="" rel="nofollow">mr:</a> <a href="/ed/Arz:%D9%88%D9%8A%D8%A8" id="w">arz:</a> <a href="/ed/Mzn:%D9%88%D8%A8" id="w">mzn:</a> <a href="" rel="nofollow">ms:Jaringan Sejagat</a> <a href="" rel="nofollow">mn:</a> <a href="" rel="nofollow">my:</a> <a href="" rel="nofollow">nl:Wereldwijd web</a> <a href="" rel="nofollow">ja:World Wide Web</a> <a href="" rel="nofollow">no:World Wide Web</a> <a href="" rel="nofollow">nn:Verdsveven</a> <a href="" rel="nofollow">oc:World Wide Web</a> <a href="/ed/Mhr:%D0%A2%D3%B1%D0%BD%D1%8F%D0%BC%D0%B1%D0%B0%D0%BB_%D1%8D%D2%A5%D1%8B%D1%80%D0%B5%D0%BC%D1%8B%D1%88%D0%B2%D0%BE%D1%82" id="w">mhr:</a> <a href="/ed/Pnb:%D9%88%D8%B1%D9%84%DA%88_%D9%88%D8%A7%D8%A6%DA%88_%D9%88%DB%8C%D8%A8" id="w">pnb:</a> <a href="" rel="nofollow">ps:WWW</a> <a href="/ed/Pcd:Arnitoile_(Intarn%C3%A8te)" id="w">pcd:Arnitoile (Intarn te)</a> <a href="" rel="nofollow">pl:World Wide Web</a> <a href="" rel="nofollow">pt:World Wide Web</a> <a href="" rel="nofollow">ro:World Wide Web</a> <a href="" rel="nofollow">rm:World Wide Web</a> <a href="/ed/Rue:%D0%A6%D1%96%D0%BB%D0%BE%D1%81%D0%B2%D1%96%D1%82%D0%BE%D0%B2%D0%B0_%D0%BF%D0%B0%D0%B2%D1%83%D1%87%D1%96%D0%BD%D0%B0" id="w">rue:</a> <a href="" rel="nofollow">ru:</a> <a href="/ed/Sah:World_Wide_Web" id="w">sah:World Wide Web</a> <a href="" rel="nofollow">sq:World Wide Web</a> <a href="" rel="nofollow">scn:World Wide Web</a> <a href="" rel="nofollow">si:</a> <a href="" rel="nofollow">simple:World Wide Web</a> <a href="" rel="nofollow">sk:World Wide Web</a> <a href="" rel="nofollow">sl:Splet</a> <a href="" rel="nofollow">so:World Wide Web</a> <a href="/ed/Ckb:%D8%AA%DB%95%D9%88%D9%86%DB%8C_%D8%A8%DB%95%D8%B1%D8%A8%DA%B5%D8%A7%D9%88%DB%8C_%D8%AC%DB%8C%DA%BE%D8%A7%D9%86%DB%8C" id="w">ckb:</a> <a href="" rel="nofollow">sr:</a> <a href="" rel="nofollow">sh:World Wide Web</a> <a href="" rel="nofollow">fi:World Wide Web</a> <a href="" rel="nofollow">sv:World Wide Web</a> <a href="" rel="nofollow">tl:World Wide Web</a> <a href="" rel="nofollow">ta:</a> <a href="/ed/Kab:World_Wide_Web" id="w">kab:World Wide Web</a> <a href="" rel="nofollow">te:</a> <a href="" rel="nofollow">th:</a> <a href="" rel="nofollow">tr:World Wide Web</a> <a href="" rel="nofollow">uk:</a> <a href="" rel="nofollow">ur:</a> <a href="/ed/Vec:Web" id="w">vec:Web</a> <a href="" rel="nofollow">vi:World Wide Web</a> <a href="/ed/Fiu-vro:WWW" id="w">fiu-vro:WWW</a> <a href="" rel="nofollow">wa:Daegntoele s waibes</a> <a href="/ed/War:World_Wide_Web" id="w">war:World Wide Web</a> <a href="" rel="nofollow">wo:World Wide Web</a> <a href="" rel="nofollow">yi:World Wide Web</a> <a href="/ed/Zh-yue:%E8%90%AC%E7%B6%AD%E7%B6%B2" id="w">zh-yue:</a> <a href="" rel="nofollow">zh:</a></p> <p></p> </td> </tr> </table> <center> <br> <br> <br> <br> <form action="/encyclopedia/sencyclo.jsp"> <input type="text" name="keywords" maxlength="100" size="40"> <input type="submit" value="Search Encyclopedia"> </form> <hr width="500" size="1"> Source: <a href="/rd.jsp?">Wikipedia</a> | The above article is available under the <a href="/rd.jsp?">GNU FDL.</a> | <a href="/rd.jsp?">Edit this article</a> </center> <br> <br> <br> <center> <table bgcolor="#E5F6FF" width="500" class="tabsnip13"> <tr> <td align="left">Search for <a href="/t/World+Wide+Web"><b>World Wide Web</b></a> in Tutorials</td> </tr> <tr> <td align="left">Search for <a href="/World+Wide+Web_es.html"><b>World Wide Web</b></a> in Encyclopedia</td> </tr> <tr> <td align="left">Search for <a href="/v/World+Wide+Web"><b>World Wide Web</b></a> in Videos</td> </tr> <tr> <td align="left">Search for <a href="/books.jsp?keywords=World+Wide+Web"><b>World Wide Web</b></a> in Books</td> </tr> <tr> <td align="left">Search for <a href="/software.jsp?keywords=World+Wide+Web"><b>World Wide Web</b></a> in Software</td> </tr> <tr> <td align="left">Search for <a href="/dvds.jsp?keywords=World+Wide+Web"><b>World Wide Web</b></a> in DVDs</td> </tr> <tr> <td align="left">Search for <a href="/store/index.php?k=World+Wide+Web&c=blended"><b>World Wide Web</b></a> in Store</td> </tr> </table> <br> <br> </center> </td> <td align="middle" style="{ vertical-align: top }"> <br> <br> <table align="right"> <tr> <td> <font size="1">Advertisement</font><br> <noscript><a href="" target="_blank" rel="nofollow"></a></noscript> </td> </tr> </table> </td> </tr> </table> <br> <br> <br> <br> <center> <font class="reg">World Wide Web in Encyclopedia</font><br> <img src="/images/uparrow.gif" border="0" alt="World_Wide_Web"> <a class="sl12" href="#">top</a> <img src="/images/uparrow.gif" border="0" alt="World_Wide_Web"><br> <hr class="foothr" width="600" size="1"> <font size="-1"><a href="/">Home</a> - <a href="/addtg.jsp">Add TutorGig to Your Site</a> - <a href="/disclaimer.jsp">Disclaimer</a></font> <script language="Javascript" type="text/JavaScript"> goog_lang_inc(); </script> <p><font size="-2">©2011-2013 All Rights Reserved. <a href="/privacy.jsp">Privacy Statement</a></font></p> <br> </center> </body> </html>