The academic community has been working on this idea for some time, calling it the "semantic Web." Some suggest that these basic tags don't begin to approach the complexity needed for supersmart Web bots to do supersmart things. Others say that we need to start somewhere and the tag soup from the Microdata API will make it easier for browsers to do intelligent things.
Most browsers don't implement this yet, and it's even less clear what it means for website developers to implement the API. It's one thing to parse the tags correctly and put entries in the DOM tree. It's another to actually do something with them. It would be nice, for instance, to recognize the
time tags and connect somehow with a local or global calendar, but even that simple response is beyond the API.
Any discussion of the HTML Microdata API doesn't fit perfectly with this section because it's not devoted to local storage of data. In fact, most of the tags don't seem to have much to do with the average person's Web browser. They may be more for the sake of some distant search engine buried deep inside a remote colo bunker. Or they might end up being used extensively by the next browsers and their plug-ins. It's all very open-ended.
Bottling the Web
There is no conclusion to this section of APIs. We're not even far into the beginning of the beginning of what local persistence will do to the Web. There are many, many edge conditions to work out regarding who gets access to the data, how much data will be stored, and how long the data will live.
Apart from the
localStorage objects, which all of the current leading browsers (Chrome, Firefox, Internet Explorer, Opera, and Safari) implement to some extent, browser support for the other APIs discussed here is sketchy. Only Chrome and Firefox implement the
FileReader API. Although all but Internet Explorer (IE9 beta included) support
AppCaching, none support the
FileWriter functions. Test your own browser's support for these functions at http://www.wayner.org/node/75.
This is just the beginning of a lengthy series of decisions that browser designers will need to make. Then the users can determine what features they absolutely need, and the privacy and flexibility they require, to use the Web effectively. The answers to these questions are a long way in the future.
Note: This is the second article in a series devoted to the new features of HTML5. The first article, "HTML5 in the browser: Canvas, video, audio, and graphics," examined display options, including the
<video> tags, Scalable Vector Graphics, and WebGL. The third article will examine data communications and the fourth will look at a grab bag of tools such as geolocation.
This story, "HTML5 in the browser: Local data storage," was originally published at InfoWorld.com. Follow the latest news in software development, languages and standards, and HTML at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.
You may still be better off sticking with Win7 or Win8.1, given the wide range of ongoing Win10...
Now that we're down to the wire, many upgraders report that the installer hangs. If this happens to...
Based on a technique created by a German blogger, here's how to stop wasting hours checking for Windows...
Everyone benefits from Network Time Protocol, but the project struggles to pay its sole maintainer or...
We reviewed a lot of gadgets and services in 2016, and here are our top 12 recommendations for tech...
The kit helps developers build apps that boot as OSes and are less dependent on hardware
Were it not for an alert customer, attackers could have compromised every RHEL instance on Microsoft...