Is Mozilla on the Bridge of Khazad - or on the Fence?

Last week I explored at some length the curious reasons that Sir Tim Berners-Lee gave for supporting the proposal to add hooks for DRM into HTML5. 

On Open Enterprise blog.

Tim Berners-Lee on Why HTML5 "Needs" DRM

A couple of week ago, I discussed the awful idea of adding DRM to the official HTML5 standard, and where that would lead us. More recently, Tim Berners-Lee wrote a piece about openness that included the following comment:

On Open Enterprise blog.

DRM In HTML5: What Is Tim Berners-Lee Thinking?

Back in January, we reported on a truly stupid idea: making DRM an official aspect of HTML5. Things then went quiet, until a couple of weeks ago a post on a W3C mailing announced that the work was "in scope". An excellent post on the EFF's blog explains: 

On Techdirt.

BBC Attacks the Open Web, GNU/Linux in Danger

The Web is one of the most dramatic demonstrations of the power of openness, alongside free software, which not coincidentally runs most of it and the rest of the Internet. At the heart of that openness lies HTML, a completely open way of sharing information. So what would be a really stupid thing you could do to try to throttle that openness and innovation? Why, yes: adding DRM to HTML so that you can lock down Web page elements:

On Open Enterprise blog.

Truly Stupid Ideas: Adding DRM To HTML5

You would have thought by now that people would understand that DRM is not only a bad idea, but totally unnecessary: Apple dropped DRM from music downloads in 2009 and seems to be making ends meet. Despite these obvious truths, the stupidity that is DRM continues to spread. Here, for example, is a particularly stupid example of DRM stupidity, as revealed by Manu Sporny: 

On Techdirt.

Let My Codecs Go: Will Google Free VP8?

I've written about the growing interest in HTML 5 a couple of times, and there is a parallel discussion around the role, if any, of Flash and its proprietary codecs in an Open Web. And now, hidden away in this dull press release from Google, we have another ingredient added to the bubbling cauldron...

On Open Enterprise blog.

Visualising Open Data

One of the heartening trends in openness recently has been the increasing, if belated, release of non-personal government data around the world. Even the UK is waking up to the fact that transparency is not just good democracy, but is good economics too, since it can stimulate all kinds of innovation based on mashups of the underlying data.

That's the good news. The bad news is that the more such data we have, the harder it is to understand what it means. Fortunately, there is a well-developed branch of computing that tries to deal with this problem: visualisation. That is, turning the reams of ungraspable numbers into striking images that can be taken in at a glance.

Of course, the problem here is that someone has to spend time and effort taking the numbers and turning them into useful visualisations. Enter the Open Knowledge Foundation, which today launches the self-explanatory site “Where Does My Money Go? - analysing and Visualising UK Public Spending” (disclaimer: I have recently joined the OKFN's Advisory Board, but had nothing to do with this latest project.)

Here's what the press release has to say about the new site:

Now more than ever, UK taxpayers will be wondering where public funds are being spent - not least because of the long shadow cast by the financial crisis and last week’s announcements of an estimated £850 billion price tag for bailing out UK banks. Yesterday’s pre-budget report also raises questions about spending cutbacks and how public money is being allocated across different key areas.

However, closing the loop between ordinary citizens and the paper-trail of government receipts is no mean feat. Relevant documents and datasets are scattered around numerous government websites - and, once located, spending figures often require background knowledge to interpret and can be hard put into context. In the UK there is no equivalent to the US Federal Funding Accountability and Transparency Act, which requires official bodies to publish figures on spending in a single place. There were proposals for similar legislation in 2007, but these were never approved.

On Friday 11th December the Open Knowledge Foundation will launch a free interactive online tool for showing where UK public spending goes. The Where Does My Money Go? project allows the public to explore data on UK public spending over the past 6 years in an intuitive way using an array of maps, timelines and graphs. By means of the tool, anyone can make sense of information on public spending in ways which were not previously possible.

There's currently a prototype, and a list of the datasets currently analysed available as a Google Docs spreadsheet. There are some really cool interactive visualisations, but I can't point you to any of them because they are hidden within a Flash-based black box – one of the big problems with this benighted technology. Once HTML5 is finalised it will presumably be possible to move everything to this open format, which would be rather more appropriate for a site dedicated to open data.

That notwithstanding, it's great to see the flood of information being tamed in this way; I hope it's the forerunner of many more like it (other than its dependence on Flash, of course) as governments around the world continue to release more of their data hoards. Meanwhile, do take it for a spin and pass on any suggestions you have that might improve it.

Follow me @glynmoody on Twitter or identi.ca.

You Know You're Getting Old When...

...you don't recognise half the things these young chaps are talking about...

On Open Enterprise blog.

Now We Are (HTML) 5

Remember HTML? It's (nearly) back:

This specification introduces features to HTML and the DOM that ease the authoring of Web-based applications. Additions include the context menus, a direct-mode graphics canvas, inline popup windows, and server-sent events.

(Via Heise Online.)

Now We Are Five: HTML5, XHTML5

Anything that talks about HTML5 and XHTML5 gets my attention pretty quickly. I don't pretend to understand all the implications of this, but it sounds cool:

This specification introduces features to HTML and the DOM that ease the authoring of Web-based applications. Additions include the context menus, a direct-mode graphics canvas, inline popup windows, and server-sent events.

...


The scope of this specification is not to describe an entire operating system. In particular, hardware configuration software, image manipulation tools, and applications that users would be expected to use with high-end workstations on a daily basis are out of scope. In terms of applications, this specification is targetted specifically at applications that would be expected to be used by users on an occasional basis, or regularly but from disparate locations, with low CPU requirements. For instance online purchasing systems, searching systems, games (especially multiplayer online games), public telephone books or address books, communications software (e-mail clients, instant messaging clients, discussion software), document editing software, etc.

I can't wait. (Via Vecosys.)