Mike Wilcox, profile picture
Uploaded byMike Wilcox
KEY, PDF1,337 views

The Fight Over HTML5

The document discusses the ongoing debate between the W3C and WHATWG regarding the future of HTML5, particularly focusing on its branding and the announcement that HTML5 will effectively cease to exist, becoming a living specification simply titled 'HTML.' The author critiques W3C's approach to standardization and its perceived disconnect from the practical needs of developers, leading to frustrations around deadlines and feature inclusions. There is also an exploration of broader implications for web technologies and the roles of major players like Mozilla, Apple, and Google in shaping web standards.

Embed presentation

Downloaded 44 times
1 / 127
2 / 127
3 / 127
4 / 127
5 / 127
6 / 127
7 / 127
8 / 127
9 / 127
10 / 127
11 / 127
12 / 127
13 / 127
14 / 127
15 / 127
16 / 127
17 / 127
18 / 127
19 / 127
20 / 127
21 / 127
22 / 127
23 / 127
24 / 127
25 / 127
26 / 127
27 / 127
28 / 127
29 / 127
30 / 127
31 / 127
32 / 127
33 / 127
34 / 127
35 / 127
36 / 127
37 / 127
38 / 127
39 / 127
40 / 127
41 / 127
42 / 127
43 / 127
44 / 127
45 / 127
46 / 127
47 / 127
48 / 127
49 / 127
50 / 127
51 / 127
52 / 127
53 / 127
54 / 127
55 / 127
56 / 127
57 / 127
58 / 127
59 / 127
60 / 127
61 / 127
62 / 127
63 / 127
64 / 127
65 / 127
66 / 127
67 / 127
68 / 127
69 / 127
70 / 127
71 / 127
72 / 127
73 / 127
74 / 127
75 / 127
76 / 127
77 / 127
78 / 127
79 / 127
80 / 127
81 / 127
82 / 127
83 / 127
84 / 127
85 / 127
86 / 127
87 / 127
88 / 127
89 / 127
90 / 127
91 / 127
92 / 127
93 / 127
94 / 127
95 / 127
96 / 127
97 / 127
98 / 127
99 / 127
100 / 127
101 / 127
102 / 127
103 / 127
104 / 127
105 / 127
106 / 127
107 / 127
108 / 127
109 / 127
110 / 127
111 / 127
112 / 127
113 / 127
114 / 127
115 / 127
116 / 127
117 / 127
118 / 127
119 / 127
120 / 127
121 / 127
122 / 127
123 / 127
124 / 127
125 / 127
126 / 127
127 / 127
The Fight Over HTML5 Are we to refer to it as HTML5 as the WC3 says or HTML as the WHATWG says? by Mike Wilcox March 2011
January 17th, 2011
January 17th, 2011 HTML5 Grows Up and Gets a Shiny New Logo
January 17th, 2011 HTML5 Grows Up and Gets a Shiny New Logo
New Logo! What’s Good
New Logo! What’s Good It shows the W3C is actually paying some attention to what is going on outside of their little world.
New Logo! What’s Good It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves.
New Logo! What’s Good It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations.
New Logo! What’s Good It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations. It comes with more logos!
New Logo! What’s Good It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations. It comes with more logos!
New Logo! What’s Bad
New Logo! What’s Bad We need a logo? There's no logo for CSS, JavaScript, or XML.
New Logo! What’s Bad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves.
New Logo! What’s Bad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves. Flash doesn't even have a logo. The IDE does, but AS3 doesn't.
New Logo! What’s Bad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves. Flash doesn't even have a logo. The IDE does, but AS3 doesn't. Hey! Some of those sub-logos have nothing to do with HTML5!
New Logo
New Logo By the way, nobody asked me but...
New Logo By the way, nobody asked me but... Designed by Occupop in Hawaii Price: $10 billion Time: 12 years
New Logo By the way, nobody asked me but... Done by Mike Wilcox Designed by Occupop in Hawaii Price: $0.00 Time: 15 minutes Price: $10 billion Time: 12 years
January 19th, 2011
January 19th, 2011 The WHATWG announces that HTML5 will no longer exist.
January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist.
January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. HTML5
January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH HTML5
January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH The specification will be known as “HTML” HTML5
January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH The specification will be known as “HTML” No more deadlines. It will be a LIVING SPEC. HTML5
Versionitus
Versionitus Outrage ensues.
Versionitus Outrage ensues. Can we still use the term HTML5?
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never!
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!!
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target?
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5?
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess!
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess! If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future.
Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess! If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future. Someone really said that on th WHATWG blog e
The W3C Backtrack
The W3C Backtrack
The W3C Backtrack " This is no t the offic ial logo ye t"
The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 specification? A: !No, not all of them.
The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 W3C w ill cont inue to use specification? "Open Web Platform" as A: !No, not all of them. well [as HTML5], an d we may have a corresponding logo.
The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 W3C w ill cont inue to use specification? "Open Web Platform" as A: !No, not all of them. well [as HTML5], an d we may have a corresponding logo. Ian Jacobs Head of W3C Marketing and Communications
and then...
February 14, 2011
February 14, 2011 28 d ays later
February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014.
February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Okay. It’s DONE.
February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Developers, it’s safe to use it Okay. It’s now. DONE.
February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Developers, it’s safe to use it Okay. It’s now. DONE. Last Call: MAY!!?!
Developers Rejoice!
Developers Rejoice! ...or do they?
What’s Missing
What’s Missing Because of the aggressive timeline, some things may not make the cut.
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT)
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D WebSockets
What’s Missing Because of the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D WebSockets The W3C originally said HTML5 would be done in 2010. I’m just sayin’.
The W3C or the WHATWG?
The W3C or the WHATWG?
Who are the WHATWG?
Who are the WHATWG? yeah, who am I?
Mozilla and Opera proposed to the W3C:
Mozilla and Opera proposed to the W3C: Would you please drop your XHTML efforts in favor of extending HTML 4 in more practical new ways that focused on rich web applications?
Mozilla and Opera proposed to the W3C: Would you please drop your XHTML efforts in favor of extending HTML 4 in more practical new ways that focused on rich web applications? No.
What the What?
What the What? Apple, Mozilla, and Opera start up the independent... WHATWG
What the What? Apple, Mozilla, and Opera start up the independent... WHATWG text App lication Web Hyper Group nology Working Tech
What the What? Apple, Mozilla, and Opera start up the independent... WHATWG text App lication Web Hyper Group nology Working Tech I gotta have more standards!
WHATWG Goals
WHATWG Goals Return the web to its open roots
WHATWG Goals Return the web to its open roots Bypass Flash, Silverlight, JavaFX
WHATWG Goals Return the web to its open roots Bypass Flash, Silverlight, JavaFX Modernize HTML
WHATWG Goals Return the web to its open roots Bypass Flash, Silverlight, JavaFX Modernize HTML Adapt the DOM, advance JavaScript
WHATWG Goals Return the web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML Adapt the DOM, advance JavaScript
WHATWG Goals Return the web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript
WHATWG Goals Return the web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript specs clear and unambiguous
WHATWG Goals Return the web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript specs clear and unambiguous Wa itaminute! Where is IE??
New WHATWG Proposal
New WHATWG Proposal W3C Accepts, forms the HTMLWG
New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML.
New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML. Yes. Another one.
New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML. Ok. Yes. Another But I’m in one. charge. Sure you are.
Who are the W3C?
Who are the W3C?
Who are the W3C? yeah, who are we?
W3C Credibility
W3C Credibility Membership
W3C Credibility Membership Decided by secret rules
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad Once called HTML "done" and moved on to XHTML2 (which nobody used)
W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad Once called HTML "done" and moved on to XHTML2 (which nobody used) Tried to make standards patentable
W3C Credibility - cont’d
W3C Credibility - cont’d W3C Says HTML5 Isn’t Ready for the Web
W3C Credibility - cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber 2 010 five at was go!! Th ths a m on
W3C Credibility - cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber Officials say Flash and Silverlight are still going to remain approved and viable web technologies. 2 010 five at was go!! Th ths a m on
W3C Credibility - cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber Officials say Flash and Silverlight are still going to remain approved and viable web technologies. 2 010 "There is a sense that the (W3C) is becoming a little too academic and out of the mainstream and their work too esoteric." five at was go!! Th ths a - Uttam Narsu, Giga Information Group Analyst m on
W3C - Problems?
W3C - Problems? Killing the golden goose?
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it!
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!)
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work The W3C’s antics does risk alienating the browser companies who have worked so hard to resuscitate HTML
W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work The W3C’s antics does risk alienating the browser companies who have worked so hard to resuscitate HTML
What do we do now?
What do we do now? ?? ?? ? ?
What do we do?
What do we do? Nothing.
What do we do? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime.
What do we do? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6)
What do we do? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec.
What do we do? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec. The feature is either there or it’s not.
What do we do? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec. The feature is either there or it’s not. Your client doesn’t know about this soap opera. Keep calling it HTML5.
HTML5 is still a viable marketing term.
HTML5 is still a viable marketing term. HTML5?? Give See that? You need some me six!! HTML5 right here.
Resources http://www.w3.org/News/2011.html#entry-9015 http://www.salsitasoft.com/blog/2010/12/08/the-trouble-with-web-standards-part-2- top-down-doesnt-work/ http://www.webmonkey.com/glossary/the-difference-between-the-whatwg-and-the- htmlwg/ http://en.wikipedia.org/wiki/World_Wide_Web_Consortium http://mashable.com/2010/10/07/w3c-stalls-html5/ http://wiki.whatwg.org/wiki/FAQ http://www.infoworld.com/d/application-development/whats-still-missing-in-the- html5-spec-314
The Fight Over HTML5

