14:01:32 RRSAgent has joined #exi 14:01:32 logging to http://www.w3.org/2016/10/04-exi-irc 14:01:34 RRSAgent, make logs public 14:01:34 Zakim has joined #exi 14:01:36 Zakim, this will be EXIWG 14:01:36 ok, trackbot 14:01:37 Meeting: Efficient XML Interchange Working Group Teleconference 14:01:37 Date: 04 October 2016 14:03:34 dape has joined #exi 14:09:43 brutzman has joined #exi 14:13:21 https://en.wikipedia.org/wiki/25_de_Abril_Bridge 14:20:01 We discussed TPAC topics 14:20:24 We discussed EXI renaming, Taki's point to avoid confusion is well taken 14:21:18 Carinne's suggested name of EXI = Efficient eXtensible Interchange = Efficient Extensible Interchange sounds good to attendees 14:21:34 s/Carinne/Carine/ 14:23:21 DB: We should ask the public what they think about WG name change idea. 14:23:25 (discussion) can/should we change? we could pose this to exi-member or exi-public list for possible comment 14:24:04 or related interest: here is our wikipedia page https://en.wikipedia.org/wiki/Efficient_XML_Interchange 14:24:19 s/or related/of related/ 14:25:21 likely we should ask Liam (it was his idea) and perhaps other W3C leadership 14:25:55 ... since we all want the rationale and messaging about a possible renaming to make sense 14:29:53 ACTION: CB to check whether it is feasible to change the WG name 14:29:54 Created ACTION-742 - Check whether it is feasible to change the wg name [on Carine Bournez - due 2016-10-11]. 14:30:57 DB: We may need to improve wikipedia page about EXI 14:31:37 DP: We can put a note there as well, and they will catch up. 14:32:18 ACTION: DB to improve Wikipedia description about EXI 14:32:18 Created ACTION-743 - Improve wikipedia description about exi [on Don Brutzman - due 2016-10-11]. 14:37:03 DP: I can prepare what we should present to CSS WG for what we did so far. 14:39:37 DP: I talked to one person who was leading security activity. We should keep talking to them. I could not join their meetings. 14:42:40 DP: We discussed in TPAC that if we provide support for CSS, JavaScript targeting browsers, it will make it easier to support other things such as HTML5. 14:50:15 TOPIC: Telecon time 14:52:16 (that is an interval) 14:54:37 i just belatedly posted some simple editorial comments about Canonical EXI and EXI4JSON https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0005.html 14:55:24 RESOLUTION: From next week 10/11, telecon starts at 7:30pm (Europe), 10:30am (US Pacific). 14:55:56 these are simple and do not need to delay any decision regarding publication - editor's choice 14:59:28 TOPIC: Canonical EXI 15:00:35 TK: Does everybody agree to ask to publish Canonical EXI as Canididate Recommendation? 15:00:59 DP: I do. 15:01:04 TK: I do, too. 15:01:10 +1 15:01:41 +1 15:02:37 RESOLUTION: The group decided to ask W3C to promote Canonical EXI as Candidate Recommendation, after incorporating several editorial stuff discussed today. 15:05:58 looking ahead: Taki, I plan to be in your neighborhood 19-20 OCT at Samsung for the W3C Workshop on Web & Virtual Reality 15:06:09 https://www.w3.org/2016/06/vr-workshop/ 15:06:17 Participant position statements are available at https://www.w3.org/2002/09/wbs/1/vr-workshop/results 15:06:35 Web3D Consortium is adding EXI plus geometric compression as an efficient binary encoding for X3D, Extensible 3D Graphics international standard. 15:07:43 The combinataion of EXI compactness/performance along with potential for XML Security compatibility will be important in this domain. 15:09:53 it may be that everyone is so "headset happy" that they don't care about performance or privacy, we shall see! 8) 15:17:15 list of expected participants https://www.w3.org/2016/06/vr-workshop/participants.html 15:22:07 s/combinataion/combination/ 15:25:29 TK: we will meet at the later time next week. 15:25:57 rrsagent, create minutes 15:25:57 I have made the request to generate http://www.w3.org/2016/10/04-exi-minutes.html taki 16:01:55 Zakim has left #exi