HTTP/2 200 date: Tue, 07 Oct 2025 09:11:23 GMT content-type: text/plain content-length: 3273 cf-ray: 98ac454ee9c28cf1-BLR content-location: 23-exi-irc.txt vary: negotiate,accept,accept-charset,Accept-Encoding,Origin tcn: choice last-modified: Tue, 23 Aug 2016 16:12:33 GMT etag: "1f6d-53abf6ea49e40;53e1a7403bad6 cache-control: max-age=21600 expires: Tue, 07 Oct 2025 15:11:23 GMT content-encoding: gzip access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98ac454ee9c28cf1 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=qb1tpX.vWutD6vs7R8VSzbzNCH01VAxFWEESVT4UGMc-1759828283-1.0.1.1-9b9OMBY88L2Vuj54.E9Z8ubUXpA8rYtlyNFZEQPvJEx8xiyB_.W.RSaIsYX5IsvhGZFw0evbJ34D8PlsHaiGH60j4gzLe3l_fEKTUV4YWKI; path=/; expires=Tue, 07-Oct-25 09:41:23 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare alt-svc: h3=":443"; ma=86400 14:03:34 RRSAgent has joined #exi 14:03:34 logging to https://www.w3.org/2016/08/23-exi-irc 14:03:36 RRSAgent, make logs public 14:03:36 Zakim has joined #exi 14:03:38 Zakim, this will be EXIWG 14:03:38 ok, trackbot 14:03:39 Meeting: Efficient XML Interchange Working Group Teleconference 14:03:39 Date: 23 August 2016 14:03:41 dape has joined #exi 14:07:57 brutzman has joined #exi 14:09:57 scribe: TK 14:10:03 scribeNick: taki 14:11:10 TOPIC: EXI4JSON 14:11:27 https://www.w3.org/TR/2016/WD-exi-for-json-20160823/#toc 14:11:43 https://www.w3.org/TR/2016/WD-exi-for-json-20160823/ 14:13:03 DP: We might want to inform the public about this publication. 14:14:41 DP: I will send a note to the list in a couple of days. I will need to to some implementation in the meantime. 14:16:00 ACTION: DP to notify the public list about EXI4JSON second publication 14:16:00 Created ACTION-737 - Notify the public list about exi4json second publication [on Daniel Peintner - due 2016-08-30]. 14:16:04 brutzman has joined #exi 14:16:39 when link to updated EXI4JSON draft is available, we also want to update EXI public page https://www.w3.org/XML/EXI/ 14:18:44 DP: We now allow for dedicated schemas. 14:19:50 DP: I have not seen any updates in JSON schema github issue. 14:20:09 DB: They are working on draft 5. 14:20:50 https://github.com/json-schema-org/json-schema-spec/issues/13 14:21:10 am checking status further... the JSON Schema work can be found at https://github.com/json-schema-org/json-schema-spec 14:21:37 with background information at https://json-schema.org 14:22:54 DP: Let's wait and see if there are going to be any updates. 14:24:04 DB: They are working on stuff. I will post a link. 14:24:27 Unanswered status: "What does it take to get the JSON-Schema specification adopted by an IETF working group?" https://github.com/json-schema-org/json-schema-spec/issues/27 14:24:59 maybe this standards stuff is hard? someone has to do work... 14:25:44 DP: IETF is driven more by people. 14:26:34 Roger Costello asked the same question in 2014: https://groups.google.com/forum/#!topic/json-schema/DIRRlx2w_7U 14:27:26 Latest version at IETF remains v4 https://tools.ietf.org/html/draft-zyp-json-schema-04 14:28:48 DB: We took a look at version 5 in X3D community. 14:29:26 This expired in 2013. Nevertheless it does work, we have tested v4 extensively in the past 8 months for X3D JSON encoding. There is email on the site for JSON Schema v5 progress but nothing definitive. 14:29:49 s/look at version 5/look at version 4/ 14:30:43 Given that it works, but absent any other effort or progress, I think it is worth EXI listing it as informative. 14:33:14 DP: The next EXI4JSON might want to take a look at how we support custom schema. 14:33:31 DP: We need to decide what's the best approach. 14:34:22 Question https://www.w3.org/TR/2016/WD-exi-for-json-20160823/ is now working for me, is it stable? 14:36:34 DB: I will post to issue #13 (in JSON schema discussion) tomorrow. 14:36:49 https://github.com/json-schema-org/json-schema-spec/issues/13 14:39:16 TOPIC: Canonical EXI 14:41:37 DP: We also need to make it HTML5 compatible. 14:42:08 DP: XML schema link to options document is currently missing. 14:42:35 DP: Carine has access to EXI spec location, where we plan to put the schema. 14:44:53 TK: CB will probably comes back next week. 14:46:22 DP: The last time we discussed, I recalled CB saying that publication step rule has changed? 14:46:42 TK: I think last call and CR are now one together. 14:47:52 DP: We integrated all comments from DB, JS, TK. 14:48:01 DP: Resolved all issues. 14:49:29 There is a typo in action 713 for you Daniel, "securit" https://www.w3.org/2005/06/tracker/exi/actions/713 14:50:50 DB: We have action ACTION-713. 14:50:55 https://www.w3.org/2005/06/tracker/exi/actions/713 14:51:18 DP: Once we get to CR, we look into implementations. 14:52:35 Given imminent publication of EXI C14N, wondering if it is time to approach XML Security folks, perhaps discussion at TPAC https://www.w3.org/2016/09/TPAC/ 14:53:04 https://www.w3.org/2016/09/TPAC/schedule.html 14:53:21 DP: there is Web Security IG and Web Application Security WG 14:54:29 https://lists.w3.org/Archives/Member/member-xmlsec/ 14:54:34 Web Security IG is Monday afternoon, https://www.w3.org/2016/09/TPAC/schedule.html#mon 14:54:37 https://lists.w3.org/Archives/Public/public-xmlsec/ 14:56:04 https://www.w3.org/2011/webappsec/ 14:56:09 also Web Application Security WG on Thursday afternoon https://www.w3.org/2016/09/TPAC/schedule.html#thu 14:57:44 public-xmlsec list is active, member-xmlsec list has been inactive for 2 years 15:00:33 might we discuss our long-term strategy regarding XML Security parallels next week, perhaps prepare a summary for that community and potential TPAC discussions 15:01:12 example topics: applying XML Signature and XML Encryption to EXI documents 15:01:35 s/applying/adapting and applying/ 15:03:38 reference E.1 Signature Processing Steps https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#signatureProcessingSteps etc. 15:04:31 DB: Do we have security considerations for either of the specs? 15:05:12 we might also need a section for Security Considerations in either of our active drafts? that section is requirement in IETF RFCs, not sure about W3C requirements... 15:05:25 DB: One requirement of IETF is to have security consideration section in the spec. 15:06:43 we might do well to consider such sections in the next versions of these drafts. 15:07:47 TK: F.2 Internet Media Type in EXI spec discusses security consideration. 15:08:06 --> https://www.w3.org/TR/exi/#internetMediaType 15:10:15 TOPIC: EXI for CSS 15:11:27 DP: I tried to validate CSS. I used CSS parser, and fixed errors in css. 15:13:22 https://github.com/EXIficient/exificient-for-css/blob/master/data/wsj.css#L445-L445 15:17:56 wondering, might stylesheet.xsd be renamed as exi4css.xsd perhaps? 15:22:31 DP: I know many people use CSS minifiers. 15:24:02 --> https://yui.github.io/yuicompressor/ 15:26:46 http compression example: Accept-Encoding: gzip, deflate 15:28:22 https://www.w3.org/TR/exi-best-practices/#http-content-negotiation 15:28:47 just created exi4css schema documentation using XML Spy and posted it to the member-exi thread 15:32:29 YUI Compressor documentation reference "Minification v Obfuscation" says that "After minifying or obfuscating, you should GZIP." https://yuiblog.com/blog/2006/03/06/minification-v-obfuscation/ 15:33:18 So it will be interesting in the test quite to compare source .css, exi4css, YUI compression, and exi4css of YUI compression 15:34:13 btw that documentation reference also says "GZIP can further reduce the size of the program. GZIP is so effective that the difference in the efficiency between minification and obfuscation becomes insignificant." 15:35:56 i think it is important to continue with this great work. it will be great to compress all formats in the Open Web Platform (OWP) using EXI. 15:37:16 TK: WebAssembly is working on JavaScript in binary form. 15:38:03 thanks for another great meeting! 15:40:16 rrsagent, create minutes 15:40:16 I have made the request to generate https://www.w3.org/2016/08/23-exi-minutes.html taki 16:10:32 Zakim has left #exi