15:03:26 RRSAgent has joined #exi 15:03:26 logging to http://www.w3.org/2016/01/12-exi-irc 15:03:28 RRSAgent, make logs public 15:03:28 Zakim has joined #exi 15:03:30 Zakim, this will be EXIWG 15:03:30 I do not see a conference matching that name scheduled within the next hour, trackbot 15:03:31 Meeting: Efficient XML Interchange Working Group Teleconference 15:03:31 Date: 12 January 2016 15:07:18 present: DP, TK, CB, JavierF 15:09:06 scribe: TK 15:09:11 scribeNick: taki 15:15:25 TOPIC: EXI for JSON 15:18:04 DP: Decimal support is marked as at risk. 15:18:18 DP: We will be able to remove it safely later. 15:18:33 DP: Appendix now talks about design decisions. 15:19:10 DP: I got comments from DB. I already implemented most of them. 15:19:12 http://services.w3.org/htmldiff?doc1=http%3A%2F%2Fwww.w3.org%2FXML%2FEXI%2Fdocs%2Fjson%2Fexi-for-json.html&doc2=http%3A%2F%2Fwww.peintner.org%2Ftmp%2Fexi-for-json.html 15:24:50 DP: JSON-LD supports certain keywords. It is an additional item we started to discuss at TPAC. 15:25:53 DP: It is also more general topic. 15:27:23 DP: Options we define in our documents. "strict" and "schemaId". 15:35:52 DP: I would stick with current schema ID. In the next version, we can add "-2" or something to indicate version. 15:37:45 DP: Steven Williams suggested us to use BSON as well. 15:38:33 DP: I am not BSON expert, but I know it is a binary format. 15:42:25 DP: "strict" is required because unknown elements are not convenient for EXI to JSON conversion. 15:44:02 DP: By requiring strict, implementation can be simpler. 15:45:25 JF: Appendix talks about implementation. 15:45:44 JF: Appendix has schema. 15:46:33 DP: Appendix B is schema. section 3 discuss conversion rules. 15:47:53 ... DP showing exificient implementation online... 15:48:30 JF: My first impression was this was about conversion. 15:51:47 TK: I think we can describe the reason why we require "strict" in design decision. 15:54:52 CB: We can publish as a Note, or can publish it saying it will be revised. 15:55:41 CB: Note in general means final. 15:56:54 CB: Drafts invite comments much more than Notes. 15:59:20 DP: Liam suggested we first publish draft or note. In the future, we can work on making it REC. 15:59:57 DP: Currently, we have schema in the document. I want to make the schema available separately. 16:00:20 CB: We can make a copy somewhere, that's ok. 16:03:06 CB: Schema doesn't have to be normative since it is for draft. 16:03:39 once published https://www.w3.org/TR/exi-for-json 16:03:50 DP: I want to have the document and schema consistent. 16:04:03 https://www.w3.org/TR/exi-for-json/schema-for-json.xsd 16:04:42 www.w3.org/2016/exi-for-json-schema.xsd 16:05:58 CB: We need to describe in the draft that we have another place that manages latest schema. 16:07:28 CB: The schema and document need to be modified at the same time. 16:09:28 DP: Can Carine check and modify SOTD? 16:09:37 CB: Yes, I will do that. 16:18:59 TOPIC: Canonical EXI 16:19:30 TOPIC: Call for opinions on how to represent empty elements in Canonical EXI 16:21:13 DP: Latest draft mentions both approaches. 16:22:59 DP: I am fine with going ahead with approach B. 16:23:42 TK: The group decided to choose approach B for how to represent empty elements. 16:25:02 DP: I will update the document accordingly. 16:25:39 TOPIC: Whitespace preservation mode 16:26:38 DP: Section 4.2.5 describes whitespace handling rules. 16:28:09 TK: I will review that section. 16:34:38 rrsagent, create minutes 16:34:38 I have made the request to generate http://www.w3.org/2016/01/12-exi-minutes.html taki 17:18:45 Zakim has left #exi