- From: Robin Berjon <robin@robineko.com>
- Date: Mon, 31 May 2010 16:05:26 +0200
- To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Cc: W3C Device APIs and Policy WG <public-device-apis@w3.org>
Hi Anssi, On May 31, 2010, at 13:16 , Anssi Kostiainen wrote: > During last week's telco the WG was requesting use cases for exposing network attributes that are currently in danger of being dropped out. We did some thinking and came up with the following use cases. The below UCs are applicable to widgets (implying user's consent is required during installation), and not necessarily for the open web. If these are use cases that you don't see as applying to the open web, then I'll point out that the consensus from the call was that we could farm those out to a separate specification that would extend SysInfo (and I'm guessing likewise for other documents). If you're interested in supporting these, then I can only encourage you to go forward with it and put something in CVS. It's certainly in-charter. > - roaming (re ACTION-177) > > A widget wants to optimize the user experience by reducing data traffic or displaying user warnings about increased data costs when the device is roaming. I think that roaming is in-scope for the open web, but it does have the issue (as discussed) that it doesn't necessarily mean "expensive". We agreed to improve the specification with some explanation of how to best use it. -- Robin Berjon robineko — hired gun, higher standards http://robineko.com/
Received on Monday, 31 May 2010 14:05:56 UTC