WebMob teleconf

<schuki> for anyone who needs call details: https://www.w3.org/wiki/Mobile/Meetings

<scribe> ScribeNick: dom

Welcome

schuki: JAPAN IS FLU
... happy new flu to all
... today on our agenda some updates on the task forces
... welcome to some new group participants
... relevant mobile updates from W3C
... any addition to the agenda?

Task Force update

schuki: some of you were not on the call in December

<schuki> https://www.w3.org/wiki/Mobile/Work

schuki: on that call, we explained our new approach for this year
... we've been documenting use cases and requirements for APIs
... we want to continue that as part of an API gap task force
... but in addition, we want to look at the interactions between network and Web, a topic important to many participants in this group
... the wiki page has links to the charters
... we'll review the two proposed task forces on this call

Networking task force

<schuki> https://github.com/w3c-webmob/networking-tf-charter/blob/master/charter.md

schuki: the networking task force came primarily from the breakout session that Dom held in TPAC in October
... (telcos@w3c)
... a number of you attended and gave input on how W3C could do more for network operators and ISPs
... the charter is a result of that discussion; it was sent to the list in December and got a lot support for it

<schuki> https://github.com/w3c-webmob/networking-tf-charter/blob/master/charter.md#deliverables

schuki: we're thus approving the charter as of today; we'll thus be working on the deliverables in that charter
... including a Data Plan Info API, Optmiization API, Network bundling, roadmaps of evolutions
... we can't tackled everything at once; we'll start with 2 or 3 to begin with

<schuki> https://www.w3.org/wiki/Mobile/Work

