Home > Articles > Web Development > HTML/CSS

XHTML 2 vs. HTML5: A Tale of Two World Wide Webs

  • Print
  • + Share This
David Chisnall looks at the two competing philosophies currently driving the World Wide Web, as presented by the Web Hypertext Application Technology Working Group (WHATWG) and the World Wide Web Consortium (W3C), and contrasts their goals and utility.
Like this article? We recommend

Over the last decade, there have been two competing visions for the World Wide Web. These visions have recently become embodied in two different standards groups: the Web Hypertext Application Technology Working Group (WHATWG) and the World Wide Web Consortium (W3C) and by their relative proposals: XHTML 2 and HTML5.

The interesting thing about these two is not the minor syntactic differences between the two; it's the widely different problems that they are trying to address with very similar technology. Both have an idea of how the web should be, and their respective standards describe tools for implementing that web.

It's the Apps, Stupid!

The WHATWG vision is for web applications. Interestingly, WHATWG was largely led by Apple in its early days. One of the most popular parts of the HTML5 specification, for example, is basically a set of JavaScript bindings to Apple's CoreGraphics APIs.

Pushing web applications was a strategic move for Apple because it was the underdog in the desktop computing market, and web applications made it easier for people to switch to Mac OS X from Windows—they could just run the same software.

When the original iPhone was launched, the WHATWG technologies were the only official development environment. They provided accelerated 2D graphics with a rich PostScript-style model including antialiased beziers and composited raster graphics, audio and video playback, and even local storage. These were later largely downplayed in favor of native development.

The shift toward native applications is also easy to understand. Apple had a large early install base, so no longer had the underdog's incentive to make switching easy. Applications work just as well for lock-in on mobile devices as they do on desktops, and if all iPhone applications were web applications then it was very easy to switch to a competitor's model.

The Semantic Vision

The competing vision, championed by Sir Tim Berners-Lee and the W3C, was the semantic web. In this model, web pages and web services are the primary components of the web.

A web page contains semantic markup, allowing it to be parsed by a variety of tools and displayed in a range of ways. Web services provide information in XML that clients can process and interpret.

The core idea in this model is the separation of content from presentation. Servers provide data and services, but they don't (necessarily) dictate how they are displayed to clients. This alleviates some of the burden from the owner of the site because they are less responsible for ensuring that it displays nicely on a small-screen device or a Braille reader. Custom viewers for these devices are easy to write.

A Simple Example

For the two models, consider trying to book a journey. This involves finding hotels and organizing various forms of transport.

If you're flying, you may take trains to the station or possibly buses. You want to be able to find the shortest time and the cheapest transport, and compare the options. In the web applications model, each transport company will have a web application that lets you view their timetables. These are inconvenient to use when they are just one part of a journey, so you'll typically use an intermediary, which will let you compare various trips. It will present its own web application and will handle bookings for you.

In the semantic web vision, each transport company would provide a page containing their timetables and a web service for booking. They'd probably provide some default style sheet that would let you navigate this in a generic web browser, but you could also use a custom travel application that would collect information from all of the sources and provide cost and time calculations.

More importantly, the second approach implicitly encourages competition. If the data is available in an easy-to-use form, then it's relatively easy for anyone to build an interface to it. The barrier to entry is much lower.

Search and Advertising

In the last couple of years, we've seen a lot of popular web sites releasing mobile applications for Android and iOS. They are motivated by largely the same requirements as the semantic web model: that of needing a custom user interface for certain uses. A lot of them, however, implement their own custom protocols and explicitly make it difficult for a third party to provide a replacement.

This seems odd because a web site ought to have a vested interest in ensuring that its users can access its content easily, and allowing third-party tools to access it should encourage this.

Unfortunately, the problem is advertising. We're currently near the tail end of an Internet advertising bubble, and the main way of funding a web site is via advertising. Sometimes this is quite direct. You can probably see advertisements for some of my books on one side of this article: InformIT exists to try to persuade you that people who write books for Pearson write things worth buying, in the hope that next time you want to learn about some technology, one of these books will be your first choice. More commonly, however, advertising is provided by third parties.