More Related Content

KEY
The Fight Over HTML5
byMike Wilcox
 
PDF
6 Principles for Enabling Build/Measure/Learn: Lean Engineering in Action
byBill Scott
 
PDF
How Frameworks Can Kill Your Projects at XP Days Ukraine 2013 in Kiev
bySander Hoogendoorn
 
PPT
01-a-Intro-BetterDev
byMarcio Marchini
 
PDF
FreshAir2008
bytutorialsruby
 
PDF
Do Try This At Home
bybdillard
 
PPTX
Wc3
byKevin Oswaldo Chavez Berrios
 
PDF
Pressbook FUTURS-EX (2016)
byPat Kebra
 
The Fight Over HTML5
byMike Wilcox
 
6 Principles for Enabling Build/Measure/Learn: Lean Engineering in Action
byBill Scott
 
How Frameworks Can Kill Your Projects at XP Days Ukraine 2013 in Kiev
bySander Hoogendoorn
 
01-a-Intro-BetterDev
byMarcio Marchini
 
FreshAir2008
bytutorialsruby
 
Do Try This At Home
bybdillard
 
Wc3
byKevin Oswaldo Chavez Berrios
 
Pressbook FUTURS-EX (2016)
byPat Kebra
 

Similar to The Fight Over HTML5