schuki: the 3 things we will be looking at are Data Plan API (which I'll lead),
... Bundling of requests (led by Dom)
... and Network evolution roadmap (still tbd)
... the roadmap aims at detailing how the network is set to evolve in the upcoming say 3 years
... not everything can be shared publicly in the operators world
... if anyone is interested in helping out, let me know
... question or comments on the roadmap?
... we want to explain the evolution of network to help see how they may affect the Web
... incl NFV, "5G" (even though it doesn't exist)
... as they may impact Web technologies

<schuki> dom: Bundling of network requests and security

<schuki> ... the idea of this document will be to look into how resources are delivered over the web

<schuki> ... and then we can look into whether requests should be delivered in bundles, separately, performance for new protocols

<schuki> ... it would be good for us to understand to these issues / topics and document them

schuki: this hasn't started yet
... a lot of work has already been done in this space when SPDY then HTTP2 got developed
... would be useful to understand that and see if we can bring some statistics in that discussion

<dka> +1

schuki: The other item is the Data Info API
... I'm working on this with Telefonica, Mozilla, Google, and some contributions from Vodafone
... it aims to deliver to give info about the user data plan back to the device
... e.g. how much data can the user still download on their current plan
... we know there are privacy issues attached to this, possible legal problems as well
... we're working on this with GSMA legal team
... we still need to understand how this would work from an operators view
... before we can move to prototypes with browser vendors
... if you're interested to work on this, let me know

<dka> It’s a wonderful task force.

schuki: I set some deadlines on our work page
... e.g. Feb 21 for networking evolution assuming we find someone knowledgeable
... Data Info API set for June, Bundling from April

Dom: ArtB is asking whether the charters are final or if we should do a CfC?
... I think there was sufficient support and review time for networking task force to assert there was consensus
... as we will discuss, it may get to a different conclusion on the API task force

Natasha: noted; I'll remove the [draft] label on the networking task force

API Gap Task Force

<schuki> https://github.com/w3c-webmob/api-gap-tf-charter/blob/master/charter.md

schuki: this charter hasn't received as much support as the networking charter, so we're still treating it as draft
... it may be because of the time of the announcement (December)
... or that people found it not fit
... I propose to look at the deliverables and people should feel free to +1 on these
... the charter is grouping some of our existing work, trying to formalize them a bit and get them updated on a more regular basis
... plus a few additional deliverables
... task force would work on documenting gaps and documenting use cases and req (as Marcos has spearheaded so far)
... in terms of gap documents, there is the Standards for Web Applications on Mobile that Dom releases on a regular basis
... the API Gap List is another important piece of work, but could use some formalization and fleshing up
... it doesn't need to be completely exhaustive, but at least try to look at popular APIs from native platforms
... A proposed addition to our work is to look at popular plugins and extensions to see if there are lessons to be learned from them
... Finally, the Gap Analysis document would make a higher-level comparison between Web and native
... One of the proposals with the charter is to link them to specific regular deadlines to push for updates
... of course, getting the 1st version might take more time to pull together

<schuki> https://www.w3.org/wiki/Mobile/Work

schuki: We would start by focusing on 2 main items
... the standards roadmap
... and API Gap, which Leandro would lead for an early March release
... there hasn't been much support yet on constituting this work as a task force — please let us know

Dom: I'll release another edition of the roadmap around the end of this month FYI

Schuki: the API Gap document can have impact across W3C, incl. on the recent IoT discussions

New Group Participants

Schuki: we have a number of new group participants (from Dec and Jan)
... UCWeb (from UC Browser)
... Baidu
... they had expressed interest on Deep Linking
... Giri is joining us from Qualcomm
... @@@ from Japan
... Tencent
... Jérôme from Orange
... Ilya and Chaals from Yandex
... I'll be getting in touch with all of you/them to see how they can contribute to the group's work

W3C updates relevant for mobile

Schuki: some updates relevant for mobile that I've seen
... please share yours as well
... e.g. work where use cases from mobile would be useful
... or work that has impact on mobile
... 3 favorite updates from me: Payments IG is kicking off, Web of Things is going on, and TAG view of moving the Web to https which DKA will tell us about

<dka> con gusto

Schuki: First, the Payment IG is having a F2F early Feb with important topics, incl Wallet, use cases and requirements, payment tokenization and flow
... it will be in Amsterdam

<Istvan> it is in Utrecht

<Istvan> probably not for now

Schuki: Second, the Web of Things

<Istvan> i had issues with audio - sorry

Schuki: the Community Group is being upgraded to an Interest Group

<Istvan> many thanks, I cna give an update fo ryou at the next call

Schuki: they're working through the use cases of where the Web fits into the IoT
... some good contributions from NTT on use cases for local network

<dka> https://w3ctag.github.io/web-https/

DKA: the TAG is working on the document I've pasted on IRC the link to
... it's a TAG finding — a guidance document that is intended to influence additional work in the W3C and the standards community
... this document is specifically targeted toward the idea we're moving more and more of the Web to encryption, via TLS in particular
... the document lists some of the motivations behind that
... incl. mobile oriented ones
... e.g. limiting privileged APIs to secure origins
... e.g. for geolocation or media capture
... the document is sweet and short
... it also discusses some of the usually raised concerns about https

<chaals> [The document is much sweeter and shorter than the mailing list discussion about it…]

DKA: There was also a recent election in the TAG, including Yan from Yahoo who will help us in this field through her experience
... some interesting discussions around the UX of security in browsers
... esp. as it has been more challenging to express it in mobile
... maybe this group can help for the mobile specifics

<schuki> dom: ongoing work for application foundations

https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_most_important

<dka> This is the blog post from Yan: https://zyan.scripts.mit.edu/blog/tls-everything/

https://lists.w3.org/Archives/Public/public-most-important-priorities/

<schuki> dom: AB started task force for working towards the most important priorities

<schuki> ... for w3c and standards

http://www.w3.org/blog/2014/10/application-foundations-for-the-open-web-platform/

<schuki> ... it was annouced with the application foundations

https://www.w3.org/wiki/Application_Foundations

<schuki> ... hopefully this would give some approach to where the web is going

<schuki> ... this is mainly a heads-up for this, but good for everyone to know!

schuki: it will be interesting to see the focus that is emerging from that work
... next time, I'd like to give an update around security
... Web Crypto is rechartering
... Web App Sec is making interesting progress with their work

AOB

Schuki: meeting time is 3pm one Wednesday every month
... that time is difficult for some people
... maybe we can run a Doodle to find a better slot
... it's obviously hard to find a time that works globally
... I'll send a Doodle to see if we can find a slot that works better for more people
... Finally, MWC is coming up
... both Natasha and Istvan will be there; so will Dom
... if you're attending and want to catch up on WebMob, let me know