<schuki> Zakim: this is webmob

<schuki> Zakim: what conferences do you see?

<schuki> Zakim: list conferences

<schuki> wha????

<schuki> Zakim isn't listening to me

<schuki> chaals: :D

<schuki> thanks!

<schuki> Zakim: list teleconferences

<schuki> weird

<schuki> Zakim: hates me ;.;

<schuki> this is very odd, chaals would you mind telling Zakim "this is webmob?"

<schuki> hey guys, just dialing in!

<schuki> ah thanks chaals!!!

<schuki> lol!

<schuki> we'll get started

<schuki> some callers, many missing, so i'll type notes and send it round!

<schuki> https://lists.w3.org/Archives/Public/public-web-mobile/2015Feb/0014.html

<scribe> Scribe: Dan

<scribe> ScribeNick: DKA

New conference call times going forward

Natasha: we did a doodle poll. I think wed at 3pm UTC is a good time. We’re missing people though - they have conflcits. So we have a new doodle. We got the most hits for Monday at 4pm UTC. So we’ll do that for now on.

<schuki> https://www.w3.org/wiki/Mobile/Meetings#2015_Meetings

… that should be reflected in the meeting page.

… also in the iCal feed.

iCal feed: http://www.w3.org/Mobile/IG/teleconferences.ics

Networking Task Force

<schuki> https://github.com/Data-Info-API/Architecture/blob/master/use-cases.md

<schuki> https://github.com/Data-Info-API/Architecture

We’re working on developing a prototype with Kevin from Telefónica.

Natasha: hopefully something within the next couple of weeks.

… would like to see some comments on this.

… legal issues, use cases, etc...

https://github.com/Data-Info-API/Architecture/issues

<schuki> dka: yes please do send your input

<schuki> ... kevin and i had somequestions for this

<schuki> ... we wondered about the use cases and how applicable they are

<schuki> ... we thoughts about the geo location api and how it works by passing data to the browser

<schuki> ... this seems like a similar architecture to what we're doing here

<schuki> dka: we thinking this is howit would work rather than an xhr request

Dan: also now thinking about this more like how the geolocation API works - the browser calls a private web api instead of exposing this web api directly to the webapp.

Kevin: also some questions about what network operators can and can’t release in real -time. E.g. some of this info is commercially sensitive.

Natasha: comments would be greatly appreciated.

… also getting feedback from policy team and privacy team. Interesting to collect those pieces of data - what can and can’t be shared in different locations / countries.

trackbot, start meeting

<trackbot> Date: 25 February 2015

<scribe> Chair: Natasha

<schuki> https://github.com/w3c-webmob/network-evolution-roadmap

<scribe> Scribe: Dan

<scribe> Scribenick: dka

Natasha: the roadmap is looking 3-5 years ahead.

… we should be able to collect enough info.

<schuki> https://github.com/w3c-webmob/network-evolution-roadmap/blob/master/roadmap.md

… we’ve se tup the repo. Geary has offered to help.

… braindumped a bunch of information which I think is relevant.

… can mobile operators and OEMs please take a look and see if we have issues there?

<gmandyam> Giri Mandyam on the call - hoping to get a first draft of the Network Evolution doc onto GH within the next month

s//Geary/Gigi

Natasha: by the end of March is the deadline for this.

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

Networking taskforce

… you will see we have other deliverables as part of this taskforce. We’re only focusing on the dataplan info API and the network evolution roadmap at the moment. If people want the other things to happen [they need to step forward] to do the work.

API Gap Task Force

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

Natasha: on the API gap - announcement on the standards for webapps on mobile is complete for Jan.

<schuki> http://www.w3.org/Mobile/mobile-web-app-state/

Natasha: lots of work here to make sure it’s updated and to release a version every quarter.

… (by Jedi Dom)

<schuki> https://github.com/w3c-webmob/web-api-gap

Natasha: new APIs: API gap - we have web API gap repo.
... now working on developing that into a document.

… looking for people to be involved with that work

… especially we need usage statistics on native and hybrid API [usage]

Relevant work occurring in other W3C groups

Natasha: Payments group. They are documenting use cases & requirements. We’ve done some of this as well and sent them over to the payments CG.

… they will use these.

… they are working on a wallet API / payment agent.

… also web of things group has just started. A sister group. They are looking at web of things use cases.

Powerful features: http://www.w3.org/TR/powerful-features/

Natasha: also CSP and mixed content drafts.
... will me a tighter security and user experience.

… more work also happening on service worker. Service worker is on Chrome 40.

… so open to experimentation.

… relevant to offline webapp experience.

Cookbook: http://jakearchibald.com/2014/offline-cookbook/

<schuki> dka: jake made some great service worker code snippets and info

<schuki> dka: also "powerful features" is moving forward, talking about the names of this and what it should be

<schuki> ...

<schuki> ... we had a tag call and we agreed this could be a joint piece of work between the TAG and webappsec

https://w3c.github.io/webappsec/specs/powerfulfeatures/

<schuki> dka: hope that this will develop into a more normative definition of what a powerful feature is

<schuki> ... and that it can be enforced properly through the tag review and the webappsec group

Natasha: interesting document. Questions about things should geolocation be more locked down.

… any other updates?

… if so please drop a link or email.

AOB

Natasha: something about mobile world congress.
... please follow on twitter w3c_webmob

… i will try to tweet stuff happening there.

<edent> https://twitter.com/w3c_webmob

Giri: a comment on the webapp sec document. this work seems to be going on in a vacuum. We agreed at TPAC to put out rquest for comment on requuring secure context for geo - and had very little response (except from Mozilla).
... I’m goign to renew that [geo] call and cc other groups.

Dan: please also CC www-tag@w3.org

Giri: will do.

Natasha: next talk on the 21st of March.

Adjourned

<schuki> thanks dka!

trackbot, end meeting

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/khr/xhr/
WARNING: Bad s/// command: s//Geary/Gigi
Found Scribe: Dan
Found ScribeNick: DKA
Found Scribe: Dan
Found ScribeNick: dka

WARNING: No "Present: ... " found!
Possibly Present: Cookbook Dan DanSun Giri Kevin Natasha P29 P3 Scribenick Team_W3M WAI_RDWG aaaa aabb aacc active chaals dka edent gludi gmandyam https ianmaffett jerry joined schuki trackbot webmob
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Found Date: 25 Feb 2015
Guessing minutes URL: http://www.w3.org/2015/02/25-webmob-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.