14:03:39 RRSAgent has joined #exi 14:03:39 logging to http://www.w3.org/2016/05/26-exi-irc 14:03:41 RRSAgent, make logs public 14:03:41 Zakim has joined #exi 14:03:43 Zakim, this will be EXIWG 14:03:43 ok, trackbot 14:03:44 Meeting: Efficient XML Interchange Working Group Teleconference 14:03:44 Date: 26 May 2016 14:05:02 dape has joined #exi 14:12:19 scribe: TK 14:12:23 scribeNick: taki 14:12:27 TOPIC: EXI4JSON 14:13:20 DP: I reflected the discussed points in the latest editor's draft. 14:14:19 DP: You need to surround with key elements. 14:14:57 DP: If it is in empty namespace, you need to create key construct for XML to JSON conversion. 14:16:34 DP: key in 3.2.8 needs to be quoted. 14:17:28 DP: For JSON to EXI transformation, if it is the value of a JSON key/value pair. 14:20:21 DP: We don't change the schemaId. I described in section 1.1 "Warning". 14:21:20 DP: DB also was concerned about structure change. 14:23:15 TK: I will ask DB to review EXI4JSON latest change. 14:24:01 CB: We use the same XSLT across all the documents. 14:24:20 CB: We don't need to fix it individually. 14:24:43 DP: I also fixed XLST for the new style. 14:25:22 CB: If you jump to the TOB... 14:26:00 CB: I will compare with other specs, and see how we can fix the problem. 14:28:23 DP: Example 5-1 also look strange. We should be able to fix it easily. 14:29:51 CB: They will mandate HTML5. 14:30:47 https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.w3.org%2FXML%2FEXI%2Fdocs%2Fformat%2Fexi.html 14:33:11 TOPIC: Canonical EXI 14:34:01 TOPIC: Communicating EXI-C14 options 14:35:11 DP: JS would integrate EXI C14N with other EXI options. 14:36:18 DP: I think we started with using URL because Canoncal XML was using that methodology. 14:36:56 DP: If we adopt this new approach, the URL is a single one. 14:41:05 DP: Section 2 needs to add more, and point to D.2. 14:42:50 TK: I also think JS's suggestion makes sense. 14:52:31 DP: Why do we need omitOptionsDocument attribute? 14:53:39 TK: options presence bit is just a bit, not describable. 14:59:57 DP: You want to warn users that sender and receiver need to use the same schema information regardless whether schemaId is there or not. 15:01:06 DP: I think schemaId with value nil and empty string, we should be able to say MUST. 15:01:41 DP: I will reply to TK's comment, with this addition. 15:04:23 DP: When utcTime is not there, we don't do anything. 15:05:24 DP: And when it is present, we do the normalization. 15:17:52 DP: Regarding ISSUE-95, we need to describe best practices. 15:28:54 TOPIC: EXI2 15:47:56 rrsagent, create minutes 15:47:56 I have made the request to generate http://www.w3.org/2016/05/26-exi-minutes.html taki 16:14:29 Zakim has left #exi