HTTP/2 200 date: Thu, 16 Oct 2025 14:13:59 GMT content-type: text/plain content-length: 1898 cf-ray: 98f828f12a51741b-BLR content-location: 15-exi-irc.txt vary: negotiate,accept,accept-charset,Accept-Encoding,Origin tcn: choice last-modified: Tue, 15 Dec 2015 18:21:15 GMT etag: "fd9-526f3dae67cc0;52b2e0b15befc cache-control: max-age=21600 expires: Thu, 16 Oct 2025 20:13:59 GMT content-encoding: gzip access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98f828f12a51741b 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=IfAw3uZMJEPoh9QmMmOfrND3.iJ_towFVXZIxADlE7g-1760624039-1.0.1.1-gMQBn13y2zpqvzTl8E2hilb9Yp2xurcEDTivvKACX.g2LrxtJ.Dxy526xoog4x5UO023HfilFpRylom01lsAJtEg4TTJRj9KsaUD0qQ2Ebo; path=/; expires=Thu, 16-Oct-25 14:43:59 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare alt-svc: h3=":443"; ma=86400 15:00:38 RRSAgent has joined #exi 15:00:38 logging to https://www.w3.org/2015/12/15-exi-irc 15:00:40 RRSAgent, make logs public 15:00:40 Zakim has joined #exi 15:00:42 Zakim, this will be EXIWG 15:00:42 I do not see a conference matching that name scheduled within the next hour, trackbot 15:00:43 Meeting: Efficient XML Interchange Working Group Teleconference 15:00:43 Date: 15 December 2015 15:00:45 zakim, this is exi 15:00:45 got it, taki 15:04:42 dape has joined #exi 15:07:23 scribe: TK 15:07:29 scribeNick: taki 15:08:02 TOPIC: Plans for telecons during holiday season 15:08:12 TK: Next telecon will be on Jan 12. 15:09:01 DP: Javier D. Fernández joined the WG. 15:09:26 DP: From University of Austria. 15:09:39 DP: He is interested in RDF representation. 15:11:48 DP: I did take a look at the format. (HDT? or both?) It is very much aligned with EXI strategy. 15:13:05 DP: One is a submission to W3C, I believe. 15:14:50 TOPIC: EXI for JSON 15:15:31 DP: I planned to update the document to prepare for review by the group for the first working draft. 15:16:13 CB: Thursday will the last day for publication this year. 15:17:02 DP: I will finish the draft this week. Don said he was going to take a look. Review by Jan 12 will be ok. 15:17:09 CB: Sounds good. 15:17:48 TOPIC: Canonical EXI 15:19:27 TOPIC: Re: Support for Canonical EXI interoperability test in TTFMS 15:21:09 DP: Header allows DTRM. 15:24:23 TK: User's EXI datatype that permits empty string also needs to be mentioned. 15:27:35 DP: The more you have to specify, the less good solution is. You have to process empty CH when the EXI datatype permits empty string. 15:31:33 TK: I will summarize the two proposals, asking the public which of the two is favorable. 15:32:45 TOPIC: Whitespace preservation mode 15:36:31 DP: Currently, we are using the rules defined by XBC working group. 15:39:01 DP: If you want that behaviour, you can put xml:space on the root element. 15:41:09 DP: We should try to limit the number of variations. 15:48:15 DP: Should we have a section about whitespace handling? 15:49:50 TK: Yes, I think we need to specify whitespace handling. 15:50:31 TOPIC: ACTION-732: Investigate whether ecma's json spec is more appropriate to make a reference to or not 15:53:26 CB: I suggest we use RFC. 15:53:46 https://www.ecma-international.org/publications/standards/Ecma-404.htm 15:55:42 DP: Wikipedia says ECMA is minimal whereas RFC provides semantics and security aspects. 15:57:07 CB: We should use most recent and most recent one, which is the one from IETF. 15:58:06 TK: So, the group thinks we should use RFC for referencing JSON. 15:59:01 TOPIC: ISSUE-110: What to do with xml:space being preserved in strict mode 16:03:59 DP: If you have an element type-castable and nillable, in strict mode, you can't do both. 16:06:22 TK: I think best practice is to use default-schema mode when you deal with documents that use xml:space="preserve". 16:10:28 DP: Preservation of prefixes, for example. Qualified names are encoded as strings. 16:16:38 DP: In canonical EXI, we should mention it. But we should keep track of those issues, and have those mentioned somewhere. 16:19:36 DP: Appendix section of the spec. Or best practice document is another choice. 16:22:08 https://www.w3.org/TR/exi/#addingProductionsStrict 16:30:47 TK: Do we want to update the spec to mention that in the errata of the core spec. 16:33:36 TK: I am going to add it in the errata. 16:40:54 rrsagent, create minutes 16:40:54 I have made the request to generate https://www.w3.org/2015/12/15-exi-minutes.html taki 17:24:45 Zakim has left #exi 18:18:45 liam has joined #exi