Don’t call me DOM

As a follow-up on my toying with DTDs, I added a new Python script to my toolbox this morning: dtd-compare.py allows to compare the vocabularies defined in several DTDs to see which elements and attributes are present or absent among them.

For instance, running python dtd-compare.py http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd http://www.openmobilealliance.org/tech/DTD/xhtml-mobile10.dtd http://www.w3.org/TR/xhtml-basic/xhtml-basic11.dtd http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd has allowed me to build a comparison of the various mobile XHTML flavors with the content of XHTML 1.0 Strict.

I haven’t included XHTML MP 1.1 and XHTML MP 1.2 in that comparison chart since the officlal DTDs seems to have syntax errors, reported by the script as follows:

My daily work schizophrenia makes me half Mobile Web Initiative Activity Lead, half a developer in the W3C Systems Team (a.k.a. “Systeam”).

The first half of my self has started blogging in the MWI Team Blog a while ago - and I’m now trying to make sure to import these blog posts in this very blog as well -, and my second half has now also a new blog output available: the Systeam blog opened yesterday, and I’m hoping my colleagues and I will feed it regularly with the various hacks, open source contributions, and practical advices that we come up with.

To celebrate the progress of GRDDL towards its final stage, and to replace the aging and somewhat unreliable XSLT-based GRDDL demonstrator, I’ve just released a brand new W3C GRDDL service.

It simply takes a Web page and extracts the RDF statements it can find in there using GRDDL.

I have made its source code available on W3C Public CVS server, but the gist the work is done by the underlying library, python-librdf, the Python binding for Redland. Particular thanks to Dave Beckett who provided amazing user support to help setting this up!