This week I participated in some very interesting discussions during the Document Interoperability Initiative event held in London. One of these discussions was related to conformance testing. Obviously, the world of documents is moving forward and one of the important processes going on is the continuous improvement of standards. But standards by themselves are not enough.
It turns out that when one talks about conformance testing in the world of documents there are at least two issues to talk about. The first one is document conformance testing and it’s the easier one (nota bene, I’m saying easier not easy). It is all about the conformance of a particular document to a published standard. When it comes to OOXML, the standard is ISO/IEC 29500 with its four parts:
Who’s in charge of the standard? Well… that’s a more complicated question. The International Standards Organization (ISO) and the International Electrotechnical Commission (IEC) are running a collaborative effort named Joint Technical Committee 1 (JTC1) whose members are National Bodies (42 participating members and 44 observers). All in all, there are about 2100 technical experts from around the world that work with JTC1. Among the subcommittees of JTC1, there is one named SC34 – Document Description and Processing Languages which is in charge, among many other things with the ISO/IEC 29500 standard. SC34 has 5 Working Groups:
- WG1 – Information description
- WG2 – Information presentation
- WG3 – Information association
- WG4 – Office Open XML
- WG5 – Document interoperability
As you might notice, despite the fact that the documents and the bodies governing them are quite complex (remember, it’s the easier side of conformance, not the easy one :) ), testing document conformance is pretty much an exact science.
The second aspect of conformance testing, is unfortunately a bit more fuzzy. I’m talking here about application conformance testing. This one is supposed to test whether an application that works with certain types of documents does what it is supposed to do. Because we’re talking here mainly about user interaction, testing for conformance is much more complicated. Think about the simplest example possible: is the application displaying italic fonts in all places where the underlying document states so? Well … seems to be quite a difficult test to be implemented in an automated way, right? That’s why, unfortunately, much of today’s application conformance testing is still performed manually.
Ok, you might ask, what’s all the talk about OOXML and conformance testing anyway? Well, some of it has to do with JTC1/SC34/WG5, or in plain English, with document interoperability. Now that Office 2007 SP2 supports ODF 1.1, all of the sudden the issue of document interoperability got much hotter. And obviously, conformance testing is going to play a major role in this area for years to come.