- From: Jo Rabin <jo@linguafranca.org>
- Date: Wed, 18 Jul 2012 19:20:46 +0100
- To: Tobie Langel <tobie@fb.com>
- Cc: Core Mobile <public-coremob@w3.org>
- Message-Id: <0FB0A529-7614-408C-8475-F84BC3615BA0@linguafranca.org>
Thanks for the summary Tobie, very useful! I'm noting here for Tracker that this entire thread was in response to Jean-Francois's ACTION-24. Please when fulfilling an action note it like that in your email, preferably as part of the subject, and the emails will be picked up and listed. For example, after I send this this email it will be listed on tracker [1]. What we're trying to do is answer the question: "Are the valid use cases for use of Network Information API in scope for CoreMob Level 1?" Raised as ISSUE-31 [2] in Tracker In order to answer that we need a) To know what the valid use cases are, and b) What is in scope for CoreMob Level 1. Assuming that the valid use cases are documented correctly and completely on Tobie's Wiki Page[3] then all we have to decide is are they in scope for Coremob Level 1 and the answer is ... PROPOSED RESOLUTION: Support for Network Information API is in Scope for Coremob Level 1. thanks Jo [1] https://www.w3.org/community/coremob/track/actions/24 [2] https://www.w3.org/community/coremob/track/issues/31 [4] http://www.w3.org/community/coremob/wiki/Features/Network_Information_API On 18 Jul 2012, at 17:49, Tobie Langel wrote: > Hi, > > In order to make progress on this issue, I've created a wiki page[1] where > I referenced all use cases submitted so far and divided them in to two > categories: those that could be met with Network info and those that > couldn't. > > I also added a section which explains what Network info provides and what > it doesn't. Worth reading as the spec has changed recently. > > I've also added a use case[2] for responsive images, as I found out there > are JavaScript libraries[3] using Network info for this purpose. > > There are three use cases that can be met with the Network Info API alone: > > - Warning against or avoiding downloading of large-sized files > - Poor man's adaptive streaming > - Poor man's responsive img > > > (Note the later ones are temporary solutions until better, dedicated > technology gets specified and implemented.) > > I suggest we concentrate our discussion around these three use cases only. > And make a decision for inclusion in L1 based on the validity of these use > cases and vendor intent to implement the spec. > > Best, > > --tobie > > --- > [1]: > http://www.w3.org/community/coremob/wiki/Features/Network_Information_API > [2]: > http://www.w3.org/community/coremob/wiki/Features/Network_Information_API#P > oor_man.27s_responsive_img > [3]: https://github.com/adamdbradley/foresight.js > >
Received on Wednesday, 18 July 2012 18:21:17 UTC