Don’t call me DOM

As of this month, my time allocation is moving from half-QA/half-Systems Team to half-Mobile Web Initiative (also known as MWI)/half-Systems Team.

While I have a certain sadness to leave the work on QA after having been involved in it for the past three years, it’s good to leave it with a set of very satisfying results: the Specification Guidelines were published as a W3C Recommendation a few weeks ago, the Working Group - while its charter is not going to be renewed - is on track to continue its most important work items through the Interest Group, after a truly excellent face-to-face meeting in Dublin; among them, work has started on formalizing the group experience on test case metadata which should hopefully be published as a note in the upcoming weeks.

I was kindly notified that my RSS feed was ill-formed for the past few days, because of an — entity in one of my previous posts. While I have fixed manually the issue, I was asked in return why this entity made my feed invalid. I’m taking this question as an opportunity to start a new category on tutorials about markup languages; it may end up being only one article only, but I’m interested in getting more questions for this category if people find it useful (let me know through comments or mail).

The Web is a formidable tool to host documentation; nothing new about that.

But documentation, be it on the Web or not, tend to rot when not maintained. Nothing new about that either.

While documentation maintenance is probably better addressed at the social-engineering level, there are tools that can help manage it; namely, a few weeks ago, W3C Systems Team went through the process of cleaning up our internal documentation on processes, tools, services, configurations, etc. that sits on our Team-only Web site, but is too rarely kept up to date with the latest developments.