XKCD recently published the future and found through a good number of Google searches that finishing up HTML5 would herald the demise of newspapers and the Third Coming of Christ.

Coincidentally the W3C declared that finally CSS 2.1 had reached Proposed Recommendation status, and surely, surely!, the end, in the form of CSS 2.1 as Recommendation, should be nigh [Note from the future: it became one later same year]. I recapped the story in an almost four year earlier entry, Cruelly Slow Slog, a slog that cruelly continued for four more years. 11 years of labour is not bad for what was intended as a quick fix.

Urban planning and city architecture has traditionally been a closed process between the client and the planner, possibly with a public hearing (too) late in the process.

We are now at a stage technically, and sometimes socially, that this process could be organised differently. It could be more like the process for producing the HTML5 standard for instance, with early prototyping, public involvement with the stakeholders, scenarios and visualisations, and a transparent process.

Any area potentially under development could be put on Google maps, or local equivalents, as well as on a time line for any interested citizen to see or get involved with.

I am interested to know: What “prior art” do you know of in architecture along these lines, how was it done, what were the consequences and lessons?

Many of the developments in the 10 and 11 versions of Opera are important, but personally my key word for these upgrade would be “disappointment”. There is one feature/bug fix which would make a huge difference in my browser use, not when things works smoothly, but be a life saver when they don’t, fixing bug 155102. For such an important bug it has taken its time fixing. It was still there in Opera 9, when finally there was an interest in fixing it, it was still there in Opera 10, and it is still there in Opera 11.

"How unique – and trackable – is your browser?"

This is well and nice, but there is a problem. These configuration details don't usually change very often and there are so many combinations of these configurations that it is possible, even probable, that your personal settings may be globally unique. In other words nobody else will have the settings that your browser has, even if you haven't personalised it. In the words of this site, your browser will have a fingerprint. Where ever it is used it can be identified. …

(more…)

Today at 十/十/十 十:十:十 in your zone is the third last factino second this century.

When you have “dinner at seven” it would be dinner at seven tonight unless that time has already passed, then it would be dinner at seven tomorrow night. If it were “breakfast at seven” then it would be tomorrow morning as most of us have breakfast in the morning and dinner in the evening. The way we specify dates is highly contextual and highly cultural, so artificial or natural intelligence will have a hard time figuring out what time it really is. …

HTML5 allows you to specify that when it matter, so that when the HTML processor encounters “7/11” the markup will tell if you if the fraction 0.6363.. was meant, a date (and which one), a convenience chain, or something else. The time-related capabilities are limited, but HTML5 can give you the time of day. In other cases you need to go beyond HTML5. If you need to establish “7/11” as your friend’s birthday, as opposed to day of birth, you need to use some calendar extension, as you would if a vague time is needed, like “during next week”.

The water wagon, a public house that only sells water.

The Norwegian Prime Minister, having been grounded in New York by Icelandic eruptions, did the natural thing for a politician in a modern democracy. He called in the press.

There has been a lot of talk about HTML5 video, codecs, containers, and the lot. That certainly matters, but it isn’t something I care about. Assuming the browsers could agree on some standard media codec plug-in interface, like they have done before, browsers shouldn’t be different from any other media player like VLC. That way it wouldn’t be a major work to update the browsers and the spec itself to new formats. Problem solved. …

The licensing problem wouldn’t go away, but it would be moved from the domain of the browsers (or other media players). If a royalty-free codec like Theora were shown to be torpedoed by one of those media patents, and we had to use some Plan TheorB it would be a matter of discovering how to evade the patent in question and distribute the new patent-proof plug-in, instead of involving a number of browser upgrade cycles. It also moves the patent risk from the browser companies, which are huge lawsuit targets like Microsoft, Google, and Apple, and smaller ones like Opera and Mozilla, to the plug-in developers that would be so small and fleet as not to be a viable target.

I care about a much simpler issue, subtitles, those little blocks of text that put movies into writing. For all the controversy of the video element, the design goals have pretty modest, essentially recreating YouTube without using Flash. But HTML5 doesn’t “natively” support YouTube’s captions, annotations, and subtitles. Of course it doesn’t have to, anything you can do, you can do with JavaScript. However it would be a missed opportunity.

Why care about subtitles?

Subtitles are not that popular in mostly monolingual countries like USA with a tradition of dubbing foreign videos, they can be considered an aquired taste. They are still superior to dubbing, and crucially subtitles are more adapted to the Internet age, and they are searchable and accessible as well.