If this article is reprinted elsewhere, but with attribution left intact, and people read it and think, "David Chisnall's a hoopy frood who really knows where his towel is; I'd better buy one of his books," then that's great. If a site depended on revenue from clicking on advertising, however, then putting it in a form where it's easy (and gives a better user experience) if you strip off the advertisements is not in their best interests.

Unfortunately, in the absence of micropayments, there really isn't a good revenue model for the semantic web, at least for sites that make money from their content.

This isn't universally the case: A lot of sites make money from disseminating their information. In the earlier example, a train company makes money from people travelling on their trains. If people know when their trains are running, then they're more likely to do so.

Oddly enough, a lot of companies fail to realize this. TV listings are a good example. These are often jealously guarded as if they are trade secrets and sold to a small number of companies for publication. Yet the TV stations make money by selling advertising, their advertising revenue is based on viewership figures, and their viewership is dependent on people (or, at least, DVRs) knowing when their shows are on.

A Hybrid World

Although I've portrayed these two visions as mutually exclusive, they don't have to be. There's no reason why you can't provide both: a web service presenting data in an easy machine-parseable form and a web application as the default front end. This may seem like a lot of extra work, but a good application—web or otherwise—is likely to employ a model-view-controller design. The web service encapsulates the model, and the web application encapsulates the controller and view.

A well-designed application using this model is also easy to turn into a mobile application. If all the back-end services are exposed as web services, it's easy to use off-the-shelf libraries for all the mobile (and, indeed, desktop) platforms to talk to it. You then need to write only the user interface and not worry about implementing yet another way of communicating with it.

Perhaps more importantly, other people can do this for you. If you provide some valuable service and document your APIs, then you can expect to see your users write applications for integrating with it. In some cases, even if you don't provide a sensible interface, then users will do this via screen scraping.

There was a case a while ago in the UK of an application developer being asked to remove an application that was getting train times from the operator's web site because it violated some terms and conditions. Apparently the web site owners forgot that the entire point of the site is to make it easier for people to get on their trains, the thing that actually makes money for their company.

A Case Study in Failure

The canonical example of how to entirely miss the point of the World Wide Web is the BBC iPlayer. The BBC charter requires it to provide entertaining and educational content to the widest possible audience in the UK. It tries to fulfill this requirement on the web via its iPlayer interface.

Now, if you were designing this sort of site with these goals in mind, you might think that the obvious thing to do would be provide RSS or Atom feeds of programs, with the URLs to download each one in a variety of different resolutions, and then wrap this in some web interface using either HTML5 or Flash, depending on the web browser's capabilities.

Unfortunately, their entire infrastructure is based on Flash. When Adobe killed Flash on recent versions of Android, the BBC suddenly realized that it had a problem and ported its infrastructure to a more sensible design. Well, something like that. The BBC actually asked Google and Adobe to put Flash back in the Google Play store for the UK.

If the BBC had provided an open set of APIs, then this would almost certainly not have been a problem. The Apple App Store and Google Play would already have numerous third-party apps for displaying iPlayer content, and it would be able to just list them and tell people who wanted to use its service without Flash to use one.

Why do I feel so confident to say this? Because even without a public documented API, there are already two third-party applications for downloading iPlayer content, plus a few GUI front ends.

Remember this lesson when you're designing a web site to provide information. There are sometimes commercial pressures to ensure that people use your interface, but make sure that these are actually aligned with your business objectives (and other buzzwords) before you give in to them.

If your service depends on advertising revenue, then it may be important to force access to go via your portal (although you may find that most of your customers just run ad blocking plugins, anyway).

If it isn't, and it exists to provide information that people can use to allow them to give you money, then think about presenting it not just in the best way that you can think of but also in a way that makes it easy for other people to expose it in ways that you haven't thought of.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020