RE: New draft of mobileOK Basic 1zq (draft 43) - preview of PR draft

Hi All,

I was expecting the W3C to give technical recommendation. Pricing at the end is a marketing task and I am not sure whether this is our task. 

In Germany you pay around 39 euro cent per Megabyte.


Heiko Gerlach 
Vendor Manager / Product Owner
Global Consumer Internet Services & Platforms 
Tel: +49 211 820 2168 
Fax: +49 211 820 2141 
Mobile +49 172 20 40 50 7 

Vodafone Group Services GmbH
Mannesmannufer 2, D-40213 Düsseldorf
Amtsgericht Düsseldorf, HRB 53554 
Geschäftsführung: Dr. Joachim Peters, Rainer Wallek
This message and any files or documents attached are confidential and may also be legally privileged or protected by other legal rules. It is intended only for the individual or entity named. If you are not the named addressee or you have received this email in error, please inform the sender immediately, delete it from your system and do not copy or disclose it or its contents or use it for any purpose. Thank you.  Please also note that transmission cannot be guaranteed to be secure or error- 
-----Original Message-----
From: Francois Daoust [] 
Sent: 07 July 2008 17:03
To: Gerlach, Heiko, VF-Group
Cc: Jo Rabin; MWI BPWG Public
Subject: Re: New draft of mobileOK Basic 1zq (draft 43) - preview of PR draft

Gerlach, Heiko, VF-Group wrote:
> Hi Jo,
> Thanks for the update. I would like to keep the images out of that discussion. So I think we should focus on the html markup size. But we should have in mind that devices are improving steadily. 
> I am concerned that at the end of our discussion many made for mobile sites which are delivering good user experience may not fit with the MobileOK requirements.

100Kb ~ 1$ is still a common thing, and having to pay 0.2$ per page is already expensive. I doubt we should go beyond that. As Jo stated, this is the content delivered to the DDC, content providers should take advantage of device capabilities (on which I would add knowledge that the user has a flat rate for instance) whenever possible.

Note that these limits already appear in Mobile Web Best Practices 1.0, which is about to be transitioned to Recommendation, so there is no real way we can change these values now:

> A 2nd item is the following: If we set up a dediacted mobile ok user agent string the site owners could return/deliver complete different content based on the user agent. And than they are counted as mobile OK?!

That's precisely the idea! The content providers should take advantage of the capabilities of devices whenever possible!

And it indeed has the following not-so-good consequence: a content provider may return a mostly empty page upon receipt of a request that contains the mobileOK User-Agent string, and be mobileOK.


Received on Monday, 7 July 2008 15:08:02 UTC