Understanding HTML's Semantic Elements

I want to introduce you to some new tags, and I want them to be properly defined by the people who define the standard so that we can understand not how we think they should be used, but we can learn how they should be used based on the original intentions.

We need to go back to the people who define the standard, and there are actually two groups that you might find defining the standard, and I want you to understand which one is the correct one that we're going to reference. So let's go back to before web standards were created.

Back then there were browsers like Netscape and internet Explorer and Microsoft—they could decide to implement whatever code they wanted, and it didn't have to work in other browsers, so websites were being made for Netscape or made for internet Explorer and we didn't have a universal web where websites worked in all browsers. Then this idea of standards was created and the W3C was formed, the World Wide Web Consortium, and they defined a standard and browsers now try to achieve a standard so that we can write one set of code that works universally across most browsers, assuming that they're following the standard.

So as years went on, the iPhone was coming out and we were thinking about the mobile web for the first time, and during that time the W3C was focused on their own priorities. They were thinking about creating the next version of HTML called XHTML 2, combining XML and HTML so it could be more flexible and you could define whatever tags you wanted, but they were doing things that the industry didn't really need or want, and XHTML 2 was going to break backward compatibility with the web, which just wasn't going to be good for the industry moving forward.

---

So at that time Apple was focused on the iPhone, and this was prior to the App Store coming out, so there were no native apps. They wanted to let people create apps and thought, well, let's create web apps, and so the Web Hypertext Application Technology Working Group was created by Apple, Mozilla, and Opera, who at that time was making its own browser and its own browser rendering engine.

Think about web apps, right? HTML is the Hypertext Markup Language, and hypertext web apps were basically just HTML as a web app. There were no video or audio tags during that time. Everybody was using plugins—things like Flash to view videos or listen to audio—but plugins didn't work on the iPhone. So the idea was to move the standard forward in a way that works without plugins.

So this technology working group was focused on the next version of HTML, not splintering off and creating XHTML as a different flavor of the language. They were creating what would eventually become known as HTML5. Eventually they said, let's not version-number these things; let's just call it the living standard. Today, it's simply called the living standard; it's not one specific version number.

---

As long as we follow the latest version of this, we're always getting the latest and greatest innovations as soon as browsers get updated and the standards get pushed out. Apple, Google, Mozilla, and Microsoft—basically the people who make the browsers—are the ones behind this, and they have essentially taken over the standards. So it's no longer the W3C that we look at for those standards; we now look to the Web Hypertext Application Technology Working Group.

That is a mouthful of a name—it's a long name—but they define the living standard. Essentially they make the browsers, so of course they define the standard. We don't call it HTML5 anymore; we just call it the latest, greatest version of HTML, called the living standard.