13:00:00 RRSAgent has joined #sysapps 13:00:00 logging to http://www.w3.org/2013/08/29-sysapps-irc 13:00:15 RRSAgent, draft minutes 13:00:15 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html Josh_Soref 13:00:18 RRSAgent, make logs world 13:00:33 Zakim, this will be SysApps 13:00:33 ok, Josh_Soref, I see UW_SYSAPPS()8:00AM already started 13:00:54 Agenda: http://www.w3.org/wiki/System_Applications:_2nd_F2F_Meeting_Agenda 13:01:05 Meeting: SysApps Face-to-Face #2 13:01:13 Chair: mounir, wonsuk 13:01:32 scribe: Josh_Soref 13:01:34 scribenick: timeless 13:01:39 RRSAgent, draft minutes 13:01:39 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 13:03:54 Joonhyung has joined #sysapps 13:08:36 Zakim, what is the code? 13:08:36 the conference code is 79727 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Josh_Soref 13:08:49 Josh_Soref has changed the topic to: conference code is 79727 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), 13:12:04 marcosc has joined #sysapps 13:14:04 jungkees has joined #sysapps 13:14:30 Present+ Jungkee_Song 13:17:55 gmandyam has joined #sysapps 13:17:59 Marta has joined #sysapps 13:18:03 chaals has joined #sysapps 13:18:40 topic: DataStore 13:18:55 https://wiki.mozilla.org/WebAPI/DataStore 13:19:11 s|https://wiki.mozilla.org/WebAPI/DataStore|-> https://wiki.mozilla.org/WebAPI/DataStore WebAPI/DataStore| 13:19:39 jmajnert has joined #sysapps 13:19:40 marcosc: zkis, you did some work showing that you could map contacts to this? 13:19:54 lgombos has joined #sysapps 13:20:03 zkis has joined #sysapps 13:20:11 q? 13:20:36 Claes has joined #sysapps 13:21:00 https://etherpad.mozilla.org/un9XkdXeKh 13:21:16 genelian has joined #sysapps 13:21:20 zkis: i removed the storage access methods -- they're provided by datastore 13:21:26 ... i moved the sms/mms objects to navigator 13:21:30 Present+ Claes_Nilsson 13:21:50 can someone drop the link for the MozPad? 13:21:52 s|https://etherpad.mozilla.org/un9XkdXeKh|-> https://etherpad.mozilla.org/un9XkdXeKh draft API for W3C System Applications Messaging API, using DataStore concept| 13:22:08 s/can someone drop the link for the MozPad?// 13:22:17 RRSAgent, draft minutes 13:22:17 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 13:22:36 Present+ Anssi_Kostiainen 13:22:41 Present+ Sakari_Poussa 13:22:51 Zakim, who is on the call? 13:22:51 On the phone I see [Mozilla] 13:22:54 Present+ Wonsuk_Lee 13:23:22 https://etherpad.mozilla.org/whatever-you-want 13:23:44 Zakim, [Mozilla] contains marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes 13:23:44 +marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes; got it 13:24:05 Present+ Gene Lian 13:24:13 s/Gene Lian/Gene_Lian 13:25:09 marcosc: how does the system know where to put the data for sms? 13:25:14 Present+ Gene_Lian 13:25:15 zkis: we'd need to agree to this 13:25:40 s/Present+ Gene_Lian// 13:25:51 zkis: i've renamed `name` to `type` 13:25:57 marcosc: how do you query this? 13:26:06 ... does the datastore represent all objects? 13:26:10 ... i don't see a cursor 13:26:17 Present+ Mounir_Lamouri 13:26:17 zkis: the datastore doesn't specify underlying satorage 13:26:22 Present+ Laszlo_Gombos 13:26:40 s/satorage/storage/ 13:27:09 mounir: the UC is to exactly not do that with Datastore 13:27:19 ... if you want to get all contacts w/ FirstName=John 13:27:33 ... you export all data from the Datastore into your own IndexedDB 13:27:42 ... and that Datastore has its own structure / indices 13:28:01 marcosc: aren't you duplicating data? 13:28:12 s/Datastore/IndexedDB/ 13:28:22 dsr has joined #sysapps 13:28:25 Everyone: Yes 13:28:47 marcosc: it's screaming for other functionality 13:28:52 ... IndexedDB is already a pain 13:28:56 q+ Josh_Soref to answer 13:29:03 ... you're stuck w/ half the functionality you need 13:29:14 ... data synchronization 13:29:16 ... but nothing else 13:30:10 ack Josh_Soref 13:30:10 Josh_Soref, you wanted to answer 13:30:25 q? 13:30:26 q+ 13:30:28 Josh_Soref: The idea is to make everything except synchronization painful 13:31:14 ... to force you to pull all the information into your storage system (probably IndexedDB) 13:34:26 Present+ Chaals(IRC) 13:35:12 ... you construct your IndexedDB (or whatever) to have wihchever indices you need 13:38:26 ack mounir 13:43:59 wonsuk has joined #sysapps 13:44:42 wonsuk has left #sysapps 13:44:49 wonsuk has joined #sysapps 13:46:13 thinker has joined #sysapps 13:47:36 Zakim, who is on the call? 13:47:36 On the phone I see [Mozilla] 13:47:37 [Mozilla] has marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes 13:48:02 zkis: I want to be able to expose sim1, sim2, and phone as distinct sources of data 13:48:09 mounir: i don't want filtering in the datastore 13:48:29 marcosc: are we renaming DataStore to DataSource to indicate that it's not really a primary write api 13:48:32 Josh_Soref: yes 13:48:43 mounir: there's no UC for having isolation of data 13:49:00 Josh_Soref: BlackBerry Balance and Samsung's competition into the area shows that there is demand for isolation 13:49:31 ... where an application or type of application have multiple things, one which they're ok w/ sharing to everyone, and one which users (or their supervisors) only want to share w/ some limited set 13:50:17 Josh_Soref: chaals is not in the room (and not on the bridge) 13:50:28 zkis: is there something we can draw on? 13:50:30 marcosc: yes 13:50:40 [ Marcos wanders off to get something for scribbling ] 13:50:45 [Yes, being able to identify data from different sources has use cases.] 13:51:35 kenneth_ has joined #sysapps 13:51:43 [SIMs are "often" (for rich users with lots of money to spend) effectively related to location (for poor users they are related to cheapest way to connect to someone)] 13:52:25 opoto has joined #sysapps 13:52:33 [either way, knowing which source "taxi", "john" and "jo*" come from is extremely useful in practice] 13:52:57 hsinyi has joined #sysapps 13:53:08 dsuwirya has joined #sysapps 13:53:46 marcosc: i think that (what chaals said) makes sense 13:54:23 ... Adding .. if you have two sims and you add, and you can't target the sim, what does that mean... 13:54:27 ... is that missing/useful? 13:54:40 ... if i want to add Bob as a Contact for sim2 13:54:44 ... how would i do that? 13:54:55 zkis: let's solve reading first 13:55:24 [If you can't decide which SIM to add to, you have a fail] 13:55:35 zkis: partitions ... 13:55:53 ... as a platform provider, i want the freedom to define how to put the sim data -- together, or separately 13:56:14 ... i want the freedom for merging/not merging online sources 13:56:28 gmandyam: zkis, where would end user dialog boxes appear? 13:56:31 q+ 13:56:37 ... an application that wants something from the dataS* 13:56:44 ... targeting something that's application specific 13:56:54 ... where would a dialog pop up, what would it say? 13:57:00 zkis: dialogs pop up, that's a policy 13:57:08 ... for accessing this data, you need this permission 13:57:24 ... if an application gets Facebook, or All, that's by app 14:00:18 Josh_Soref: The security boundary is at Navigator.getDataStores(type) 14:00:38 ... whether your signature entitled you to all, or you get prompted 14:01:17 ... and whether you permanently grant that source to that client-app 14:01:22 gmandyam: ok 14:01:39 i/boundary/gmandyam: Where is the security boundary?/ 14:01:51 gmandyam: I think this does handle the Gallery API UC too 14:01:54 marcosc: ok 14:01:59 ... i think that was good 14:02:03 ... we made good progress there 14:03:16 q+ genelian 14:03:18 ack genelian 14:03:23 genelian: on UCs 14:03:28 ... we have a "special type of SMS" 14:03:31 ... a "silent SMS" 14:03:37 ... fairly similar to regular SMS 14:03:56 ... when radio interface receives a silent SMS, the system doesn't reflect that 14:04:19 ... can the DataS* api manage that? 14:04:27 zkis: that's binary/port targeted 14:04:35 ... and the system won't dispatch it to this API 14:04:44 marcosc: are they stored? 14:05:14 zkis: they are not serialized to the sim, they are associated with it and dispatched or dropped immediately 14:05:19 zkis: what's next? 14:05:24 marcosc: sounds like it's a good thing 14:05:27 ... we know there are issues 14:05:33 ... can we retrofit apis to fit this? 14:05:35 ... kind of maybe 14:05:46 zkis: can we make a resolution to use it in the spec? 14:05:55 mounir: i don't think we should resolve to use the api 14:06:00 ... unless people agree to the UCs 14:06:12 mounir: i think we have fundamental requirement differences 14:06:18 zkis: so you're suggesting dropping the whole thing? 14:06:26 mounir: i think we should think about it and see how we should go 14:06:34 zkis: who looks into it, how, how does this work? 14:06:51 ... i could do work on messaging/telephony, or work w/ chris/eduardo on contacts 14:06:54 marcosc: i could work on it 14:07:00 mounir: chris could update contacts 14:07:04 ... eduardo updates messaging 14:07:11 mounir: what if some people want to implement, some don't 14:07:17 ... some think it's a good idea, some don't 14:07:26 ... if you want to do updates, i'm not going to forbid you 14:07:30 ... i don't feel consensus 14:07:35 zkis: let's vote 14:08:21 thinker: datasource for other apis ... contacts/messaging 14:08:28 ... we have a lot of api to define similar 14:08:34 marcosc: yes/no 14:08:42 mounir: you can't do yes/no... yes for what? 14:08:56 [ Argument between mounir / marcosc -- both of Mozilla ] 14:09:09 zkis: if you're giving this to the community 14:09:14 ... and letting it be changed 14:09:23 mounir: the requirements you have are not the requirements we have 14:09:32 ... i won't commit to that 14:09:52 zkis: it's adding one property 14:09:58 mounir: it's changing the meaning 14:10:04 anssik: we could commit to refining the UCs 14:10:15 zkis: i need a clear answer from mounir 14:10:21 wonsuk: i don't think we made a consensus now 14:10:26 ... how about more time for discussion 14:10:28 s/from mounir/from Mozilla/ 14:10:41 ... not all participants are here at this meeting 14:10:45 ... i want feedback from other editors 14:10:54 ... and we can make a decision later on how to handle this API 14:10:57 ... i'm not sure the scope 14:11:05 zkis: first we need UCs and Requirements 14:11:26 wonsuk: we mentioned Messaging/Contacts 14:11:30 ... gmandyam mentioned Gallery 14:11:37 gmandyam: and mounir said sim card was out of scope 14:11:41 +1 on clearly defining UCs and Reqs and then let the wider group review them 14:11:41 q? 14:11:49 q+ 14:11:52 marcosc: ok, we'll take it to the list 14:11:55 ... it isn't ideal 14:12:05 ... i think it's fair to give the other editors a chance to look at it 14:12:18 dsr: i heard yesterday that we wanted to simplify the other specifications 14:12:30 ... rather than saying in-scope/out-of-scope 14:12:47 ... -- i'll type the rest 14:13:55 ... you could send pull requests 14:13:59 s/... you could send pull requests// 14:14:33 We talked yesterday about simplifying a number of our specifications by refactoring them, that in turn implies understanding whether our respective requirements for those specifications are compatible or not. This should drive the work not questions of scoping for a datastore API. 14:14:45 topic: Event Pages 14:14:49 wonsuk has joined #sysapps 14:14:51 topic: Event Pages 14:14:57 s/topic: Event Pages// 14:15:04 anssik: wondering how we'd like to use the session. we reviewed what we proposed w/ kenneth_ 14:15:12 ... i'd like to propose real time updating the proposal 14:15:17 ... it's on my github 14:15:22 ... you could send pull requests 14:15:28 ... people could point to the spec/section. 14:15:32 ... let's not use github issues 14:15:35 https://etherpad.mozilla.org/event-pages 14:16:07 http://anssiko.github.io/runtime/app-lifecycle.html 14:16:43 s|http://anssiko.github.io/runtime/app-lifecycle.html|-> http://anssiko.github.io/runtime/app-lifecycle.html Application Lifecycle and Events| 14:17:00 mounir: the next time-block will have two sessions in parallel 14:17:43 marcosc: in 45 minutes we'll have a Sockets meeting concurrent to this meeting 14:17:52 ... this block will run for two hours 14:18:20 ... we have half an hour afterwards 14:18:31 ... my idea was that each group would give a summary of what they concluded -- then 14:20:33 ... i don't really expect this to be minuted 14:24:31 i/time-block/Topic: Order of business 14:24:35 topic: Event Pages 14:24:56 anssik: there's a question of whether we're basing stuff on Workers or ... 14:25:05 ... it's on the etherpad 14:28:35 marcosc: "Runtime" is weird, why not "App"? 14:28:43 mounir: because chrome does that 14:33:12 chaals has joined #sysapps 14:41:02 [discussions happenning without scribing] 14:42:38 [OK. I'll ask someone what happened] 15:01:34 chaals has left #sysapps 15:06:16 s/mounir/scribe/ 15:06:27 topic: Break outs 15:06:37 Event Pages has moved to the other room 15:06:50 The main room is now informal 15:06:56 Sockets has moved somewhere 15:10:45 https://etherpad.mozilla.org/event-pages 15:10:53 http://localhost/~akostiai/sysapps/runtime/app-lifecycle.html 15:10:57 JonathanJ1 has joined #sysapps 15:11:18 ehsan has joined #sysapps 15:11:24 s/http://localhost/~akostiai/sysapps/runtime/app-lifecycle.html/http://anssiko.github.io/runtime/app-lifecycle.html/ 15:11:28 http://anssiko.github.io/runtime/app-lifecycle.html 15:12:13 kjwallis has joined #sysapps 15:19:00 thinker has joined #sysapps 15:23:51 JonathanJ1 has joined #sysapps 15:24:21 Present+ Jonghong_Jeon 15:30:24 http://gnosis.cx/publish/programming/sockets.html 15:30:34 http://nodejs.org/api/net.html#net_socket_write_data_encoding_callback 15:30:48 https://developer.mozilla.org/en-US/docs/WebAPI/TCP_Socket 15:34:00 http://stackoverflow.com/questions/2014033/send-and-receive-a-file-in-socket-programming-in-linux-with-c-c-gcc-g 15:34:20 // You need a loop for the write, because not all of the data may be written 15:34:20 // in one call; write will return how many bytes were written. p keeps 15:34:20 // track of where in the buffer we are, while we decrement bytes_read 15:34:20 // to keep track of how many bytes are left to write. 15:34:21 void *p = buffer; 15:34:21 while (bytes_read > 0) { 15:34:21 int bytes_written = write(output_socket, p, bytes_read); 15:34:22 if (bytes_written <= 0) { 15:34:22 // handle errors 15:34:22 } 15:34:22 bytes_read -= bytes_written; 15:34:22 p += bytes_written; 15:34:22 } 15:35:02 http://pubs.opengroup.org/onlinepubs/009695399/functions/write.html 15:35:07 If fildes refers to a socket, write() shall be equivalent to send() with no flags set. 15:35:15 http://pubs.opengroup.org/onlinepubs/009695399/functions/send.html 15:35:27 ssize_t send(int socket, const void *buffer, size_t length, int flags); 15:35:39 RETURN VALUE 15:35:39 Upon successful completion, send() shall return the number of bytes sent. Otherwise, -1 shall be returned and errno set to indicate the error. 15:38:32 http://linux.die.net/man/3/send 15:39:03 If space is not available at the sending socket to hold the message to be transmitted, and the socket file descriptor does not have O_NONBLOCK set, send() shall block until space is available. If space is not available at the sending socket to hold the message to be transmitted, and the socket file descriptor does have O_NONBLOCK set, send() shall fail. The select() and poll() functions can be used to determine when it is possible to send more data. 15:41:54 rrsagent, draft minute 15:41:54 I'm logging. I don't understand 'draft minute', JonathanJ1. Try /msg RRSAgent help 15:45:28 rrsagent, draft minutes 15:45:28 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 15:48:31 chaals has joined #sysapps 16:02:56 http://nodejs.org/api/net.html#net_socket_write_data_encoding_callback 16:05:15 https://github.com/joyent/node/blob/master/src/stream_wrap.cc 16:06:29 https://github.com/joyent/node/blob/master/src/tcp_wrap.cc 16:12:35 zaki, who is on the call? 16:12:41 zakim, who is on the call? 16:12:41 On the phone I see [Mozilla] 16:12:42 [Mozilla] has marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes 16:15:28 [lunch break because Intel guys want to eat] 16:57:15 spoussa has joined #sysapps 17:13:44 topic: Agenda 17:13:58 mounir: i had this slot for SysInfo, but the person who was going to call in isn't here 17:14:02 ... we'll move thatlater 17:14:06 s/thatlater/that to later/ 17:14:16 ... we could start w/ dev outreach 17:14:22 topic: Dev outreach 17:14:44 mounir: we're missing feedback a lot 17:14:48 ... we're missing Implementation Feedback 17:14:53 ... we're missing Developer Feedback 17:14:59 ... we don't know if APIs are following a good path 17:15:08 ... we don't know if developers will like them or not 17:15:47 ... we were wondering if dsr could talk to the W3 dev-rel team 17:16:14 ... do people here have feedback from dev-outreach? 17:16:21 ... or would they be willing to do dev-outreach? 17:16:42 kenneth_ has joined #sysapps 17:16:48 dsr: sure, i can contact the dev outreach team @w3 17:17:02 ... but there's only a few of them 17:17:07 ... wondering what we can do from our website 17:17:12 ... or elsewhere to reach out directly 17:17:20 marcosc: no...because... 17:17:36 ... when we publish stuf 17:17:54 ... Lea Verou sends things out 17:17:59 ... it reaches quite a few people 17:18:05 ... but one-to-one outreach 17:18:12 ... perhaps we want to encourage developers to contribute UCs 17:18:18 ... or contribute examples of what they've written 17:18:37 mounir: i've considered getting a Twitter account 17:18:42 opoto has joined #sysapps 17:18:43 ... for SysApps, and maybe tweet 17:18:49 ... web developers have and use twitter 17:19:04 ... marcosc and I tried to get people from public-script-coord 17:19:11 ... but we didn't get much 17:19:17 marcosc: some were good, some were not so good 17:19:31 mounir: people said very little 17:19:36 ... it's hard to get feedback w/o anything working 17:19:47 ... i'm more optimistic from developers using FirefoxOS APIs 17:20:14 opoto: would it help 17:20:25 ... if we had some way to rapidly share prototypes 17:20:49 ... so it isn't something fully compliant, but something to play w/ 17:20:54 +1 for opoto 17:20:59 marcosc: coincidentally 17:21:05 ... we've tried to do that from the beginning 17:21:12 ... the original Alarm had a reference Impl 17:21:20 ... mart has rewritten that, there's a JS impl 17:21:28 ... there's a pull request yesterday 17:21:40 ... I hope to be able to write a raw sockets api on top of Node 17:21:44 ... but we need help 17:21:49 ... writing real or lightweight impls 17:21:52 ... they don't take too long to write 17:21:58 ... especially on top of node or FirefoxOS 17:22:05 kjwallis has joined #sysapps 17:22:07 Josh_Soref: can i put in a plug for Cordova? 17:22:45 q? 17:22:47 marcosc: i spoke w/ Fil Maj 17:22:51 ... they were keen to do stuff 17:23:10 mounir: implementations behind flags is not enough 17:23:17 ... we don't get feedback until we push stuff to a release build 17:23:29 ... i've tried to get more developer feedback 17:23:36 ... by pushing apis in a limited ecosystem 17:23:59 ... we did that for Contacts API for example 17:24:04 ... we fixed a lot based on that 17:24:25 ... Contacts API is only available in FirefoxOS to signed apps 17:24:32 ... which let us get feedback from some developers 17:24:42 ... we weren't in a position that we couldn't change the api later 17:24:48 ... which is a big issue w/ experimenting 17:25:22 ... marcosc, can you ask the mozilla dev-outreach group? 17:25:28 ... dsr, the same to w3? 17:25:36 ... and i'll create a twitter account and tweet 17:25:49 ACTION: marcosc will contact the dev-rel team at Mozilla to do some dev-outreach 17:26:16 ACTION: dsr will contact the dev-rel team at W3C to do some dev-outreach (marcosc recommends contacting Léa Verou) 17:26:45 ACTION: mounir will open a Twitter account for sysapps and publish some stuff to get developers attention 17:28:32 http://2013.lxjs.org/ 17:32:10 Topic: Coordination and infrastructure 17:33:11 scribe: mounir 17:33:24 rrsagent, draft minutes 17:33:24 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 17:33:27 marcosc: it seems that the github system is working well 17:33:42 ... something I have done is adding people to some groups so they got more emails 17:33:48 ... is that something that bother people? 17:33:58 q+ 17:34:23 [discussion about what to do with ACTIONS recorded] 17:34:44 mounir: I will take care of the actions 17:34:50 marcosc: have ppl got troubles? 17:35:00 ack mounir 17:35:35 ack dsr 17:35:55 mounir: it is still hard to follow what's happening without being following a github repo 17:36:27 marcosc: following what is happening in github is not much 17:37:01 marcosc: I try to look at pull requests to check if things should move to the list 17:37:07 marcosc: but we don't want to slow down things 17:37:49 q? 17:38:17 q+ to ask if we could get PR emails in the list 17:39:18 wonsuk: what about test cases in github? 17:39:33 marcosc: it is too early 17:39:42 ... we need to go to last call 17:40:01 ... we did some tests for app uri scheme but this is because that went to LC in webapps 17:40:31 marcosc: jmajnert will tell you that there are a lot of tests in widget, it takes a long time to write test suite 17:40:45 q? 17:41:01 dsr: why not add test even if it is not complete? 17:41:24 marcosc: we do TDD (Test Driven Development)... 1 sec... 17:41:38 [showing his AlarmPI tests] 17:42:21 [he lost himself in his GH page] 17:42:39 q? 17:42:45 ack mo 17:42:45 mounir, you wanted to ask if we could get PR emails in the list 17:43:19 mounir: what about having PR emails in the mailing list? 17:43:40 marcosc: I do not know if we can filter PR/commits/issues? 17:43:58 mounir: I will have a look 17:44:06 marcosc: ... unless they added this feature recently 17:46:24 cq+ 17:46:27 [marcosc speaks about tests and webkit] 17:46:28 q+ 17:46:38 ack lgombos 17:47:48 as agreed yesterday once the test are getting mature we should push them to the official w3c test repository 17:49:12 s/as agreed/lgombos: as agreed/ 17:49:17 s/lgombos/scribe/ 17:51:48 See http://www.w3.org/QA/2013/08/event_report_test_the_web_forw.html for recent testing the web forward event 17:52:46 anssik: why not send tests to web-platform-tests? 17:53:00 marcosc: I guess we should do at least one 17:53:11 ... Marta and I could send something just to see how it goes 17:53:20 ... and I told tobie that we will do so 17:55:13 Topic: Device Capabilities 17:55:21 http://www.w3.org/2012/sysapps/device-capabilities/ 17:56:12 anssik: we have something in our charter for this 17:56:16 ... lets look at the charter 17:56:22 [showing the charter on the screen] 17:56:46 [reading the charter] 17:57:04 anssik: some of our guys from China have been looking at this 17:57:18 ... we have something in Chrome behind a flag, not really this spec but something similar 17:57:31 ... we tried something similar in DAP, it was called System API 17:57:56 ... IIRC, that spec was shelved because we were not comfortable exposing that API to the Web because of the fingerprinting concerns 17:57:58 q+ 17:58:05 anssik: I do not think we should look into this in details 17:58:20 ... it has been written by people fairly new to the W3C process so do not mind the spec language 17:58:37 ... what I would like to ask the group is if this is in scope and what are the UCs? 17:59:02 anssik: we would like to hear feedback from other implementers if there is interest 17:59:23 ... basically the overview of the specification is that this is a simple API to get system information 17:59:25 rrsagent, draft minutes 17:59:25 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 17:59:41 ... things like information about the available memory, the device available storage space, CPU, number of cores 17:59:58 gprintemps has joined #sysapps 18:00:13 anssik: as an example, one of the UC is to figure out how to split the tasks amongst workers 18:00:28 ... to do that, you need to know how many cores the client has 18:01:11 anssik: what timeless said is that we can already do that today by running computation in N workers and see what is the value of N that is the most efficient 18:01:58 anssik: this is split in different methods, like getCapabilites() that return a list of booleans 18:02:23 anssik: for example, there is 'multiTouchCount' to know how many touch point there is 18:02:34 q+ 18:02:41 marcosc: it seems that all of these should go back to the API that defines those things 18:02:58 anssik: yes, the editor pointed that at the beginning of the specification 18:03:11 ... that was my guidance, this is probably not needed 18:03:45 ack gmandyam 18:04:45 gmandyam: have these spec editors confirmed that this information can be retrieved? for example, there are things here that need to be read from the modem but we never got request to expose that from our customers 18:05:51 gmandyam: you talk about use of wifi for indoor location or gps for indoor location but you might be using a combination of two 18:05:59 ... this is not something that is exposed by the modem 18:06:09 ... did you guys look at if this information is queriable? 18:06:21 s/did you guys/did your guys/ 18:06:39 anssik: I am pretty sure they did not look at your chipsets, this is why we have the discussion here 18:06:52 gmandyam: is that implementable from an Intel stand point? 18:06:59 anssik: yes 18:07:05 gmandyam: is it useful? 18:07:09 anssik: it is another discussion 18:07:20 q+ 18:08:21 gmandyam: I am not sure we will get the two implementation support here 18:08:38 anssik: we should think about if there is use cases if any and then we should see if this is implementable 18:08:47 ack jungkees 18:09:07 jungkees: I do not know if this is appropriate at this time but I have a comment regarding the WebIDL design 18:09:24 jungkees: in 5.1, there is a mistake [did not catch the details] 18:09:36 q- 18:09:43 q? 18:10:23 q+ 18:10:35 Zakim, what's the passcode? 18:10:35 the conference code is 79727 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), marcosc 18:10:40 interface DeviceCapabilityProfile should be rather defined as a dictionary as interface object would not be needed in JavaScript binding. 18:11:15 For what I was referring to (PMIC-targeted API), see the Trepn description at https://developer.qualcomm.com/mobile-development/performance-tools. 18:12:41 http://www.w3.org/2012/sysapps/device-capabilities/#devicecapabilities-interface 18:18:22 q? 18:18:52 [discussion that no one scribed :(] 18:19:17 gmandyam: I think the editors should make the difference between the things that are meaningful and those that are not 18:20:01 ... I understand the UCs but they should step back and see how developers actually use these things 18:20:15 anssik: we should come out with compelling UCs first... 18:20:34 anssik: it seems that some improvements should be done 18:20:49 ... in some APIs but this is out of scope for this WG 18:21:24 q? 18:21:37 For instance, exposing the no. of active cores: this is dynamically managed in typical multicore CPU's based on e.g. loading, thermal mgmt., power mgmt.. It is not clear a developer can leverage this info, and may actually harm their app performance based on knowledge of such info. 18:22:00 ack wonsuk 18:22:14 AndroUser has joined #sysapps 18:22:22 The editors should go beyond the typical W3C description for use cases, and consider exactly how developers would use each system capability exposed through this API. 18:23:06 wonsuk: following DAP experience, we should have UCs 18:23:24 ... and split in different specs if needed 18:23:32 q? 18:23:56 zakim, who is on the call? 18:23:56 On the phone I see [Mozilla] 18:23:57 [Mozilla] has marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes 18:24:38 lgombos: do you expect to change Chromium as you go or are you going to wait until you have a better version of the spec? 18:25:01 q+ 18:25:16 spoussa: the Chromium API is changing all the time so it is not stable anyway 18:25:21 ... it is a subset of that 18:25:32 spoussa: they seem to have UCs for those APIs 18:25:34 q? 18:25:53 ack genelian 18:26:28 genelian: I notice lots of capabilities in the profile and it seems that it is mostly a yes/no value 18:26:47 ... what if the system has more complex answer like if it doesn't want to expose some capabilities? 18:27:02 anssik: generally, developers do this currently with feature detection 18:27:28 ... by looking if the objects exist or try to use the API before assuming if something is present 18:28:01 anssik: generally, web apis should be feature detectable but that is not the case in all APIs 18:28:46 q? 18:29:52 RESOLUTION: the editors of the Device Capabilities API should come back to the group with a new specification with some UCs 18:30:07 ehsan_ has joined #sysapps 18:30:36 Topic: Secure Elements presentation by Gemalto 18:30:51 http://www.w3.org/wiki/images/6/6f/SysApp_-_Secure_Element_API_-_intro.pdf 18:31:06 Zakim, who is on the call? 18:31:06 On the phone I see [Mozilla] 18:31:07 [Mozilla] has marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes 18:31:52 opoto: this is an introduciton to collect some feedback on this subject 18:32:03 opoto: this API is identified in phase 2 of the WG 18:32:25 + +49.151.629.4.aaaa 18:32:56 opoto: for those of you not familiar with secure elements, there is smart cards 18:33:14 ... with contact or NFC (one, the other or both) 18:33:28 ... these smart cards are used in many application domain such as ID cards 18:33:39 ... from governments or corporations 18:34:02 opoto: In these secure elements the chips is running a Java Card VM 18:34:13 ... and the communication with the SE is a standardised API (ISO) 18:34:22 ... these are used everywhere including mobile world 18:34:37 opoto: there are also some SD cards that embed secure elements 18:34:44 ... some of them with contact-less interface 18:35:14 opoto: some device embed hardware secure elements 18:35:35 ... which offer secure service such a tamper-proof storage, crypto op, ... 18:35:54 opoto: we would like to allow web services around SE 18:36:20 opoto: the environment in which we want to use these SE are PC, mobile, tablets, ... 18:36:33 ... in the PC world it might be more common to have smart cards 18:36:42 ... on mobile you will mostly find either sim cards or nfc 18:36:51 ... also, some embedded secure elements 18:37:02 q+ 18:37:09 opoto: one of the main UC for SE is for doing auth 18:37:16 ... the SE is able to host a credential such as a key 18:37:31 ... based on these secrets, it is able to authenticate a user 18:37:43 ... the user can present a smart card instead of typing a user/password 18:37:51 ... which, we know, is bad regarding security 18:38:15 ... the user would have to type a PIN code 18:38:28 ... and then, it will compute a cryptogram that certified that the user is genuine 18:38:44 opoto: this is the scenario that you could have in a web application 18:38:59 ... you could also have a system application such as a VPN using this kind af auth mechanism 18:39:27 opoto: in addition to auth, you would also be able to do signing, for example in email clients 18:39:35 RRSAgent, draft minutes 18:39:35 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 18:39:36 ... to digitally sign an email with your SE 18:39:48 ... these are typical UCs that we would like to address 18:39:57 q? 18:40:18 zolkis: how can we make sure that this is a genuine UI (regarding the PIN code)L 18:40:25 s/)L/)?/ 18:40:42 opoto: this is something that is addressed by the trusted execution environment in the mobile world 18:40:58 ... the environment is trusted, from the input to the display 18:41:09 ... you would need some secure execution environment 18:41:11 ack gmandyam 18:41:24 Contrast UC 1 in the presentation to what FIDO Alliance supports 18:41:51 http://www.fidoalliance.org/how-it-works.html 18:42:24 q+ 18:42:47 gmandyam: it seems to me that what FIDO is doing could cover UC #1 [from the presentation] 18:43:09 opoto: FIDO alliance cover some of those scenario but they do not cover some other UC like authentification with a SIM card 18:43:21 gmandyam: fair enough but we want this to go further than SIM card 18:43:30 ... but what you are proposing is specific to SIM card 18:43:31 opoto: no 18:43:51 +1 to gmandyam 's concern that this seems to be specific to SIM card 18:43:55 opoto: maybe there is some overlap with FIDO alliance but I do not think they are covering all the UCs 18:44:00 q? 18:44:04 ack dsr 18:44:35 dsr: I think we should look at the low level vs high level API here 18:44:50 ... we have some low level APIs [some examples] 18:45:10 ... but some high level API like [can't hear] 18:47:00 Cites experience with HTML object element which proved valuable e.g. for Flash, and we now have standardized a high level API for specific cases e.g. the HTML5 audio and video elements 18:48:09 q+ 18:48:24 ack 18:48:26 ack dsr 18:48:39 opoto: another interesting UC is for mobile commerce 18:48:59 ... what is currently used today to pay is either a very simple payment scheme where you only provide your account/CC details 18:49:07 ... with no verifications 18:49:15 ... or the payload that a bank propose 18:49:25 ... but with this, you could directly pay with a SE that embed the payment application 18:49:40 ... it could be a NFC visa card in your mobile 18:49:49 ... the SE could communicate with this card to sign the transaction 18:49:58 AFAICT, there are multiple standards bodies working on API's that access the SIM. OMA OpenCM API for example, which has web bindings. GlobalPlatform is taking up API's for SE's, and this standards body has much stronger expertise in this area than the W3C. 18:49:59 q+ to say that we have a payment api/tf for that 18:50:27 opoto: another UC is for updting the context of a SE 18:50:49 ... for example, in a public transportation card like London's Oyster card 18:51:11 ... with this API what would be interesting would be to buy tickets on this card online 18:51:20 ... you should be able to pay online and load content in your SE 18:51:34 q? 18:51:46 opoto: another UC is out of bound authentification 18:51:53 ... this is when you use a second device to authenticate 18:52:05 ... for example, you use your PC and you want to authenticate with your mobile 18:52:18 ... Instead of entering the credetials on your PC, you use your mobile 18:52:25 ... so you do not disclose any information on the PC 18:52:40 ... which is very useful if you use a computer that you do not trust in an internet cafe, for example 18:53:25 opoto: those are only a few examples of what can be done with this API 18:53:32 ... if you want to see some demos, feel free to ask us 18:53:40 q+ 18:53:50 opoto: of course, this is not something new, there are already some organisations that worked on this 18:54:07 ... in particular the SIM alliance group, to define an Open Mobile API to define a SE API 18:54:15 ... this API has been implemented in several mobile environment 18:54:40 opoto: A similar API has been defined and used in other organisations such as Tizen and Webinos 18:54:52 ... those are Web APIs similar to the one from the SIM Alliance 18:55:03 opoto: those APIs are available in many devices 18:55:14 ... in particular the SIM Alliance one is available in many Android devices 18:55:39 opoto: there are 180 devices released with a SE API 18:55:49 ... but on those devices, it is not a Web API but a native API 18:55:50 q? 18:56:00 opoto: so what we want to do here is to have similar API but for the Web 18:56:18 ... so, what we propose it to start drafting a specification 18:56:33 SE API essentially exposes APDU access as defined by ISO/IEC 7816-4 and widely supported in SIM and smart cards etc. 18:56:37 ... with UC and requirements 18:56:52 -> http://www.nfc.cc/nfc-phones/blackberry-9900-nfc/ BlackBerry 9900 (OS 7.1) Secure Element/NFC 18:57:10 opoto: Tran, from Intel said that he would be volunteer to participate to this specification 18:57:12 -> http://www.blackberry.com/developers/docs/7.0.0api/net/rim/device/api/io/nfc/NFCManager.html BlackBerry 7.0 NFC API 18:57:15 q+ 18:57:25 q? 18:57:29 ack mo 18:57:29 mounir, you wanted to say that we have a payment api/tf for that 18:57:52 -> http://www.w3.org/wiki/Payments_Task_Force W3 Payments Task Force 18:57:55 ack gmandyam 18:58:15 gmandyam: just to clarify my early comments: we know that we need SE access but the question for this group is whether we need to expose this API to third party developers 18:58:38 ... and when I discussed this internally... this was one of the most difficult API to implement internally 18:59:01 ... and when I asked how many developers wanted to use this in a third party application, there was none 18:59:05 ... all users are pre-installed 18:59:22 ... so I am asking you Olivier, what is the demand? 18:59:34 q? 18:59:37 opoto: well... for sure, this API does not exist 18:59:42 ... so no developer use it 18:59:54 ... we are offering something, so it is not easy to know who would use it 19:00:09 - +49.151.629.4.aaaa 19:00:35 Zakim, where is +49? 19:00:35 country code 49 is Germany 19:01:08 + +49.151.629.4.aabb 19:01:09 -[Mozilla] 19:01:11 +[Mozilla] 19:01:14 AAA: this is a chicken and egg problem 19:01:25 s/AAA:/dsuwirya:/ 19:01:29 ... you can't know how many developers use the API if it is not available 19:01:53 ... government, companies, might use this API if it is an available API 19:02:16 ... for public use, it is more for eGov UC like eServices, to pay your taxes, etc. 19:02:31 ... this is an application that would be published by the government for citizens 19:02:34 Zakim, aabb is probably gprintemps 19:02:34 +gprintemps?; got it 19:02:40 Right - I'm calling with German number 19:02:49 Zakim, gprintemps? is gprintemps 19:02:49 +gprintemps; got it 19:02:53 https://www.cibc.com/ca/features/mobile-payment.html Mobile payment with app accessing secure element on SIM card 19:02:59 s/Right - I'm calling with German number// 19:03:10 s|https://www.cibc.com/ca/features/mobile-payment.html|-> https://www.cibc.com/ca/features/mobile-payment.html| 19:03:18 RRSAgent, draft minutes 19:03:18 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html Josh_Soref 19:03:19 ... at the end it is going to be a signed packaged app, it is not a regular app 19:03:30 q? 19:03:49 opoto: this is why we want this work to be done to the sysapps WG 19:03:57 ... we want the applications using this API to be trusted 19:04:22 ... also, we want that only authorised applications can access the SE 19:05:07 We need also a way to receive events fro SE 19:05:30 mounir: you are dodging the question by saying it is a chicken and egg problem 19:05:45 ... you said that there are many native implementations 19:06:01 dsuwirya: this is going to be a niche market 19:06:09 ... Gemalto has interested clients 19:06:14 s/scribe: as agreed/[scribe] as agreed/ 19:06:17 RRSAgent, draft minutes 19:06:17 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 19:06:18 ... it is not a matter of number of developers 19:06:50 All operators will be interested by these APIs 19:06:54 dsuwirya: without this specified, it is not possible to have an application to access the SE 19:07:15 ack dsuwirya 19:07:18 ack dsr 19:07:33 dsr: the workshop regarding payment is happening next year 19:07:56 ... at this point, it sounds likely that we will be using packaged applications to do this 19:08:21 Purpose is not only payment but to have a generic channel to discuss with SEs 19:08:41 it it likely they will use it or it is not likely? 19:09:02 the secure element API would be useful for payment solutions built as sysapps. 19:09:40 scribe: Josh_Soref 19:09:42 scribenick: timeless 19:09:50 mounir: what are member positions on this? 19:09:52 [ Silence ] 19:09:59 mounir: this seems like a niche 19:10:02 ... we have other things to do 19:10:09 ... we should probably focus on other things to do 19:10:15 ... i'd be interested to know who would implement it 19:10:19 ... i doubt mozilla would implement it 19:10:27 ... if people would be interested in implementing it, it might help 19:10:28 rrsagent, draft minutes 19:10:28 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 19:10:35 I forgot to add that secure elements will be important for corporate apps for enterprises. 19:10:47 wonsuk: as the Samsung representative 19:10:48 Why will Mozilla not implement it? 19:10:51 ... we want to support this 19:10:56 ... we already have SE API in Tizen 19:11:00 gmandyam: what does that mean? 19:11:09 gprintemps: I mean, we will not implement it anytime soon 19:11:40 i/gprintemps/scribe: mounir/ 19:11:42 q? 19:12:32 lgombos_ has joined #sysapps 19:12:41 This APIs can also be used by non web os devices 19:13:33 scribe: Josh_Soref 19:13:37 scribenick: timeless 19:13:44 mounir: speaking as Chair 19:13:47 ... if we take this work itme 19:13:52 s/itme/item/ 19:13:59 ... there will be one group working on it, Tizen 19:14:02 ... they'll do it 19:14:12 ... and much later someone will come and say "i completely disagree" 19:14:19 ... i'm trying to save bandwidth for the group 19:14:22 ... we have many things to do 19:14:28 q+ 19:14:52 ... we have many things Mozilla and Tizen are interested in working on 19:14:55 ack gprintemps 19:15:04 gprintemps: I'm discussing w/ manufacturers 19:15:08 ... and also OS providers 19:15:11 ... non web providers 19:15:16 ... not just Tizen/Mozilla 19:15:23 ... but other vendors like Google and Microsoft 19:15:29 ... i'm pretty sure that this API is really useful 19:15:32 ... you cannot 19:15:42 ... it's useful because you can create an application that can run on different OSs 19:15:52 ... the main problem we have is that we have to rebuild our application for each OS 19:16:03 ... HTML5 is the key for having NFC technology working on different OSs 19:16:08 ... w/o a W3 API 19:16:11 ... for access to SE 19:16:30 ... w/o it, we'll never have wallet on WebOS 19:16:31 q+ to say that NFC is another api and that we need other bits before working on SE if interoperability is the important thing 19:17:10 ... w/o it things won't have a thing for iOS/BlackBerry/WebOS 19:17:26 ... as opoto mentioned 19:17:42 ... having the same application on iOS, WP, BlackBerry, WebOS, Firefox, Tizen 19:17:49 ... it's a key for us to develop an app based on NFC 19:17:51 ... not P2P 19:17:53 ... not ... 19:17:58 ... i'm talking about Card Emulation mode 19:18:06 ... all apps based on Card Emulation mode 19:18:16 ... won't be built in HTML5 w/o this 19:18:20 ... the risk is fragmentation 19:18:24 ack mounir 19:18:24 mounir, you wanted to say that NFC is another api and that we need other bits before working on SE if interoperability is the important thing 19:18:24 ... the main risk is fragmentation 19:18:49 mounir: I think W3C is working on NFC in another WG, maybe NC 19:18:51 s/NC/NFC 19:19:01 ... i think SE is below NFC 19:19:11 NFC WG: http://www.w3.org/2012/nfc/ 19:19:14 ... i think we can do NFC w/o defining an SE api 19:19:18 ... Interop is important 19:19:27 ... we want a web application is a web application that works everywhere 19:19:36 ... SE API is quite not the priority 19:19:44 ... if we don't have a runtime that mentions a security model 19:19:50 ... if we don't have a packaged application system 19:20:24 gprintemps: i'm in the NFC group 19:20:38 ... we're only doing P2P and QQQ 19:20:43 s/QQQ/Reader Mode/ 19:20:49 ... but they're scoping out Card Emulation mode 19:21:01 ... in NFC WG we're focusing on Reader-Writer Mode and P2P 19:21:07 ... if W3 wants to handle NFC 19:21:11 ... we want to handle all 3 modes 19:21:16 ... not just Reader-Writer and P2P 19:21:24 ... using NFC for transactions 19:21:27 ... but for opening doors 19:21:32 ... for loyalty cards 19:21:38 ... for them, we need access to the Secure Element 19:21:45 ... it's key because it can contain the application 19:21:50 ... it can contain the ZZQ 19:21:58 ... it's secure 19:22:00 ... it's something we don't have 19:22:09 ... why on the PC, can't you put the credit card in your reader 19:22:12 ... all laptops have readers 19:22:17 ... why can't we put our card in the reader 19:22:27 ... why can't we put the numbers in? 19:22:31 ... for banks it isn't secure 19:22:48 ... this is for bank cards, loyalty cards, etc 19:22:54 ... we need a way to store these in a secure way 19:22:54 q+ to suggest we continue work on use cases and the target developer communities 19:23:00 ... i'm not talking about UICC 19:23:05 ... i'm talking about all SEs 19:23:08 q? 19:23:20 marcosc: does anyone here have a laptop w/ a secure element 19:23:24 dsr: i have one 19:23:38 [ People show marcosc are card reader slot ] 19:23:44 dsr: some systems have card readers too 19:23:49 zolkis has joined #sysapps 19:23:53 ... i'm hearing we don't have consensus 19:23:58 ... but there's interest in looking at UCs 19:24:03 ... and identifying the target commuunity 19:24:34 mounir: i want to see the NFC and Web Payment groups looking forward 19:24:43 ... likely they could specify in those groups if they want those bits 19:24:52 opoto: the NFC does not cover all the UCs 19:25:00 ... #1 that i mentioned was online authentication 19:25:11 ... the scenario that you have a smart card and a pc w/ a reader 19:25:17 ... and you authenticate w/ PKI in your smartcard 19:25:21 ... it's neither payment nor nfc 19:25:39 dsuwirya: the biggest UC is the SIM card access in the mobile 19:25:42 ... PKI usage 19:25:45 q+ to mention corporate provisioning of SIM or microSD cards with enterprise SE applets 19:25:46 ... authentication/signature 19:25:51 ... is not something addressed via NFC 19:25:58 ... that's an app using UUIC directly 19:26:02 ack dsr 19:26:02 dsr, you wanted to suggest we continue work on use cases and the target developer communities and to mention corporate provisioning of SIM or microSD cards with enterprise SE 19:26:06 ... applets 19:26:08 dsr: it isn't juts about NFC 19:26:12 s/juts/just/ 19:26:15 ... for Enterprise 19:26:21 [Marcos impressed by "the future" of computing] :) 19:26:22 ... you could provision apps through the SIM/uSD 19:26:46 s/juts/just/ 19:26:53 wonsuk: we need to gather UCs 19:26:57 ... and gather feedback from members 19:27:03 ... i don't want to reject/pending for this work 19:27:18 RRSAgent, draft minutes 19:27:18 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 19:27:18 +q 19:27:22 s/+q/q+/ 19:27:44 mounir: i don't think we have enough traction to go through the entire process 19:27:52 ... we already have enough issues for the items we're working on 19:28:00 q? 19:28:02 ack marcosc 19:28:16 marcosc: we have a good opportunity for Tizen(Intel, Samsung) to provide implementation feedback 19:28:19 q+ to ask for auth feedback 19:28:25 ... pioneer w/ web tech and then we can learn for free 19:28:31 ... it isn't that people disagree that it's great stuff 19:28:38 ... but getting it to work and showing it working 19:28:43 ... Mozilla doesn't have any IPR 19:28:47 q? 19:28:47 ... there's nothing we can contribute 19:28:53 ... we can provide API design help 19:28:59 ... but it feels early to standardize 19:29:00 Josh_Soref: +1 19:29:08 marcosc: as a web tech, it feels a bit immature 19:29:14 ... we don't know how it's going to work 19:29:24 ... there's potential to do this innovation 19:29:31 ... we should standardize after innovations happen 19:29:32 Josh_Soref: +1 19:29:39 mounir: you mentioned authentication 19:29:44 q? 19:29:48 ... Google, Facebook, Twitter had issues w/ authentication on the web 19:29:50 ack mo 19:29:50 mounir, you wanted to ask for auth feedback 19:29:55 ... do you know if they think it's a solution for this? 19:30:05 opoto: this isn't something we discussed with those players 19:30:07 [ Strike 1] 19:30:10 s/]/ ]/ 19:30:39 mounir: honestly, you should talk to them, and get them (Google, Facebook, ...) to come back and say that they want this 19:30:44 ... everyone would run to implement that 19:30:51 Josh_Soref: +1 19:31:05 opoto: Google/Facebook are big companies 19:31:19 ... but this is likely to be used in corporate or more restricted environments 19:31:32 ... as Gemalto, we know customers are interested in those technologies 19:31:42 ... we have products based on proprietary solutions 19:31:48 ... we'd like to replace them w/ standards based solutions 19:31:59 ... there are governments interested w/ those authentication mechanisms based on web 19:32:04 ... we have products based on this 19:32:20 timeless: w3 does have members who are goverments or represent governments 19:32:31 ... if you can get some of them to appear on the table, we will listen 19:32:32 s/mounir/scribe/ 19:32:33 s/mounir/scribe/ 19:33:19 q? 19:33:36 link? 19:33:46 opoto: we have Intel, Samsung, Gemalto, 19:33:49 http://www.w3.org/Consortium/Member/List 19:34:04 Josh_Soref: there are government members 19:34:11 mounir: we should write a resolution... 19:34:37 ... i feel we should consider later 19:34:44 ... maybe w/ more feedback from NFC and Payment effort 19:34:51 http://www.w3.org/egov/IG/charter-2011 19:34:52 ... and see if we can get more people around the table interested in doing 19:34:55 ... does that sound ok? 19:35:25 dsr: sounds like we need more participants from stakeholders in this group 19:35:32 ... and we'll need more implementations than just Tizen 19:35:48 anssik: on editing 19:35:54 ... i think the editors here aren't editors elsewhere 19:36:01 ... so on resourcing, i don't think you block much 19:36:06 ... so i don't see that as a major issue 19:36:11 ... from a scope PoV 19:36:15 ... i don't think it's a big thing 19:36:21 ... but from priority, i wouldn't be working on that 19:36:26 ... i'll be working on event pages 19:36:35 mounir: obviously, every company can do what it wants w/ its resources 19:36:53 ... if opoto and dtran want to work on it 19:36:57 ... they're welcome to 19:37:08 ... my point is we shouldn't take that spec as an official spec of SysApps 19:37:11 s/spec/draft/ 19:37:17 DTAG can help 19:37:24 ... ala Runtime, where no one had looked at it and given feedback 19:38:17 anssik: how about starting w/ UC and Req 19:38:23 ... marcosc has good experience 19:38:29 marcosc: we have a presentation 19:38:33 kenneth_ has joined #sysapps 19:38:35 anssik: would it help to refine the UCs? 19:38:41 marcosc: i'd prefer they iterate 19:38:50 ... i'm guessing most experience is from Java Apps/UIs 19:38:56 anssik: if you could gather those 19:39:00 marcosc: there might be UI constraints 19:39:04 ... there might be Java interfaces 19:39:11 ... there's all this stuff about Flooding the little chip 19:39:21 ... those are important thing 19:39:31 s/thing/things/ 19:39:40 ... those constraints or whatever that need to be taken into consideration 19:39:48 Josh_Soref: +1 to worrying a *lot* about those constraints 19:39:54 marcosc: you can prototype using 19:40:01 ... you could throw up a web view in android 19:40:10 ... and use the web view to expose the JS object 19:40:13 ... do a prototype on that 19:40:22 mounir: you can do a chrome/firefox extension 19:40:37 marcosc: oh, yeah, do it in Firefox 19:40:46 ... "i'd recommend you do it in Firefox" 19:40:49 [ cough ] 19:40:50 AndroUser has joined #sysapps 19:40:54 opoto: we have experience in Firefox 19:41:00 marcosc: does it expose JS API? 19:41:05 ... you have implementation experience? 19:41:06 opoto: yes 19:41:17 marcosc: that can be enough for standardization 19:41:47 .. we could give you a bit of feedback 19:41:50 s/../.../ 19:41:54 ... that's a good rapid way to do it 19:41:58 ... you could throw up a document 19:42:23 ... you can do that to get it going quickly 19:42:25 q? 19:42:27 ... that would be good 19:42:36 +1 for this direction Marcos suggested to start over 19:43:22 q? 19:43:22 s|http://www.w3.org/egov/IG/charter-2011|-> http://www.w3.org/community/egovernance/ Electronic Governance CG| 19:43:52 How about that Olivier and Tran continue to iterate the use cases and prepare a draft API for review as and when SysApps revieeers become avaialbale 19:44:10 s/revieeers/reviewers/ 19:44:23 s/avaialbale/available/ 19:44:32 RRSAgent, draft minutes 19:44:32 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 19:44:49 +1 for dsr proposal 19:44:56 s|s/juts/just/|| 19:45:19 RESOLUTION: Olivier and Tran should continue to iterate the UCs and prepare a draft specification for review when SysApps reviewers become available 19:45:42 mounir: we're nearly done 19:45:48 ... does anyone have anything to add? 19:46:10 zkis: we were going to talk about Bluetooth/other phase two items? 19:46:27 mounir: we don't have any specs in LC? 19:46:32 marcosc: app: is almost in LC 19:46:36 mounir: at that point, if we add stuff 19:46:41 ... we're just adding work 19:46:46 ... but i don't feel we're going very fast 19:46:50 ... it doesn't seem like a good idea 19:47:04 ... but if someone in the group wants to trade a phase 1 for a phase 2 item 19:47:11 zkis: if there are new people working on them? 19:47:15 marcosc: which new people? 19:47:53 mounir: it's always valuable to have a draft sent 19:47:56 ... that doesn't hurt 19:47:59 ... we can look at it 19:48:02 ... Mozilla has an API 19:48:08 ... it sounds like Google has something 19:48:12 ... if everyone is in sync 19:48:19 ... you had someone next to you working on that 19:48:32 ... does someone @Mozilla/Google have anyone to work w/ you on that? 19:48:42 zkis: another topic we spoke w/ sicking at the last F2F 19:48:47 q+ 19:48:50 ... it sounded like there was interest in standardizing a way 19:49:00 ... how audio/notifications are handled while a call is in place 19:49:08 -gprintemps 19:49:09 ... i have a draft for extending the notification API 19:49:20 ... and a spec for extending output device recognition 19:49:29 q+ Josh_Soref to say HTML is working on extra displays 19:49:37 zkis: mozilla has a draft on this too 19:49:45 ... sicking mentioned this would be interesting to work on that 19:49:52 q+ 19:49:54 ... i have draft specs on it 19:49:58 ... it would fit the charter 19:50:04 ... when should we pull it out/start discussing it 19:50:07 mounir: re the charter 19:50:14 ... i believe if it isn't in the list in the specs that are listed 19:50:19 ... then it isn't in charter 19:50:22 ... IANAL 19:50:32 [ thus it would require rechartering ] 19:50:40 mounir: rechartering is painful 19:50:49 ... you could open a wiki page for things to add for the next charter 19:50:54 ... i know webapps does that 19:51:03 dsr: we can try to recharter anytime we like 19:51:06 ... but it's expensive 19:51:08 ack jungkees 19:51:17 jungkees: in the morning during the runtime discussion 19:51:22 ... we gathered a lot of items/issues 19:51:32 ... i want to volunteer as a coeditor of application/lifecycle events 19:51:36 ... at the beginning of the year 19:51:44 ... i was working on a proposal w/ a similar idea 19:51:52 ... i have the idea, and i'd like to help sort out the issues 19:51:58 ... if it would help, i'd like to 19:52:00 anssik: +1 19:52:02 q? 19:52:06 ack JonathanJ1 19:52:12 ack Josh_Soref 19:52:12 Josh_Soref, you wanted to say HTML is working on extra displays 19:52:55 rrsagent, draft minutes 19:52:55 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 19:52:57 can we have a link of that work ? 19:53:11 Josh_Soref: WebRTC was worrying about additional output devices 19:53:16 ... and realized it was beyond their scope 19:53:19 ... so they spoke w/ HTML 19:53:25 ... who said it was indeed something HTML should do 19:53:34 ... and the work was transferred there 19:53:35 q? 19:53:39 ... no pointer-- sorry 19:53:46 indeed, the work affects HtmlMediaElement 19:54:02 marcosc: i heard notifications 19:54:06 q? 19:54:08 ... that should be sent to WebApps 19:54:09 ack mar 19:54:10 Josh_Soref: +1 19:54:15 q? 19:54:20 marcosc: if you have enhancements for that 19:54:25 ... it would be better to put it there 19:54:31 ... i've thought about similar things 19:54:36 ... it would be useful in Web Notifications 19:54:41 ... it was supposed to support html 19:54:47 ... including video/audio 19:55:02 q? 19:55:15 q? 19:55:41 http://lists.w3.org/Archives/Public/public-html/2013Aug/0104.html 19:55:48 Topic: Next F2F 19:56:06 s|http://lists.w3.org/Archives/Public/public-html/2013Aug/0104.html|-> http://lists.w3.org/Archives/Public/public-html/2013Aug/0104.html Re: Fwd: Proposal for output device selection| 19:56:16 mounir: the next meeting is @TPAC 19:56:20 anssik: was that Th/F? 19:56:26 dsr: i've asked about changing that 19:56:35 ... it may take a few days to find out 19:56:44 mounir: we agreed to try to move the F2F to M/Tu 19:56:49 ... to avoid overlapping w/ WebApps 19:57:00 ... we scheduled to avoid overlapping w/ DAP, but DAP canceled 19:57:02 http://www.w3.org/2013/11/TPAC/#GroupSchedule 19:57:06 ... we'll see the agenda and discuss later 19:57:12 ... thanks everyone 19:57:16 dsr: thanks for hosting us 19:57:17 [ Applause ] 19:57:27 mounir: thanks for scribing 19:57:30 wonsuk: thanks Josh_Soref 19:57:31 [ Applause ] 19:57:50 mounir: thanks Facilities for the Heat 19:57:51 thanks for Josh_Soref +1 19:58:05 RRSAgent, draft minutes 19:58:05 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html timeless 19:58:05 thanks for Josh_Soref +1 19:58:18 rrsagent, draft minutes 19:58:18 I have made the request to generate http://www.w3.org/2013/08/29-sysapps-minutes.html JonathanJ1 19:58:50 RRSAgent, bye 19:58:50 I see 3 open action items saved in http://www.w3.org/2013/08/29-sysapps-actions.rdf : 19:58:50 ACTION: marcosc will contact the dev-rel team at Mozilla to do some dev-outreach [1] 19:58:50 recorded in http://www.w3.org/2013/08/29-sysapps-irc#T17-25-49 19:58:50 ACTION: dsr will contact the dev-rel team at W3C to do some dev-outreach (marcosc recommends contacting Léa Verou) [2] 19:58:50 recorded in http://www.w3.org/2013/08/29-sysapps-irc#T17-26-16 19:58:50 ACTION: mounir will open a Twitter account for sysapps and publish some stuff to get developers attention [3] 19:58:50 recorded in http://www.w3.org/2013/08/29-sysapps-irc#T17-26-45 19:59:01 Zakim, bye 19:59:01 leaving. As of this point the attendees were marcosc, Josh_Soref, anssik, mounir, spoussa, kjwallis_, gmandyam, genelian, zkis, dsr, wonsuk, jungkees, lgombos, Claes, 19:59:01 Zakim has left #sysapps