
"...you may be able to offer some objective advice on the following. One of the programmers said that he would recommend doing ours in HTML5 because it works on all recent browsers, works on I Phone and I Pad, is open source, is a Java based language and therefore can be done by a larger group of programmers, takes less memory, and requires no plug in."a recent email to my office
There is a lot of questions, confusion, and out-right mis-information surrounding HTML5 today. Over the next 90 minutes I hope to address these questions, and more:

At the W3CHTML5: A vocabulary and associated APIs for HTML and XHTML
At the WHAT WGThis specification evolves HTML and its related APIs to ease the authoring of Web-based applications.
http://dev.w3.org/html5/spec/spec.html
HTML5 is designed to provide a comprehensive application development platform for Web pages that eliminates the need to install third-party browser plug-ins.
HTML5 provides support for 2D graphics (canvas element), document editing, drag and drop, browser history management, video playback and local file storage.
At the W3CThe HTML5 specification contains a broad set of technologies at varying degrees of adoption and implementation.
At the WHAT WGWe moved to a new development model, where the technology is not versioned and instead we just have a living document that defines the technology as it evolves. We were going to change the name last year but ended up deciding to wait a bit since people still used the term "HTML5" a lot. However, the term is now basically being used to mean anything Web-standards-related, so it's time to move on!
I prefer “NEWT” which stands for New Exciting Web Technologies and can thus safely encompass real-HTML5, CSS 3, SVG, XHR2, Geolocation, Web Sockets, WOFF, Web DB, IndexedDB, WebGL and the like.
The WHAT WG prefers everything in one place.
The W3C prefers a more modular approach.
"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."
"Defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism."
Web Applications? Yes!
![[Graphic - Not HTML5]](images/not.png)
![[Photo - an endless row of filing cabinets]](images/storage.png)
Web Applications? Yes!
![[Graphic - Not HTML5]](images/not.png)
Common sources of location information include Global Positioning System (GPS) and location inferred from network signals such as IP address, RFID, WiFi and Bluetooth MAC addresses, and GSM/CDMA cell IDs, as well as user input.
No guarantee is given that the API returns the device's actual location.
http://dev.w3.org/geo/api/spec-source.htmlWeb Applications? Yes!
![[Graphic - Not HTML5]](images/not.png)
Web Applications? Yes!
![[Graphic - Not HTML5]](images/not.png)
(all together now...)
![[Graphic - Not HTML5]](images/not.png)
http://www.w3.org/TR/2010/WD-html-markup-20100304/
<!DOCTYPE html> <div id="header"> <header> <div id="nav"> <nav> <div id="footer"> <footer> <article> <aside> <section>
A number of problems today:
Like HTML5 Forms, Drag and Drop recognizes common functionality delivered via JavaScript & makes it native to the browser
Some people with poor fine motor control have difficulties making small movements and remaining steady. For this group of people, the dexterity requirements to accurately select and move an object using a pointing device can cause them problems, and they benefit from a keyboard equivalent being made available to allow them to use such functionality in a different way.
People with very poor eyesight are unable to perceive the start and end points of a drag and drop operation when it is conveyed in purely visual terms. For these two groups, drag and drop operations can be impossible to perform without accessibility considerations being designed into the process.
To be accessible, all functionality should be operable through the keyboard alone. Making drag and drop operations keyboard accessible is a relatively simple process, but there are a few extra challenges for people using assistive technologies, such as screen reader users and screen magnifier users.
![[Bargraph - HTML5 Accessibility support in current browsers]](images/a11y_support.jpg)
- source: http://www.html5accessibility.com/

http://soap.stanford.edu/presentations/postcard2