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

Re: BP2 Name Problem: Delivery context assumed not stated?

From: Jeff Sonstein <jeffs@it.rit.edu>
Date: Fri, 4 Apr 2008 07:52:01 -0400
To: public-bpwg@w3.org
Message-Id: <EEE3CED9-4EC2-420C-B1ED-F17E9337015D@it.rit.edu>
Cc: Charles McCathieNevile <chaals@opera.com>

Chaals wrote:

> So BP2 really becomes how to adapt content to take advantage of
> capabilities - and needs to be clear about how you determine whether  
> or
> not you have those capabilities. If we are working from some  
> preconceived
> notion of what the target browser is, we are making a very big  
> mistake -
> we should be working with an assumption of the kinds of things that  
> phones
> have available, which is a broader set but also makes us consider
> carefully each option


I agree with much of this statement

while graceful degradation and progressive enhancement are indeed
"so 1996" (as one blog-comment had it)
I am afraid that the situation is somewhat like that now...
all mobile browsers do not (yet) support the same minimal-capabilities- 
set
so our code has to figure out at run-time
how to adjust to the browser environment
actually encountered on the client

just my $0.02 worth
jeffs

--
"Absurdity, n.: A statement or belief manifestly
  inconsistent with one's own opinion."
-- Ambrose Bierce --
============

Prof. Jeff Sonstein
Director, MS-IT Program

http://www.it.rit.edu/~jxs/
http://ariadne.iz.net/~jeffs/
http://chw.ariadne.mobi/
http://www.xvrml.net/
http://ariadne.iz.net/~jeffs/jeffs.asc
http://www.it.rit.edu/~jxs/emailDisclaimer.html
Received on Friday, 4 April 2008 11:52:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:51 UTC