13:49:41 RRSAgent has joined #dap 13:49:41 logging to http://www.w3.org/2012/04/04-dap-irc 13:49:43 RRSAgent, make logs world 13:49:43 Zakim has joined #dap 13:49:45 Zakim, this will be DAP 13:49:45 ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 11 minutes 13:49:46 Meeting: Device APIs Working Group Teleconference 13:49:46 Date: 04 April 2012 13:50:07 Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2012Apr/0007.html 13:50:40 Regrets+ Robin_Berjon 13:50:51 Chair: Frederick_Hirsch 13:50:54 Present+ Frederick_Hirsch 13:51:40 UW_DAP()10:00AM has now started 13:51:47 + +1.289.261.aaaa 13:53:12 Mohammed has joined #dap 13:53:42 Zakim, aaaa is me 13:53:42 +Josh_Soref; got it 13:54:20 present+Mohammed_Dadas 13:54:34 s/+/+ / 13:55:01 Scribe: Josh_Soref 13:55:27 Zakim, who is on the call? 13:55:27 On the phone I see Josh_Soref 13:56:29 SungOk_You has joined #dap 13:57:10 + +33.5.34.31.aabb 13:57:35 +[IPcaller] 13:57:41 AnssiK has joined #dap 13:57:43 zakim, [IPcaller] is me 13:57:43 +fjh; got it 13:57:48 -Josh_Soref 13:57:56 zakim, who is here? 13:57:56 On the phone I see +33.5.34.31.aabb, fjh 13:58:02 On IRC I see AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, ilkka, mounir, Josh_Soref, rektide, trackbot, dom 13:58:41 +??P10 13:58:51 Present+ Anssi_Kostiainen 13:58:51 dsr has joined #dap 13:59:05 zakim, ??P10 is me 13:59:05 +AnssiK; got it 13:59:34 +Josh_Soref 13:59:41 +Dsr 13:59:53 zakim, aabb is mohammed 13:59:53 +mohammed; got it 14:00:02 + +1.503.542.aacc 14:00:06 Jungkee has joined #dap 14:00:10 Present+ Dsr 14:00:15 Present+ Jungkee_Song 14:00:34 dtran has joined #dap 14:00:34 Zakim, where is +1503? 14:00:34 North American dialing code 1.503 is Oregon 14:00:36 Hi all ! 14:00:36 zakim, who is here? 14:00:36 On the phone I see mohammed, fjh, AnssiK, Josh_Soref, Dsr, +1.503.542.aacc 14:00:38 On IRC I see dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:01:07 zakim, where is 33.5 14:01:07 fjh, I do not see a party named 'where'. If you meant to ask a question you need to add '?' 14:01:13 Sylvain_lalande has joined #dap 14:01:17 zakim, where is +33.5? 14:01:17 country code 33 is France 14:01:23 + +1.425.214.aadd 14:01:31 Zakim, where is aadd? 14:01:31 sorry, Josh_Soref, I do not understand your question 14:01:35 Zakim, where is +1425? 14:01:35 North American dialing code 1.425 is Washington 14:01:58 Present+ Dzung_Tran 14:02:13 aacc is me 14:02:25 s/aacc is me// 14:02:31 Zakim, aacc is dtran 14:02:31 +dtran; got it 14:02:38 Clarke has joined #dap 14:02:42 bryan has joined #dap 14:02:59 +??P33 14:03:03 present +Bryan_Sullivan 14:03:10 RRSAgent, draft minutes 14:03:10 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html Josh_Soref 14:03:31 +??P0 14:03:46 zakim, ??P0 is Clarke 14:03:46 +Clarke; got it 14:03:52 rrsagent, make logs public 14:04:00 Topic: Administrative 14:04:02 Zakim, who is making noise? 14:04:06 Zakim, mute me 14:04:06 Josh_Soref should now be muted 14:04:07 zakim, who is here? 14:04:09 On the phone I see mohammed, fjh, AnssiK, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke 14:04:10 On IRC I see bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, ilkka, mounir, 14:04:10 Present+ Clarke_Stevens 14:04:14 ... Josh_Soref, rektide, trackbot, dom 14:04:17 Josh_Soref, listening for 10 seconds I heard sound from the following: Clarke (6%), fjh (75%), Josh_Soref (15%), ??P33 (5%) 14:04:24 + +33.2.31.26.aaee 14:04:25 Cathy has joined #dap 14:04:39 Web Application Store Community Group Launched: http://lists.w3.org/Archives/Public/public-device-apis/2012Apr/0003.html 14:04:51 Topic: Minutes Approval 14:04:55 adrianba has joined #dap 14:04:58 fjh: we aren't ready to approve them 14:05:00 Draft F2F Minutes (and notes of items in minutes requiring correction): http://lists.w3.org/Archives/Public/public-device-apis/2012Apr/0004.html 14:05:07 ... i doubt we'll be able to approve them next week 14:05:10 ... there's a lot of them 14:05:14 ... please look at them 14:05:15 please review and provide corrections to josh and public list 14:05:33 zakim, aaee is Sylvain_lalande 14:05:33 +Sylvain_lalande; got it 14:05:41 Topic: Chartering new work 14:05:55 fjh: the topic has come up as how/where/when should it be chartered 14:06:00 https://lists.w3.org/Archives/Member/w3c-ac-members/2012JanMar/0057.html 14:06:00 Please have any chartering discussion on AC forum list (member only), see also https://lists.w3.org/Archives/Member/w3c-ac-forum/2012AprJun/0000.html 14:06:06 ... i don't think it's appropriate for our WG to get into the nitty gritty of chartering 14:06:13 + +1.781.266.aaff 14:06:17 ... you can have your AC rep get involved 14:06:17 q+ 14:06:21 ack dsr 14:06:28 ... i don't think it has anything to do with technical merit 14:06:32 dsr: I had some discussions 14:06:33 Zakinthos, aaff is me 14:06:36 +[Microsoft] 14:06:43 Zakim, aaff is Cathy 14:06:43 +Cathy; got it 14:06:45 Zakim, aaff is me 14:06:45 sorry, Cathy, I do not recognize a party named 'aaff' 14:06:55 ... i followed up with ArtB 14:07:08 zakim, [Microsoft] is me 14:07:08 +adrianba; got it 14:07:10 ... there's some informal discussion in various places 14:07:15 ... i'm trying to reach out to various people 14:07:26 fjh: i think what we started to do at the F2F 14:07:39 s/Zakinthos, aaff is me/ 14:07:57 Topic: Sensor API 14:08:06 [I think I should point out that the WG can decide to discuss its charter in public if it so wishes — if you look at the beginning of http://lists.w3.org/Archives/Public/public-device-apis/ that's in fact how the first charter was elaborated] 14:08:30 List discussion following CfC, http://lists.w3.org/Archives/Public/public-device-apis/2012Mar/0222.html 14:08:33 [just be careful in using information you may have obtained through privileged channels in doing so] 14:08:34 fjh: I want to leave it to AC reps + Team 14:08:37 ... I don't want to step into it 14:08:42 Topic: Sensor API 14:08:46 fjh: we had a CfC 14:08:51 ... we talked about eliminating that spec 14:08:52 I am reaching out to people directly to clarify their interests/concerns, we may have discussion relating to use cases, scope on public list, and some people have suggested that a community group may be appropriate to discuss this further. 14:09:11 ... there's been a lot of discussion on the list 14:09:17 ... some people have asked if we can stop the discussion 14:09:20 ... i don't think we can/should 14:09:23 q+ to note that I will be capturing the list discussion on the wiki, and I recommend that we hold off making a decision for the overall threads of argument to be captured. 14:09:25 ... it's been good 14:09:41 ... there's concern about doing things in a blanket fashion 14:09:52 ... where we're really ending up is that we need to look at each sensor 14:09:59 ... and how to package it 14:10:05 ... there's a useful discussion happening 14:10:13 ... we need to look into thresholds/watchpoints 14:10:28 ... i don't think we can resolve anything on this call 14:10:38 ... if you haven't looked at the discussion on the list, you should 14:10:49 ... what i'd like to do is figure out what we can do on the list 14:10:51 q+ 14:10:55 ... and then decide what to publish 14:10:55 ack bryan 14:10:55 bryan, you wanted to note that I will be capturing the list discussion on the wiki, and I recommend that we hold off making a decision for the overall threads of argument to be 14:10:56 q? 14:10:58 ... captured. 14:11:30 +1 agree to capture arguments, understand issues, then decide re cfc 14:11:36 Zakim, who is making noise? 14:11:38 ack dtran 14:11:47 Josh_Soref, listening for 10 seconds I heard sound from the following: fjh (4%), dtran (88%), ??P33 (9%) 14:11:51 dtran: i don't know if it's useful or not to do a quick edit of the current spec 14:11:55 zakim, who is making noise? 14:12:05 fjh, listening for 10 seconds I could not identify any sounds 14:12:22 fjh: my take is that if there's anything concrete, you can move forward 14:12:27 ... the wiki is good 14:12:37 ... if you're able to do an edit that's easy and helps us move forward, then yes 14:12:50 ... imo, anything we can do that's concrete and helps us move forward is good 14:13:05 ... but you need to make a judgement about how much work you want to do 14:13:07 dtran: ok 14:13:14 ... i think the mozilla people [garbled] 14:13:34 ... i think something simple 14:13:43 ... the mozilla guys want something simple for javascript programmers 14:13:49 ... i can put an outline together and send it out 14:13:58 fjh: if anyone on the call has concerns, please speak up 14:14:06 ... bryan: do you have further plans to work on the wiki? 14:14:15 bryan: well yeah, it was intended to be collaboratively edited 14:14:23 ... i will try to capture the thread from the mail list to the wiki 14:14:29 ... it's just there as a template 14:14:40 fjh: i think you have to ask the wiki to be notified 14:14:57 ... so if you, bryan, could send out a notice to the list summarizing big updates 14:14:59 ... that'd be good 14:15:03 bryan: [lost] 14:15:07 fjh: i agree 14:15:14 [ random beeps on the line ] 14:15:40 maybe I just edit the Wiki instead? 14:15:41 s/[lost]/it's going to take a bit of time to work through the issues, to get the architecture right, and we shouldn't rush/ 14:15:53 ... we want to avoid rework 14:16:03 Topic: Network Information API 14:16:06 Network Information API was landed on the Webkit, http://lists.w3.org/Archives/Public/public-device-apis/2012Apr/0002.html 14:16:14 http://lists.w3.org/Archives/Public/public-device-apis/2012Mar/0219.html 14:16:14 fjh: dom raised some concern 14:16:26 zakim, who is here? 14:16:26 On the phone I see mohammed, fjh, AnssiK, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke, Sylvain_lalande, Cathy, adrianba 14:16:29 On IRC I see adrianba, Cathy, bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, 14:16:29 ... ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:16:50 fjh: i didn't get what dom was saying 14:17:06 ... i think he was saying you have a whole stack and it depends on the whole stack 14:17:10 q+ 14:17:16 ack anssik 14:17:37 It will take couple of weeks to capture discussions. I will update the wiki as I see significant new info. We are talking about fundamental API design approaches here, and I recommend that we take out time to do so. This is analogous to the time it took for us to course-correct from programmatic APIs to markup-based APIs (though in this case it should not take *that* long, and in that case we have subsequently waffled on the original course 14:17:37 correction) 14:17:46 unmute anssik 14:17:52 zakim, who is here? 14:17:52 On the phone I see mohammed, fjh, AnssiK, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke, Sylvain_lalande, Cathy, adrianba 14:17:55 On IRC I see adrianba, Cathy, bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, 14:17:55 ... ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:18:08 unmute josh_soref 14:18:15 unmute dtran 14:18:20 zakim, who is here? 14:18:20 On the phone I see mohammed, fjh, AnssiK, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke, Sylvain_lalande, Cathy, adrianba 14:18:22 On IRC I see adrianba, Cathy, bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, 14:18:22 ... ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:18:31 Zakim, unmute dtran 14:18:31 dtran should no longer be muted 14:18:33 Zakim, unmute Josh_Soref 14:18:33 Josh_Soref should no longer be muted 14:18:43 Zakim, mute me 14:18:43 Josh_Soref should now be muted 14:19:00 [ we can't hear AnssiK ] 14:19:02 zakim, who is here? 14:19:02 On the phone I see mohammed, fjh, AnssiK, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke, Sylvain_lalande, Cathy, adrianba 14:19:04 On IRC I see adrianba, Cathy, bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, 14:19:04 ... ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:19:09 -AnssiK 14:19:20 s/nmute member:josh_soref// 14:19:20 s/unmute josh_soref// 14:19:26 s/unmute dtran// 14:19:32 s|s/nmute member:josh_soref//|| 14:19:35 RRSAgent, draft minutes 14:19:35 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html Josh_Soref 14:19:36 +??P3 14:19:48 zakim, who is here? 14:19:48 On the phone I see mohammed, fjh, Josh_Soref (muted), Dsr, dtran (muted), +1.425.214.aadd, ??P33, Clarke, Sylvain_lalande, Cathy, adrianba, ??P3 14:19:50 zakim, ??P3 is me 14:19:50 On IRC I see adrianba, Cathy, bryan, Clarke, Sylvain_lalande, dtran, Jungkee, dsr, AnssiK, SungOk_You, Mohammed, Zakim, RRSAgent, fjh, Samarth, darobin, hiroto_away, lgombos, 14:19:50 ... ilkka, mounir, Josh_Soref, rektide, trackbot, dom 14:19:52 +AnssiK; got it 14:20:15 Zakim, unmute me 14:20:15 Josh_Soref should no longer be muted 14:20:37 I'll use Zakim VoIP 14:20:46 s/I'll use Zakim VoIP// 14:21:00 -AnssiK 14:21:01 RRSAgent, draft minutes 14:21:01 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html Josh_Soref 14:21:29 s/unmute anssik// 14:21:33 s/unmute dtran// 14:21:36 RRSAgent, draft minutes 14:21:36 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html Josh_Soref 14:21:48 + +358.504.86aagg 14:21:56 zakim, aagg is me 14:21:56 +AnssiK; got it 14:21:58 Zakim, mute me 14:21:58 Josh_Soref should now be muted 14:22:09 [ AnssiK calls in -- now with Voice 14:22:17 s/Voice /Voice ]/ 14:22:25 AnssiK: you asked about dom's message 14:22:34 ... in the cellular radio, there are a couple of power states 14:22:51 ... when you are actively sending data over the radio, it costs much more power than when it's idle 14:23:03 ... so if you can inform applications when the radio is already up 14:23:03 q+ to ask (back on the sensors topic), if we can get info from the existing implementations sent to the DAP list and/or put into the wiki, related to the questions on the wiki 14:23:11 ... for example if the user is browsing the web 14:23:30 ... then the web app can try to use the radio concurrently 14:23:42 AnssiK: an event exposed to developers, similar to the online event 14:23:51 ... saying "now the radio is actually up" 14:23:52 Last email on the list related to what Anssi is talking about: http://lists.w3.org/Archives/Public/public-device-apis/2012Mar/0221.html 14:23:56 radio on/off events exposed? 14:24:00 q+ to say that the time slices are too fast for this 14:24:22 AnssiK: so all apps get a notice "the radio is up" 14:24:30 ... and then respond to it and do their work during this window 14:24:55 fjh: there's a lead time for the radio going on 14:24:58 ... and a window when it's on 14:25:09 AnssiK: this is a message bus kind of thing 14:25:15 ... you can be clever re: when to use the resources 14:25:23 ... this is ideal for background situations 14:25:25 Dom started that thread based upon noting the AT&T work on network connection use optimization http://www.research.att.com/articles/featured_stories/2011_03/201102_Energy_efficient?fbid=Jzq2QAkHxoP 14:25:29 sounds sort of like cooperative-multitasking, maybe has similiar issues? 14:25:36 ... like twitter updates/email client updates 14:25:57 ... i'm thinking of a way to do it like offline 14:26:13 q? 14:26:14 ack bryan 14:26:15 bryan, you wanted to ask (back on the sensors topic), if we can get info from the existing implementations sent to the DAP list and/or put into the wiki, related to the questions 14:26:15 ... on the wiki 14:26:29 bryan: there is a thread on the list about this 14:26:37 ... i think something would be a good thing 14:26:45 ... i don't know how complicated it would be in the end for developers 14:26:50 ... to effectively respond to that information 14:26:59 ... maybe even the APN for the app could vary? 14:27:11 ... experience would help us learn what the risks of that information 14:27:16 ... and maybe libraries would develop 14:27:27 q? 14:27:31 ... it's definitely worthwhile to think about that 14:27:34 ack Josh_Soref 14:27:36 Josh_Soref, you wanted to say that the time slices are too fast for this 14:27:42 ... but maybe more precise than simple online 14:28:34 Josh_Soref: radio can go on and off really fast, much faster than javascript app can respond, app needs to be waiting when getting event 14:28:38 josh: the radio goes on and off fast 14:28:50 bryan: we don't think it goes so fast in our analsys 14:29:03 s/analsys/analysis/ 14:29:13 ... not order of ms 14:29:35 Josh_Soref: enable apps to make requests, queue them, have sent when it makes sense 14:29:44 the state changes don't happen on the order of MS, usually a few seconds for the transient states - see the referenced research work from AT&T 14:30:03 that would simplify things for app developer 14:30:14 bryan: we're looking into cooperative network usage 14:30:18 ... cooperative multithreading 14:30:22 ... bundling of network requests 14:30:29 ... that work is being discussed in OMA 14:30:34 ... if we want to go there in W3C 14:30:43 ... we're going to need the information that dom suggested 14:30:47 ... and that AnssiK echoed 14:31:11 fjh: i wonder if this api is bigger 14:31:20 ... it seems like it has a lot of api implications 14:31:32 s/api/implementaton / 14:31:59 [ scribe will move redaction up a line ] 14:32:16 s|[ scribe will move redaction up a line ]|| 14:32:33 fjh: we should take this to the list 14:32:34 we are beginning related work in OMA on bundling/scheduling of network transactions for efficiency - that work if it comes to W3C in some form would need the network state info described here (if that info wasn't just something known by a lower-layer native implementation of some API exposed to the webapp) 14:32:35 the API itself could be modeled on http://dev.w3.org/html5/spec/offline.html#browser-state 14:32:43 ... i think it assumes a certain architecture behind it 14:33:23 q? 14:33:23 q? 14:33:55 bryan: [sensors] if we could get people to gather information relating to implementations that already work 14:34:08 ... privacy, parameter design, what the share, ... 14:34:13 ... i'll send a request to the list 14:34:24 fjh: right, that will be helpful 14:34:59 fjh: what i try to do for a call is use the list as input for a call 14:35:08 ... and not do things on the call without drive from the list 14:35:11 Topic: AoB 14:35:17 RRSAgent, draft minutes 14:35:17 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html Josh_Soref 14:35:33 fjh: please review the F2F minutes 14:35:33 the overall objective of the OMA work I mentioned is to help address the network resource efficiency of having multiple always-on apps, that may not need immediate fulfillment of a network request, or a distinct network connection to deliver it. 14:35:40 ... send comments to josh and the list 14:35:51 ... anything else? 14:35:59 Josh_Soref: next week runs into some people's vacations 14:36:11 fjh: I know I have a vacation the following week 14:36:29 Josh_Soref: next week is Passover, but I'll be in 14:36:40 The Tacking Protection WG meeting in DC is next week. 14:36:45 fjh: if we have many regrets, we'll cancel 14:36:54 s/Tacking/Tracking/ 14:37:14 ... or we could cancel if there's nothing to discuss 14:37:21 ... i'll talk with darobin 14:37:59 [we can make that decision on Tuesday] 14:38:12 Josh_Soref: there was supposed to be a Web Apps meeting next week, but they moved it out because they didn't get a venue 14:38:26 [ adjourned ] 14:38:27 - +1.425.214.aadd 14:38:29 trackbot, end meeting 14:38:29 Zakim, list attendees 14:38:29 As of this point the attendees have been +1.289.261.aaaa, Josh_Soref, +33.5.34.31.aabb, fjh, AnssiK, Dsr, mohammed, +1.503.542.aacc, +1.425.214.aadd, dtran, Clarke, 14:38:33 ... +33.2.31.26.aaee, Sylvain_lalande, +1.781.266.aaff, Cathy, adrianba, +358.504.86aagg 14:38:35 -Clarke 14:38:37 RRSAgent, please draft minutes 14:38:37 I have made the request to generate http://www.w3.org/2012/04/04-dap-minutes.html trackbot 14:38:38 RRSAgent, bye 14:38:38 I see no action items