18:32:07 <RRSAgent> RRSAgent has joined #exi
18:32:07 <RRSAgent> logging to http://www.w3.org/2016/11/22-exi-irc
18:32:09 <trackbot> RRSAgent, make logs public
18:32:09 <Zakim> Zakim has joined #exi
18:32:11 <trackbot> Zakim, this will be EXIWG
18:32:11 <Zakim> ok, trackbot
18:32:12 <trackbot> Meeting: Efficient XML Interchange Working Group Teleconference
18:32:12 <trackbot> Date: 22 November 2016
18:40:58 <brutzman> am here, trying to connect
18:43:22 <taki> CB: Web Assembly is currently a community group.
18:43:39 <taki> CB: Currently, not a WG.
18:43:57 <taki> DP: They managed to get into many browsers.
18:44:28 <taki> CB: Not many JavaScript comminity are using it now
18:45:19 <taki> DP: 800 people are in the community group.
18:45:59 <taki> DP: Samsung has JavaScript engine that has very small footprint.
18:46:13 <taki> DP: It can be deployed to tiny devices.
18:46:38 <taki> DP: Ben Titzer from google presented Web Assembly in WoT call.
18:48:18 <taki> TOPIC: EXI Renaming
18:48:39 <taki> TK: Liam updated our public page.
18:48:49 <taki> DP: CB also made update.
18:49:14 <taki> CB: I also updated member-only page.
18:49:22 <caribou> https://www.w3.org/Member/Mail
18:50:42 <taki> CB: If you notice anywhere else that mentions old name, please let me know.
18:51:34 <taki> DP: We should announce that we change the name.
18:51:44 <brutzman> wondering if W3C Communications might get us some EXI shirts, or hats?  Not too small please...
18:52:56 <taki> TOPIC: Canonical EXI
18:54:05 <taki> TK: I setup my eclipse environment. I will implement the parameters today.
18:54:39 <taki> DP: I plan to implement some missing features in EXIficient soon.
18:56:04 <taki> TOPIC: W3C Blog
18:57:15 <n8s> n8s has joined #exi
18:57:56 <taki> DP: One comment was to move the link to EXI4CSS presentation up-front.
18:58:16 <taki> DP: Another was about "EXI to JSON" typo.
18:59:57 <caribou> https://www.w3.org/blog/?p=15827&shareadraft=baba15827_583495a2ddc34
19:01:15 <caribou> sentence about the name change should be updated
19:01:18 <taki> DB: Could we ask for a logo?
19:01:49 <taki> DP: We created a logo in WoT. We had a pushback.
19:02:20 <taki> DP: Therefore, I would say it is unlikely to happen.
19:02:48 <caribou> WoT is not yet a technology, EXI is a REC, we might get a different answer
19:02:51 <caribou> it's worth asking
19:03:43 <taki> DB: We should still be able to ask for one.
19:04:59 <taki> CB: I will ask. We have created for logo for HTML, CSS, etc. Also for some initiatives.
19:05:15 <taki> CB: I am going to ask.
19:05:53 <taki> DP: I will not wait for the logo before publishing the blog.
19:06:36 <brutzman> Link for implementaions: http://www.w3.org/XML/EXI/#implementations
19:07:54 <brutzman> change "We encourage you to take a look" to "We encourage everyone to take a look"
19:08:35 <brutzman> "Power-sensitive EXI efficiencies" sentence likely better as 4th bullet in preceding list
19:09:37 <brutzman> "Multiple implementations of EXI are available" (with url added) can then be lead sentence for last paragraph
19:15:57 <brutzman> perhaps add "Public" to "Participation and feedback are welcome!:
19:16:07 <brutzman> s/!:/!"/
19:18:28 <brutzman> might help to add authors and date to cover slide for CSS-EXI http://www.w3.org/XML/EXI/outreach/2016/11/css.html#cover (as you wish)
19:22:06 <brutzman> perhaps "leave a comment in the blog" to "leave a comment here in the blog
19:22:41 <brutzman> s/here in the blog/here in the blog"/
19:25:16 <brutzman> An early blog post by Cariine: "EXI Stance," 25 October 2007, https://www.w3.org/blog/2007/10/exi-stance
19:26:53 <brutzman> pretty cool that we achieved everything you said in that post!
19:27:43 <brutzman> Chris Lilley comment on that blog post: "Its just the tokeniser part that has to change, surely. The same tokens are being matched (elements, attributes, etc), the same DOM built. So instead of two parsers, its more like one parser with two possible input formats."
19:28:50 <brutzman> TK: "will eventually stand for" needs update... perhaps "now stands for"
19:31:47 <caribou> sure, go ahead
19:33:20 <brutzman> maybe "efficient stream of parse events" to "efficient data stream of parse events"
19:34:13 <brutzman> and then "and can have noticeable" to "that can have noticeable"
19:38:04 <brutzman> DP: 3 2 1 post!
19:38:08 <brutzman> https://www.w3.org/blog/2016/11/efficient-representation-for-web-formats/
19:42:02 <dape> https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html
19:44:26 <brutzman> brutzman has joined #exi
19:44:40 <dape> https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html
19:48:21 <taki> TOPIC: Extended String
19:50:02 <taki> DP: I noticed that the issue of EXI is that between EXI and GZIP is not big. Newer compression scheme are emerging, too.
19:58:26 <taki> rrsagent, create minutes
19:58:26 <RRSAgent> I have made the request to generate http://www.w3.org/2016/11/22-exi-minutes.html taki
20:31:33 <n8s> n8s has joined #exi
20:38:19 <Zakim> Zakim has left #exi
21:36:23 <n8s> n8s has joined #exi
22:03:27 <n8s> n8s has joined #exi
22:27:45 <n8s> n8s has joined #exi
23:41:15 <taki> taki has left #exi