Mobile Web Best Practices Working Group News

Towards a Common mobileOK Basic Tests Implementation — 4 June 2007

To paraphrase the book title: all I really need to know about HTML I learned from the W3C validator. The specification is of course necessary, but as a developer, I'm usually more interested in whether my particular document follows the specification, and if not then why not, and how I can fix it, and I'm usually interested in knowing this right now. The supporting validation tool is almost all you need to practice good HTML. It's vital to provide tools like this to bring specifications to life and make them practical for the developer community. So, it's time we followed suit. We've created the Mobile Web Best Practices recommendation, and have nearly finalized the mobileOK Basic Tests 1.0 recommendation. It describes automated tests for mobile content in pseudo-code, which is practically begging for an implementation in software. We sincerely believe in our recommendations and want to add value for developers, not just list a bunch of ideas. So, we've begun to create a reference implementation of mobileOK Basic Tests 1.0. Fortunately several groups had already begun this independently. Dom created an early implementation of some tests at dotMobi has released, which implements many mobileOK Basic tests (among other tests). Fundación CTIC has developed an implementation at Why create another implementation? We want to create an open-source, reusable library that combines the strengths of these implementations. Fortunately, the developers behind all three of these are involved in the collaborative effort within BPWG to build a reference implementation. By creating an open, generic library, we enable developers to embed this suite of tests in tools, run a private instance, help enhance and fix the code, or even develop new tools. It's an international effort, with six active developers already from Germany, Spain, Ireland, the United Kingdom, and the United States. I must say I'm pleased to see how open everyone has been about contributing time, code and experience. It's also great to see how well the W3C can incubate collaborative development efforts like this. You can see our work to date in CVS at It's a Java- and XSL-based implementation. You can follow or join in the discussion on the public-mobileok-checker mailing list. We're working towards a first "alpha" release in mid-July, at which point you'll hear from us again since we'll need everyone's help to play-test this thing. Watch this space for more.
Sean Owen Permalink

mobileOK Basic Tests 1.0 goes to Second Last Call — 31 May 2007

The group has released a new draft of its mobileOK Basic Tests document. This "second last call" has been issued after extensive revisions based on the initial last call. The working group invite comments on this draft through 22 June. Please have a look and send any comments to the public W3C mailing list ( Thanks!
Daniel Appelquist Permalink

mobileOK Basic Tests Last Call Comment Period Extended — 2 March 2007

We have decided to extend the deadline for public feedback on mobileOK Basic Tests 1.0 to March 13th. We are genuinely seeking YOUR feedback on this specification -- one that we think will play an important part in the future of the Web on mobile devices. Imagine if, as a user of the Web on your phone, you didn't have to guess any more if a Web site was going to be mobile-friendly. Imagine if the capability to discover mobile-friendly content was built in to every search engine, every mechanism where content could be brought to your attention. By putting a series of definitive tests around the Mobile Web Best Practice guidelines that this group has already produced, we hope to create a baseline for what mobile friendly content is and how it can be detected. But we can't do it without your help. The Mobile Web Best Practices group needs the help of the general public to get its work done. If you're a mobile Web expert, we need your expertise. Please take a look at this document. Challenge us on our assumptions. Show us ways we could optimize what we're already doing. Point out gaps -- things we could be testing for but aren't. That URL again is: Send comments to: Thanks for your attention!
Daniel Appelquist 2 comments Permalink

<< Previous Page :: Next Page >>

Contacts: Daniel Appelquist, Jo Rabin, Chairs
Dominique Hazaël-Massieux and François Daoust, W3C Team Contacts