|
|
|
|
PRESENTER: Often when you visit a website, the website address will start with three small letters, www. The www stands for world wide web but have you ever thought, what is the world wide web? The world wide web is not the internet. I repeat, the world wide web is not the internet. The internet is a global network of computers, whereas the world wide web is an application that runs on the internet. It was created in 1989 by Sir Tim Berners-Lee. The internet already existed then. Sir Tim Berners-Lee found a way to use the connections of the Internet to bring together documents or web pages so that people could share information. The world wide web needs the internet to operate on. So, if you imagine the internet as the paths, the roads, the motorways all over the world, the world wide web would be like what you can see on these transport routes. The shops, the petrol stations, the businesses, the cafes would be like the web servers hosting the websites and the cars, buses and bikes would represent the content travelling around the network. Without the roads of the Internet connecting the web servers that provide the world wide web, no one could communicate, no data could be sent backwards and forwards. And without the world wide web, most of us would find it really difficult to access all that information. So, me popping into a shop is like me accessing the content from a website that's hosted on a web server. But of course, on the world wide web we don't have to go anywhere. You request the information from the web server and it sends it back.
Copyright © 2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. This specification defines an API for storing data in databases that can be queried using a variant of SQL. Beware. This specification is no longer in active maintenance and the Web Applications Working Group does not intend to maintain it further. This section describes the status of this document at the time of its publication. Other documents may supersede this document. This document is the 18 November 2010 Working Group Note of Web SQL Database. Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. The W3C Web Applications Working Group is the W3C working group responsible for this document.
This document was on the W3C Recommendation track but specification work has stopped. The specification reached an impasse: all interested implementors have used the same SQL backend (Sqlite), but we need multiple independent implementations to proceed along a standardisation path. The Web Applications Working Group continues work on two other storage-related specifications: Web Storage and Indexed Database API. Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this specification should join the aforementioned mailing lists and take part in the discussions. All feedback is welcome. The latest stable version of the editor's draft of this specification is always available on the W3C CVS server. This specification is automatically generated from the corresponding section in the HTML5 specification's source document, as hosted in the WHATWG Subversion repository.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. First, a function prepareDatabase() is defined. This function returns a handle to the database, first creating the database if necessary. Sometimes, there might be an arbitrary number of variables to substitute in. All diagrams, examples, and notes in this specification are non-normative, as are all sections explicitly marked non-normative. Everything else in this specification is normative.The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and abort these steps") are to be interpreted with the meaning of the key word ("must", "should", "may", etc) used in introducing the algorithm.Some conformance requirements are phrased as requirements on attributes, methods or objects.
|
|
