1. buzz buzz buzz buzz buzz buzz buzz buzz buzz buzz HTML5??? buzz buzz buzz buzz buzz buzz buzz buzz

2. Now HTML5… What is that?

3. HTML5 ~= HTML + CSS3 + JavaScript APIs

5. HTML 4 (1997) and XHTML 1 (2000)

6. Clearer separation of data and layout/style

7. Makes what you would already do in HTML easier

8. New Content Tags

9. <nav>, <section>, <header>, <article>, <aside>, <summary>

10. New Media Tags

11. <video>, <audio>, <figure>

12. New Dynamic drawing <canvas> graphic tag

13. A tag that allows programmatic drawing via JavaScript

14. Inline metadata to help search engines identify content

16. Improved selectors for determining which content to effect

17. (good support across modern browsers)

18. Embeddable font support (TTF, OTF)

19. Improved text layout with column support

20. Rounded corners, Reflections (WebKit)

22. Application Cache (offline access)

23. Multitasking (Worker processes)

24. Sockets (real-time server communication: chat, games, etc.)

25. Native Drag and Drop events

26. GeoLocation

28. Simpler, more intuitive syntax

29. Video and Audio without requiring a plugin

30. Incremental improvements to previous HTML challenges

31. Much needed next step in HTML evolution

32. Creative enhancements: Rounded corners, gradients, text layout

33. Emergence of more advanced technologies such as O3D (WebGL)

34. Easier SEO than plugin technologies

36. Video support is not standardized

37. Not currently a single codec that all browsers will support

38. Google WebM (VP 8) (open sourced by Google)

39. OggTheora (open source)

40. h.264/MP4 (potential licensing issues)

41. No supported DRM for video or audio

43. Only the newest and best have reasonable support

44. Internet Explorer will not have decent support until IE9

45. Challenges getting consistent page display across browsers

46. Graceful page degradation is potentially complex

47. Currently no designer tools for creating HTML5 animation or interactivity (all must be implemented by a developer)

49. A replacement for technologies such as Flash or Silverlight

50. Immersive RLP’s would be much more time consuming

51. Certain functionality would not be possible or cost-prohibitive

54. For HTML-based desktop experiences, consider simplified modular layout for streamlined restyling on mobile platforms

55. Don’t expect what has been traditionally executed in Flash or Silverlight to be cost-effective or even possible in HTML

56. Clearly understand the target USER and their needs before recommending a technology

58. http://en.wikipedia.org/wiki/HTML5

59. http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/

60. http://www.html5test.com/

61. http://newteevee.com/2010/05/13/hulu-html5-isnt-ready-for-prime-time/

62. http://www.htmlgoodies.com/daily_news/article.php/386914/Is-HTML-5-the-Flash-Killer-Its-sure-got-the-potential.htm

63. http://slides.html5rocks.com/

64. http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/

65. http://www.sencha.com/products/touch/