14:04:05 RRSAgent has joined #exi 14:04:05 logging to http://www.w3.org/2016/09/13-exi-irc 14:04:07 RRSAgent, make logs public 14:04:07 Zakim has joined #exi 14:04:09 Zakim, this will be EXIWG 14:04:09 ok, trackbot 14:04:10 Meeting: Efficient XML Interchange Working Group Teleconference 14:04:10 Date: 13 September 2016 14:04:18 scribe: TK 14:04:23 scribeNick: taki 14:13:28 brutzman has joined #exi 14:18:18 chair: taki 14:18:31 DP: How Liam and Carine can support us in promoting EXI in W3C at large. 14:18:45 DP: We should find a way how to move on... 14:19:14 DP: Not only technical side. 14:19:44 DB: Working group strategy? 14:20:01 DP: Right. Support from people outside the group. 14:20:23 DB: Commucating our progress. 14:20:39 DP: Make people aware what we are doing and what we have achieved. 14:20:46 Also an opportunity to ask W3C for support where that can help, inviting further member participation, etc. 14:21:10 DP: Let's discuss with Liam first, and first get his opinion on how we progressed. 14:21:46 How to best have this dialog? maybe we should prepare a presentation that summarizes progress and plans 14:22:24 DP: We will want to chat with Liam at TPAC. 14:24:27 https://www.w3.org/2016/09/TPAC/ 14:26:26 https://www.w3.org/2016/09/TPAC/schedule.html looks like you have the room all day Monday-Tuesday 14:27:52 8 hours difference between California and Lisbon time zones 14:30:00 best times for me are Tuesday 1400 or 1300, Lisbon time 14:30:30 ... otherwise I am committed with presentations at local conferences 14:31:47 i can also try earlier on Tuesday - might not be fully awake though! 14:34:41 CB: At TPAC, W3C will announce organizational changes. 14:35:03 CB: will abandon domains. 14:35:27 CB: Chairs can also talk to other chairs. 14:37:01 DP: TPAC is usually a good way to talk to people. 14:38:24 DP: Is there going to be reports in AC meetings from each domain lead? 14:38:56 CB: But there is no domain any more. 14:39:29 brutzman_ has joined #exi 14:39:39 CB: We will have Project management, strategy management, etc. 14:40:15 CB: I saw domains as barriers between groups. 14:43:32 CB: Membership has to become more vocal. 14:44:13 https://www.w3.org/wiki/TPAC/2016/SessionIdeas 14:48:25 TK: Let's ask Liam if he is available Tuesday afternoon to sit down with us for talk, and DB will be able to remotely dial-in. 14:49:43 TOPIC: Canonical EXI 14:50:31 TK: Thank you Carine for making the style change. 14:50:42 TK: I plan to do the final review before TPAC. 14:51:05 DP: Then, we can make publication decision during TPAC, right? 14:51:12 TK: That is a good idea. 14:54:49 [i believe i'll be available on Tuesday afternoon, or can be] 14:55:28 TOPIC: JavaScript support 14:55:59 DP: Ben provided a page that converts JavaScript into JSON. 14:56:24 DP: The generated JSON is verbose. 14:58:19 json schema for Esprima AST, https://github.com/toyatech/esschema 14:58:58 https://github.com/toyatech/esschema/blob/master/esschema.json 14:59:02 DP: JSON schema shown in this page is not up-to-date. 14:59:57 i agree that this is very significant for us. for some time it seemed like Javascript compression was out of reach... however that work maps arbitrary Javascript -> JSON by expressing the output of a compiler parse tree 15:02:28 Of related interest: Brendan Eich (initial developer of Javascript) blog, From ASM.JS to WebAssembly https://brendaneich.com/2015/06/from-asm-js-to-webassembly/ 15:02:52 ... Don McGregor was showing me that yesterday 15:03:41 if nothing else, we can conclude at this point that compression of Javascript is an important topic to continue considering 15:05:15 Web Assembly Community Group https://www.w3.org/community/webassembly/ 15:06:38 "The mission of this group is to promote early-stage cross-browser collaboration on a new, portable, size- and load-time-efficient format suitable for compilation to the web." (661 participants) 15:08:46 just posted an initial draft - Candidate topics for EXI strategy summary at TPAC https://lists.w3.org/Archives/Member/member-exi-wg/2016Sep/thread.html 15:10:51 of note: significant progress 2016, OWP strategy is clearly achievable in coming year, and pursuit of XML Security strategy is now actionable 15:11:47 also of note: WoT support also possible, if we start measuring performance and power savings it may become quite significant 15:12:29 DP: I am more concerned with how to make us more visible. 15:13:22 http://www.w3.org/2005/06/tracker/exi/actions/729 15:13:22 issue: EXI remains a well-kept secret, major progress is occurring despite minimal participation by members and public. 15:13:22 Created ISSUE-119 - Exi remains a well-kept secret, major progress is occurring despite minimal participation by members and public.. Please complete additional details at . 15:13:55 oops! didn't intentionlly create that issue, but maybe it is a good idea anyway 8) 15:14:51 TK: We can make a progress on action action-729 15:15:55 s/intentionlly/intentionally/ 15:16:09 TK: We can discuss how to finalize EXI4JSON work. 15:17:41 candidate rename issue 119, Publicizing EXI capabilities and opportunities 15:17:52 ... or we can delete it 15:18:18 ... but if we keep it, we can say "oh right, telling everyone about EXI was an accident" 8) 15:18:38 ... but we did it anyway 8) 15:21:51 i updated issue 119, we can look at it again next time. https://www.w3.org/2005/06/tracker/exi/issues/119 15:23:27 DP: Outreach is an important topic at TPAC. 15:23:41 DP: For example, measurement document. 15:24:51 colleagues: how would you like this prepared for TPAC? might a brief slideset help? 15:29:40 feel free to call me for TPAC session, my cell phone will be nearby. dreaming of EXI! :) 15:30:42 rrsagent, create minutes 15:30:42 I have made the request to generate http://www.w3.org/2016/09/13-exi-minutes.html taki