W3C home > Mailing lists > Public > public-bpwg@w3.org > May 2008

ACTION-760 Reiterate Caveat on MobileOK for Korean Task Force

From: Jo Rabin <jrabin@mtld.mobi>
Date: Thu, 22 May 2008 19:15:18 +0100
Message-ID: <4835B836.9000108@mtld.mobi>
To: MWI BPWG Public <public-bpwg@w3.org>

On the call of 15th May we discussed the document from the Korean Task 
Force [1]. Ref the Gap Analysis, an item of concern was that the 
mobileOK Basic Tests and the definition of the DDC is not a reflection 
of or description of the state of the market in any particular community 
or country. (This point was also discussed in the course of the F2F in 
Korea.)

Rather, it represents a base line of the lowest possible level of 
equipment that the BPWG considers it worth considering when creating 
services for delivery to mobile devices. i.e. the BPWG is saying that it 
SHOULD be possible to access services from devices that have such 
specifications. Equally, the BPWG says that services SHOULD take 
advantage of more advanced features.

To reiterate, mobileOK Basic (and the DDC) is not considered a design 
point to aspire to. It is the absolute minimum that Services should achieve.

The BPWG has also debated at length the desirability of having a higher 
design point (called the ADC etc.) and has decided not to define this 
(as discussed under ISSUE-245). In short, the message is to take 
advantage of capabilities that are relevant to the application and to be 
sensitive to the context of use.

In carrying out its work on the Gap Analysis, the Korean task force 
should keep in mind the point that mobileOK is a minimal requirement. To 
change the values in mobileOK Basic for the Korean market would be to 
make the statement that a device with DDC-like capabilities is not a 
valid device for accessing the Web in Korea, and that that Service 
designers and creators should feel under no obligation to serve such 
devices.

Jo

[1] http://docs.google.com/View?docid=ddkw3489_20hqnfq7fr
Received on Thursday, 22 May 2008 18:16:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:58 UTC