PPT
HTML 5
byProf. Erwin Globio
 
PDF
HTML5 Pearson preso
byChris Mills
 
PDF
The Future of the Web: HTML5
byDerek Bender
 
DOCX
Html5
byShivani Gautam
 
PPTX
Html5 and-css3-overview
byJacob Nelson
 
PPTX
Why Embrace "Html5"?
byFossilDesigns
 
KEY
Everything you need to know about HTML5 in 15 min
byEdgar Parada
 
KEY
Introduction to HTML5/CSS3 In Drupal 7
byMediacurrent
 
PDF
HTML5 Introduction – Features and Resources for HTML5
byTeam Mango Media Private Limited
 
PPT
html5 css3 the future of web technology
byhazzaz
 
PPTX
Developing with HTML5
byRay Wong
 
PDF
HTML5 and XHTML2
byMichael(tm) Smith
 
PPTX
HTML5: The next disruptive technology
byLinda Jacobson
 
PDF
HTML5, CSS3 and the Future of the Web
byBerg Brandt
 
DOCX
Html5
byShivani Gautam
 
PPTX
Application Development with HTML5 (Microsoft TechDays 2011 - DEV302)
byNathaniel Bagnell
 
PDF
Html5 Seminario Tid
byJosé Manuel Cantera Fonseca
 
