HTTP/2 200 date: Wed, 08 Oct 2025 23:29:28 GMT content-type: text/plain content-length: 2295 cf-ray: 98b96ba41d9bc1f7-BLR content-location: 22-exi-irc.txt vary: negotiate,accept,accept-charset,Accept-Encoding,Origin tcn: choice last-modified: Tue, 22 Nov 2016 23:43:15 GMT etag: "1433-541ec5607eac0;602036a8fbef4 cache-control: max-age=21600 expires: Thu, 09 Oct 2025 05:29:28 GMT content-encoding: gzip access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98b96ba41d9bc1f7 strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: BYPASS accept-ranges: bytes set-cookie: __cf_bm=c.iYAo_yUmzUGLVGaHE9LDX8E8yyACLn7Oql1Kt3Zsw-1759966168-1.0.1.1-bk3ZEHBsBv.j3ar3zM9oNSZFcErHzHb9NPporMoQSpJg9QWYHgQhNYm8VR6MJ8ZuFw6nBjjX4iOMGB2YU.PkhmqnoZPhQa5rIxhfXLOA0oc; path=/; expires=Wed, 08-Oct-25 23:59:28 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare alt-svc: h3=":443"; ma=86400 18:32:07 RRSAgent has joined #exi 18:32:07 logging to https://www.w3.org/2016/11/22-exi-irc 18:32:09 RRSAgent, make logs public 18:32:09 Zakim has joined #exi 18:32:11 Zakim, this will be EXIWG 18:32:11 ok, trackbot 18:32:12 Meeting: Efficient XML Interchange Working Group Teleconference 18:32:12 Date: 22 November 2016 18:40:58 am here, trying to connect 18:43:22 CB: Web Assembly is currently a community group. 18:43:39 CB: Currently, not a WG. 18:43:57 DP: They managed to get into many browsers. 18:44:28 CB: Not many JavaScript comminity are using it now 18:45:19 DP: 800 people are in the community group. 18:45:59 DP: Samsung has JavaScript engine that has very small footprint. 18:46:13 DP: It can be deployed to tiny devices. 18:46:38 DP: Ben Titzer from google presented Web Assembly in WoT call. 18:48:18 TOPIC: EXI Renaming 18:48:39 TK: Liam updated our public page. 18:48:49 DP: CB also made update. 18:49:14 CB: I also updated member-only page. 18:49:22 https://www.w3.org/Member/Mail 18:50:42 CB: If you notice anywhere else that mentions old name, please let me know. 18:51:34 DP: We should announce that we change the name. 18:51:44 wondering if W3C Communications might get us some EXI shirts, or hats? Not too small please... 18:52:56 TOPIC: Canonical EXI 18:54:05 TK: I setup my eclipse environment. I will implement the parameters today. 18:54:39 DP: I plan to implement some missing features in EXIficient soon. 18:56:04 TOPIC: W3C Blog 18:57:15 n8s has joined #exi 18:57:56 DP: One comment was to move the link to EXI4CSS presentation up-front. 18:58:16 DP: Another was about "EXI to JSON" typo. 18:59:57 https://www.w3.org/blog/?p=15827&shareadraft=baba15827_583495a2ddc34 19:01:15 sentence about the name change should be updated 19:01:18 DB: Could we ask for a logo? 19:01:49 DP: We created a logo in WoT. We had a pushback. 19:02:20 DP: Therefore, I would say it is unlikely to happen. 19:02:48 WoT is not yet a technology, EXI is a REC, we might get a different answer 19:02:51 it's worth asking 19:03:43 DB: We should still be able to ask for one. 19:04:59 CB: I will ask. We have created for logo for HTML, CSS, etc. Also for some initiatives. 19:05:15 CB: I am going to ask. 19:05:53 DP: I will not wait for the logo before publishing the blog. 19:06:36 Link for implementaions: https://www.w3.org/XML/EXI/#implementations 19:07:54 change "We encourage you to take a look" to "We encourage everyone to take a look" 19:08:35 "Power-sensitive EXI efficiencies" sentence likely better as 4th bullet in preceding list 19:09:37 "Multiple implementations of EXI are available" (with url added) can then be lead sentence for last paragraph 19:15:57 perhaps add "Public" to "Participation and feedback are welcome!: 19:16:07 s/!:/!"/ 19:18:28 might help to add authors and date to cover slide for CSS-EXI https://www.w3.org/XML/EXI/outreach/2016/11/css.html#cover (as you wish) 19:22:06 perhaps "leave a comment in the blog" to "leave a comment here in the blog 19:22:41 s/here in the blog/here in the blog"/ 19:25:16 An early blog post by Cariine: "EXI Stance," 25 October 2007, https://www.w3.org/blog/2007/10/exi-stance 19:26:53 pretty cool that we achieved everything you said in that post! 19:27:43 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 TK: "will eventually stand for" needs update... perhaps "now stands for" 19:31:47 sure, go ahead 19:33:20 maybe "efficient stream of parse events" to "efficient data stream of parse events" 19:34:13 and then "and can have noticeable" to "that can have noticeable" 19:38:04 DP: 3 2 1 post! 19:38:08 https://www.w3.org/blog/2016/11/efficient-representation-for-web-formats/ 19:42:02 https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html 19:44:26 brutzman has joined #exi 19:44:40 https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html 19:48:21 TOPIC: Extended String 19:50:02 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 rrsagent, create minutes 19:58:26 I have made the request to generate https://www.w3.org/2016/11/22-exi-minutes.html taki 20:31:33 n8s has joined #exi 20:38:19 Zakim has left #exi 21:36:23 n8s has joined #exi 22:03:27 n8s has joined #exi 22:27:45 n8s has joined #exi 23:41:15 taki has left #exi