RE: [CONTEXT] not a requirement

Right, it's no longer first per ACTION-162 and we are debating, though not very vigorously, toning down the bit you find difficult per ACTION-152:

[CAPABILITIES]/[CONTEXT] For all but the simplest sites, do not take a least
common denominator approach and take reasonable steps to provide an enhanced
user experience by exploiting capabilities of the device.

Jo

> -----Original Message-----
> From: public-bpwg-comments-request@w3.org
> [mailto:public-bpwg-comments-request@w3.org]On Behalf Of Charles
> McCathieNevile
> Sent: 08 February 2006 03:19
> To: bpwg-comments
> Subject: [CONTEXT] not a requirement
> 
> 
> 
> There are many types of content which do not require any 
> adaptation. There  
> is no point in these services determining any kind of context. Further,  
> there is no point in determining context in any circumstances for a  
> service that cannot make use of the information.
> 
> This is not a best practice in itself, merely a technique that 
> can be used  
> to meet some others.
> 
> In addition, as has been noted by others, having it appear first 
> gives an  
> impression of a strong bias against the one web goal stated elsewhere.
> 
> cheers
> 
> Chaals
> 
> -- 
> Charles McCathieNevile                     chaals@opera.com
>    hablo español  -  je parle français  -  jeg lærer norsk
>       Peek into the kitchen: http://snapshot.opera.com/
>

Received on Wednesday, 8 February 2006 12:59:41 UTC