PDF
HTML5 for the Flash Developer
byDevelopmentArc LLC
 
PDF
Html5 intro
byYnon Perek
 
PDF
HTML5: The New html for the web
byelliando dias
 
HTML 5
byProf. Erwin Globio
 
HTML5 Pearson preso
byChris Mills
 
The Future of the Web: HTML5
byDerek Bender
 
Html5
byShivani Gautam
 
Html5 and-css3-overview
byJacob Nelson
 
Why Embrace "Html5"?
byFossilDesigns
 
Everything you need to know about HTML5 in 15 min
byEdgar Parada
 
Introduction to HTML5/CSS3 In Drupal 7
byMediacurrent
 
HTML5 Introduction – Features and Resources for HTML5
byTeam Mango Media Private Limited
 
html5 css3 the future of web technology
byhazzaz
 
Developing with HTML5
byRay Wong
 
HTML5 and XHTML2
byMichael(tm) Smith
 
HTML5: The next disruptive technology
byLinda Jacobson
 
HTML5, CSS3 and the Future of the Web
byBerg Brandt
 
Html5
byShivani Gautam
 
Application Development with HTML5 (Microsoft TechDays 2011 - DEV302)
byNathaniel Bagnell
 
Html5 Seminario Tid
byJosé Manuel Cantera Fonseca
 
HTML5 for the Flash Developer
byDevelopmentArc LLC
 
Html5 intro
byYnon Perek
 
HTML5: The New html for the web
byelliando dias
 

More from Mike Wilcox

KEY
The History of HTML5
byMike Wilcox
 
PDF
WTF R PWAs?
byMike Wilcox
 
PDF
Webpack: What it is, What it does, Whether you need it
byMike Wilcox
 
KEY
The Great Semicolon Debate
byMike Wilcox
 
PPT
How to get a Job as a Front End Developer
byMike Wilcox
 
PDF
Advanced React
byMike Wilcox
 
KEY
Dojo & HTML5
byMike Wilcox
 
KEY
Why You Need a Front End Developer
byMike Wilcox
 
PDF
Accessibility for Fun and Profit
byMike Wilcox
 
PDF
Model View Madness
byMike Wilcox
 
PDF
Professional JavaScript: AntiPatterns
byMike Wilcox
 
KEY
Flash And Dom
byMike Wilcox
 
PDF
Great Responsive-ability Web Design
byMike Wilcox
 
PDF
Web Components v1
byMike Wilcox
 
KEY
Thats Not Flash?
byMike Wilcox
 
KEY
Webpage Design Basics for Non-Designers
byMike Wilcox
 
KEY
AMD - Why, What and How
byMike Wilcox
 
PDF
Dangerous CSS
byMike Wilcox
 
PDF
Hardcore JavaScript – Write it Right
byMike Wilcox
 
KEY
A Conversation About REST
byMike Wilcox
 
The History of HTML5
byMike Wilcox
 
WTF R PWAs?
byMike Wilcox
 
Webpack: What it is, What it does, Whether you need it
byMike Wilcox
 
The Great Semicolon Debate
byMike Wilcox
 
How to get a Job as a Front End Developer
byMike Wilcox
 
