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

RE: ISSUE-245 (ADC The Un-Dead): ADC, A Wooden Stake and Some Garlic Needed [Mobile Web Applications Best Practices]

From: Scheppe, Kai-Dietrich <k.scheppe@telekom.de>
Date: Thu, 17 Apr 2008 17:54:30 +0200
Message-ID: <398533C370C23441981074C456AA3BDD031DB335@QEO00226.de.t-online.corp>
To: "Mobile Web Best Practices Working Group WG" <public-bpwg@w3.org>

As per ACTION-737 I am going to do what I was already doing :-)

I propose that we do come up with a means to exploit every capability,
but should also take a subset of those capabilities and create a typical
device of todays day and age.

I believe that we should ask some questions regarding the intent of BP2:

- is it merely a guideline on how to create good content with devices of
  If yes, then we must assume that it too will be outdated in short
time, but we give no indication that we know that.
  Instead, as guidelines, they seem to be true forever.  But since many
of them are capabilities focussed, this is incorrect.
  Yet, simply creating a guideline is ok, provided we have no higher

- do we implicitly state that any modern device will make a reasonable
online experience possible?
  no matter how badly the content is put together?
  I would hope not, but we would do that by not defining a "bar" that
needs to be topped.

- do we willfully refrain from helping authors who cannot use content
adaptation by giving them a grouping of guidelines to adhere to?
  After all, which devices can do what

- since technology will move on, whatever we write today will be
outdated to tomorrow.  
  Do we think we will not be able to set a new bar, to define a new ADC
when some other group comes along later?

- Kai
Received on Thursday, 17 April 2008 15:55:25 UTC

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