Mobile Web Best Practices Working Group News

Content Transformation Guidelines in Last Call — 6 August 2008

The Mobile Web Best Practices Working Group published a Last Call Working Draft of the Content Transformation Guidelines document a few days ago.

The document establishes a framework for Content providers and Content Transformation proxies to better communicate with each other so that the user be provided with at least a functional user experience of the Web, when mobile. The starting point is that Content Transformation is being deployed widely across mobile data access networks.

Since the publication of the document as a First Public Working Draft, and the last announcement in this blog, most of the document has been re-written in a more precise and normative way.

The publication of a document as a Last Call means that the Working Group thinks it managed to create a consistent document that represents the consensus view of a range of industry players. It now encourages the community at large to review and comment on the document.

The Working Group expects that changes will have to be made. For instance, it was already pointed out that the interpretation of a URI reference that is a same-document URI, and that is defined without fragment identifier, as pointing out to the underlying resource, and not to this specific representation of the resource does not match that defined in the RFC 3986 (section 4.4). The Working Group is likely to change its recommended use of the Link element.

The Last Call review period ends on 16 September 2008. Comments should be sent to the public mailing-list (publicly archived).

Francois Daoust Permalink

Mobile Web Best Practices published as a W3C Recommendation! — 6 August 2008

The Mobile Web Best Practices 1.0 was published as a W3C Recommendation last week.

The Mobile Web Best Practices Working Group had been waiting for that to happen for some time now. This final move forward on the Recommendation track depended on the publication of XHTML Basic 1.1, the recommended Mobile markup language, as a W3C Recommendation as well. This was done at the same time.

Both are excellent news for the Mobile Web!

The Mobile Web Best Practices Working Group especially welcomes the recognition of its Best Practices by the other Working Groups and the community at large. It strongly encourages content providers and developers of content authoring tools to keep them in mind and put them into practice. The summary page could be a useful online companion, while the Mobile Web Best Practices flipcards are a fairly cool pocket reminder!

The work of the Working Group regarding Best Practices is not over yet. While the set of Best Practices this document contains essentially referred to the development of Mobile Web pages, it occurred to the Working Group that Mobile Web Applications offered incredible possibilities in terms of user interaction. It started working on a set of Best Practices focused on Mobile Web Applications. The First Public Working Draft of the Mobile Web Application Best Practices was published last week as well. Much work remains to be done on this new document. The Working Group is looking for feedback (see the Status of This Document section for details).

Francois Daoust Permalink

Doing both Mobile Web Best Practices and Web Content Accessibility Guidelines — 9 July 2008

A few months ago, the Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group published a First Public Working Draft of a document that explored the overlaps and differences between the Mobile Web Best Practices (MWBP) and the Web Content Accessibility Guidelines (WCAG).

A new draft was published a few days ago: Relationship Between Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines.

The document was re-engineered and simplified with a view to making it easier to read and apply. In particular, the sections that explained why following a given Mobile Web Best Practice may help users with disabilities were removed for the sake of simplicity. Could the document be further improved?

The pages that detail how to address one specification when you've already done the other were completed. The page WCAG 2.0 and MWBP Together is still mostly empty, though. The thing is it is hard to present a simple mechanism that would make it easy to follow both specifications at once. The current proposal is:

  1. Decide on the WCAG level required for the project, and follow the WCAG 2.0 specification
  2. Using the page From WCAG 2.0 to MWBP, identify and follow the MWBP that still need to be addressed

Whilst it appears to be rejecting the question, it may well be the easiest answer. Could you think of any better idea?

Francois Daoust 1 comment Permalink

<< Previous Page :: Next Page >>

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