Advanced React
byMike Wilcox
 
Dojo & HTML5
byMike Wilcox
 
Why You Need a Front End Developer
byMike Wilcox
 
Accessibility for Fun and Profit
byMike Wilcox
 
Model View Madness
byMike Wilcox
 
Professional JavaScript: AntiPatterns
byMike Wilcox
 
Flash And Dom
byMike Wilcox
 
Great Responsive-ability Web Design
byMike Wilcox
 
Web Components v1
byMike Wilcox
 
Thats Not Flash?
byMike Wilcox
 
Webpage Design Basics for Non-Designers
byMike Wilcox
 
AMD - Why, What and How
byMike Wilcox
 
Dangerous CSS
byMike Wilcox
 
Hardcore JavaScript – Write it Right
byMike Wilcox
 
A Conversation About REST
byMike Wilcox
 

Recently uploaded

PPTX
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
byshyamraj55
 
PDF
Cheryl Hung, Vibe Coding Auth Without Melting Down! isaqb Software Architectu...
byCheryl Hung
 
PDF
[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...
byWintari Yasmin
 
PDF
[DevFest Strasbourg 2025] - NodeJs Can do that !!
bymoassiongbon
 
PDF
Accessibility & Inclusion: What Comes Next. Presentation of the Digital Acces...
byAssociazione Digital Days
 
PDF
Open Source Post-Quantum Cryptography - Matt Caswell
byAll Things Open
 
PDF
Lets Build a Serverless Function with Kiro
byChris Bingham
 
PDF
So You Want to Work at Google | DevFest Seattle 2025
byMargaret Maynard-Reid
 
PDF
Dev Dives: Build smarter agents with UiPath Agent Builder
byUiPathCommunity
 
PDF
Mastering UiPath Maestro – Session 2 – Building a Live Use Case - Session 2
byDianaGray10
 
PDF
[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...
byWintari Yasmin
 
PDF
Mastering Agentic Orchestration with UiPath Maestro | Hands on Workshop
byUiPathCommunity
 
PDF
Top Crypto Supers 15th Report November 2025
byStephen Perrenod
 
PPTX
Leon Brands - Intro to GPU Occlusion (Graphics Programming Conference 2024)
byleonbrands1998
 
PDF
The Necessity of Digital Forensics, the Digital Forensics Process & Laborator...
bychrstnpetwinchester
 
PDF
Transcript: The partnership effect: Libraries and publishers on collaborating...
byBookNet Canada
 
PPTX
kernel PPT (Explanation of Windows Kernal).pptx
byINFOBYTES1
 
PDF
Cybersecurity Prevention and Detection: Unit 2
byVICTOR MAESTRE RAMIREZ
 
PDF
"DISC as GPS for team leaders: how to lead a team from storming to performing...
byFwdays
 
PDF
How Much Does It Cost To Build Software
bycollinmishell2
 
The power of Slack and MuleSoft | Bangalore MuleSoft Meetup #60
byshyamraj55
 
Cheryl Hung, Vibe Coding Auth Without Melting Down! isaqb Software Architectu...
byCheryl Hung
 
[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...
byWintari Yasmin
 
[DevFest Strasbourg 2025] - NodeJs Can do that !!
bymoassiongbon
 
Accessibility & Inclusion: What Comes Next. Presentation of the Digital Acces...
byAssociazione Digital Days
 
Open Source Post-Quantum Cryptography - Matt Caswell
byAll Things Open
 
Lets Build a Serverless Function with Kiro
byChris Bingham
 
So You Want to Work at Google | DevFest Seattle 2025
byMargaret Maynard-Reid
 
Dev Dives: Build smarter agents with UiPath Agent Builder
byUiPathCommunity
 
Mastering UiPath Maestro – Session 2 – Building a Live Use Case - Session 2
byDianaGray10
 
[BDD 2025 - Artificial Intelligence] Building AI Systems That Users (and Comp...
byWintari Yasmin
 
Mastering Agentic Orchestration with UiPath Maestro | Hands on Workshop
byUiPathCommunity
 
Top Crypto Supers 15th Report November 2025
byStephen Perrenod
 
Leon Brands - Intro to GPU Occlusion (Graphics Programming Conference 2024)
byleonbrands1998
 
The Necessity of Digital Forensics, the Digital Forensics Process & Laborator...
bychrstnpetwinchester
 
Transcript: The partnership effect: Libraries and publishers on collaborating...
byBookNet Canada
 
kernel PPT (Explanation of Windows Kernal).pptx
byINFOBYTES1
 
Cybersecurity Prevention and Detection: Unit 2
byVICTOR MAESTRE RAMIREZ
 
"DISC as GPS for team leaders: how to lead a team from storming to performing...
byFwdays
 
How Much Does It Cost To Build Software
bycollinmishell2
 

The Fight Over HTML5

  • 1.
    The Fight OverHTML5 Are we to refer to it as HTML5 as the WC3 says or HTML as the WHATWG says? by Mike Wilcox March 2011
  • 2.
  • 3.
    January 17th, 2011 HTML5 Grows Up and Gets a Shiny New Logo
  • 4.
    January 17th, 2011 HTML5 Grows Up and Gets a Shiny New Logo
  • 5.
  • 6.
    New Logo! What’sGood It shows the W3C is actually paying some attention to what is going on outside of their little world.
  • 7.
    New Logo! What’sGood It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves.
  • 8.
    New Logo! What’sGood It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations.
  • 9.
    New Logo! What’sGood It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations. It comes with more logos!
  • 10.
    New Logo! What’sGood It shows the W3C is actually paying some attention to what is going on outside of their little world. W3C raises awareness for themselves. I can use the logo in my presentations. It comes with more logos!
  • 11.
  • 12.
    New Logo! What’sBad We need a logo? There's no logo for CSS, JavaScript, or XML.
  • 13.
    New Logo! What’sBad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves.
  • 14.
    New Logo! What’sBad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves. Flash doesn't even have a logo. The IDE does, but AS3 doesn't.
  • 15.
    New Logo! What’sBad We need a logo? There's no logo for CSS, JavaScript, or XML. W3C raises awareness for themselves. Flash doesn't even have a logo. The IDE does, but AS3 doesn't. Hey! Some of those sub-logos have nothing to do with HTML5!
  • 16.
  • 17.
    New Logo Bythe way, nobody asked me but...
  • 18.
    New Logo Bythe way, nobody asked me but... Designed by Occupop in Hawaii Price: $10 billion Time: 12 years
  • 19.
    New Logo Bythe way, nobody asked me but... Done by Mike Wilcox Designed by Occupop in Hawaii Price: $0.00 Time: 15 minutes Price: $10 billion Time: 12 years
  • 20.
  • 21.
    January 19th, 2011 The WHATWG announces that HTML5 will no longer exist.
  • 22.
    January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist.
  • 23.
    January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. HTML5
  • 24.
    January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH HTML5
  • 25.
    January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH The specification will be known as “HTML” HTML5
  • 26.
    January 19th, 2011 2 da ys later The WHATWG announces that HTML5 will no longer exist. ick son Ia nH The specification will be known as “HTML” No more deadlines. It will be a LIVING SPEC. HTML5
  • 27.
  • 28.
  • 29.
    Versionitus Outrage ensues. Can we still use the term HTML5?
  • 30.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never!
  • 31.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!!
  • 32.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target?
  • 33.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5?
  • 34.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess!
  • 35.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess! If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future.
  • 36.
    Versionitus Outrage ensues. Can we still use the term HTML5? 2022 was bad enough, now it’s never! If the spec is never finalized we can never use it!! How will browsers ever implement a moving target? When will it ever be safe to use HTML5? HTML will become an unusable mess! If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future. Someone really said that on th WHATWG blog e
  • 37.
  • 38.
  • 39.
    The W3C Backtrack " This is no t the offic ial logo ye t"
  • 40.
    The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 specification? A: !No, not all of them.
  • 41.
    The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 W3C w ill cont inue to use specification? "Open Web Platform" as A: !No, not all of them. well [as HTML5], an d we may have a corresponding logo.
  • 42.
    The W3C Backtrack " This is no t the offic ial logo ye t" FAQ: Q:! Are a ll those technology features de fine d in the HTML5 W3C w ill cont inue to use specification? "Open Web Platform" as A: !No, not all of them. well [as HTML5], an d we may have a corresponding logo. Ian Jacobs Head of W3C Marketing and Communications
  • 44.
  • 45.
  • 46.
    February 14, 2011 28 d ays later
  • 47.
    February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014.
  • 48.
    February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Okay. It’s DONE.
  • 49.
    February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Developers, it’s safe to use it Okay. It’s now. DONE.
  • 50.
    February 14, 2011 28 d ays later The W3C announces that HTML5 will be done in 2014. Developers, it’s safe to use it Okay. It’s now. DONE. Last Call: MAY!!?!
  • 51.
  • 52.
    Developers Rejoice! ...or do they?
  • 53.
  • 54.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut.
  • 55.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec
  • 56.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking
  • 57.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources
  • 58.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources
  • 59.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT)
  • 60.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D
  • 61.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D WebSockets
  • 62.
    What’s Missing Becauseof the aggressive timeline, some things may not make the cut. Standard video codec Multitracking Multiple video sources Multiple audio sources External Closed Caption XML file (SRT) Canvas 2D extensions, Canvas 3D WebSockets The W3C originally said HTML5 would be done in 2010. I’m just sayin’.
  • 63.
    The W3C orthe WHATWG?
  • 64.
    The W3C orthe WHATWG?
  • 65.
    Who are theWHATWG?
  • 66.
    Who are theWHATWG? yeah, who am I?
  • 67.
    Mozilla and Operaproposed to the W3C:
  • 68.
    Mozilla and Operaproposed to the W3C: Would you please drop your XHTML efforts in favor of extending HTML 4 in more practical new ways that focused on rich web applications?
  • 69.
    Mozilla and Operaproposed to the W3C: Would you please drop your XHTML efforts in favor of extending HTML 4 in more practical new ways that focused on rich web applications? No.
  • 70.
  • 71.
    What the What? Apple, Mozilla, and Opera start up the independent... WHATWG
  • 72.
    What the What? Apple, Mozilla, and Opera start up the independent... WHATWG text App lication Web Hyper Group nology Working Tech
  • 73.
    What the What? Apple, Mozilla, and Opera start up the independent... WHATWG text App lication Web Hyper Group nology Working Tech I gotta have more standards!
  • 74.
  • 75.
    WHATWG Goals Returnthe web to its open roots
  • 76.
    WHATWG Goals Returnthe web to its open roots Bypass Flash, Silverlight, JavaFX
  • 77.
    WHATWG Goals Returnthe web to its open roots Bypass Flash, Silverlight, JavaFX Modernize HTML
  • 78.
    WHATWG Goals Returnthe web to its open roots Bypass Flash, Silverlight, JavaFX Modernize HTML Adapt the DOM, advance JavaScript
  • 79.
    WHATWG Goals Returnthe web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML Adapt the DOM, advance JavaScript
  • 80.
    WHATWG Goals Returnthe web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript
  • 81.
    WHATWG Goals Returnthe web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript specs clear and unambiguous
  • 82.
    WHATWG Goals Returnthe web to its open roots backward Bypass Flash, Silverlight, JavaFX compatibility Modernize HTML specs match implementation Adapt the DOM, advance JavaScript specs clear and unambiguous Wa itaminute! Where is IE??
  • 83.
  • 84.
    New WHATWG Proposal W3C Accepts, forms the HTMLWG
  • 85.
    New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML.
  • 86.
    New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML. Yes. Another one.
  • 87.
    New WHATWG Proposal W3C Accepts, forms the HTMLWG Drops XHTML. Ok. Yes. Another But I’m in one. charge. Sure you are.
  • 88.
  • 89.
  • 90.
    Who are theW3C? yeah, who are we?
  • 91.
  • 92.
    W3C Credibility Membership
  • 93.
    W3C Credibility Membership Decided by secret rules
  • 94.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees
  • 95.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies
  • 96.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies
  • 97.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad
  • 98.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad Once called HTML "done" and moved on to XHTML2 (which nobody used)
  • 99.
    W3C Credibility Membership Decided by secret rules Is pay-for-play; requires fees Mostly large companies Listens only to large companies ...yet manages to make them all mad Once called HTML "done" and moved on to XHTML2 (which nobody used) Tried to make standards patentable
  • 100.
  • 101.
    W3C Credibility -cont’d W3C Says HTML5 Isn’t Ready for the Web
  • 102.
    W3C Credibility -cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber 2 010 five at was go!! Th ths a m on
  • 103.
    W3C Credibility -cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber Officials say Flash and Silverlight are still going to remain approved and viable web technologies. 2 010 five at was go!! Th ths a m on
  • 104.
    W3C Credibility -cont’d W3C Says HTML5 Isn’t Ready for the Web O cto ber Officials say Flash and Silverlight are still going to remain approved and viable web technologies. 2 010 "There is a sense that the (W3C) is becoming a little too academic and out of the mainstream and their work too esoteric." five at was go!! Th ths a - Uttam Narsu, Giga Information Group Analyst m on
  • 105.
  • 106.
    W3C - Problems? Killing the golden goose?
  • 107.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work
  • 108.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted
  • 109.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it!
  • 110.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death
  • 111.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!)
  • 112.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work
  • 113.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work The W3C’s antics does risk alienating the browser companies who have worked so hard to resuscitate HTML
  • 114.
    W3C - Problems? Killing the golden goose? WHATWG has done the lion’s share of the work XML History is sorted They almost killed that too. Google it! Loving HTML5 to death (cute logo guys!) Top down standards writing doesn't work The W3C’s antics does risk alienating the browser companies who have worked so hard to resuscitate HTML
  • 115.
    What do wedo now?
  • 116.
    What do wedo now? ?? ?? ? ?
  • 117.
  • 118.
    What do wedo? Nothing.
  • 119.
    What do wedo? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime.
  • 120.
    What do wedo? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6)
  • 121.
    What do wedo? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec.
  • 122.
    What do wedo? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec. The feature is either there or it’s not.
  • 123.
    What do wedo? Nothing. WHATWG’s “living standards” will get rolled into W3C’s versioned spec... somewhere. sometime. Features that don’t make it into HTML5 will go into HTML.next (I’m guessing that will be HTML6) User Agents are the ones innovating. Those innovations are added to the browser and then to the spec. The feature is either there or it’s not. Your client doesn’t know about this soap opera. Keep calling it HTML5.
  • 124.
    HTML5 is stilla viable marketing term.
  • 125.
    HTML5 is stilla viable marketing term. HTML5?? Give See that? You need some me six!! HTML5 right here.
  • 126.
    Resources http://www.w3.org/News/2011.html#entry-9015 http://www.salsitasoft.com/blog/2010/12/08/the-trouble-with-web-standards-part-2- top-down-doesnt-work/ http://www.webmonkey.com/glossary/the-difference-between-the-whatwg-and-the- htmlwg/ http://en.wikipedia.org/wiki/World_Wide_Web_Consortium http://mashable.com/2010/10/07/w3c-stalls-html5/ http://wiki.whatwg.org/wiki/FAQ http://www.infoworld.com/d/application-development/whats-still-missing-in-the- html5-spec-314

Editor's Notes