15:04:29 RRSAgent has joined #exi 15:04:29 logging to http://www.w3.org/2016/03/08-exi-irc 15:04:31 RRSAgent, make logs public 15:04:31 Zakim has joined #exi 15:04:33 Zakim, this will be EXIWG 15:04:33 I do not see a conference matching that name scheduled within the next hour, trackbot 15:04:34 Meeting: Efficient XML Interchange Working Group Teleconference 15:04:34 Date: 08 March 2016 15:04:43 zakim, who is here? 15:04:43 Present: (no one) 15:04:44 On IRC I see RRSAgent, dape, taki, liam, caribou, trackbot 15:05:08 scribe: TK 15:05:14 scribeNick: taki 15:09:05 TOPIC: W3C TPAC 2016 - Will your group meet in Lisbon? 15:10:20 DP: I might also be able to join TPAC 2016. 15:10:35 DP: There is also WoT meeting the same week. 15:10:51 DP: We will need to avoid to clash with WoT meeting. 15:12:30 CB: What will be the status of EXI at that time? 15:13:03 CB: I wonder if we really need a meeting given that we are a small group now. 15:14:47 DP: If we don't meet, do we want to have a breakout session to discuss about the future of EXI? 15:17:14 CB: We need to do more outreach to other people. 15:17:47 CB: We need to justify for the work of EXI2. We need more users. 15:18:22 CB: WoT is IG now. We can move the work and continue there. 15:18:53 CB: Some group have moved from one to another. 15:19:19 CB: Or we can recruit people from other group. 15:20:37 CB: It is hard to predict. We can hold a room for now, and need to think what would be agenda at TPAC. 15:28:31 CB: AC meeting will happen soon. 15:29:10 DP: I will talk to AC on this. 15:29:44 DP: WoT is more interested in what is already there. 15:34:23 TOPIC: EXI for JSON 15:34:52 DP: Schema for JSON. 5th version of json-schema. 15:35:03 New Discussions on GH w.r.t. JSON Schema: https://github.com/json-schema/json-schema/issues/167#issuecomment-193802112 15:36:23 DP: There are some efforts going on at Github to renew JSON schema. 15:39:40 DP: Currently, I have to API. Typed API, and the other creates and reads JSON. 15:39:55 s/have to/have two/ 15:44:02 TOPIC: Canonical EXI 15:45:13 DP: Following xml:space preserve in typed encoding. 15:45:32 DP: We should try to make users aware about the consequence of settings. 15:48:30 DP: In schema-less, we can require implementations to preserve all whitespaces. 15:48:46 https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#whitespaceHandling 15:53:12 TK: What do we do for mixed content whitespaces? 15:55:16 DP: The current rules are simple. It removes whitespaces when xml:space is default. 15:58:21 DP: Do we have any other issues? 15:58:24 https://www.w3.org/2005/06/tracker/exi/issues/raised 15:58:33 https://www.w3.org/2005/06/tracker/exi/issues/open 16:01:31 https://www.w3.org/2005/06/tracker/exi/issues/109 16:01:45 TK: I think issue 109 has been handled already. 16:03:35 TK: 108 is also from JS, and we handled it already. 16:07:23 DP: Issue 100. It is covered in section 4.2.2. 16:09:16 ACTION: DP to check Issue 100 to see Canonical EXI section 4.2.2 properly handles it 16:09:16 Created ACTION-736 - Check issue 100 to see canonical exi section 4.2.2 properly handles it [on Daniel Peintner - due 2016-03-15]. 16:12:38 TK: After we resolve those issues, we can focus on testing. 16:13:57 TOPIC: New EXI 2.0 items 16:14:38 DP: We started creating documents about shared string. 16:15:09 DP: Change to default values for strings. 16:15:38 DP: The number of string entries and length. 16:17:54 DP: ED was pointing to the same issue. FastInfoset seems to be setting a limit. 16:27:23 DP: We should also think about plugging in new compression algorithms. 16:28:26 DP: Google seems to have published one recently. 16:28:40 https://en.wikipedia.org/wiki/Brotli 16:30:16 DB: If you allow variations in standard, we may lose consistency and reliability, also patent policy. 16:37:02 rrsagent, create minutes 16:37:02 I have made the request to generate http://www.w3.org/2016/03/08-exi-minutes.html taki 17:29:30 Zakim has left #exi