14:01:30 RRSAgent has joined #exi 14:01:30 logging to http://www.w3.org/2015/10/06-exi-irc 14:01:32 RRSAgent, make logs public 14:01:32 Zakim has joined #exi 14:01:34 Zakim, this will be EXIWG 14:01:34 I do not see a conference matching that name scheduled within the next hour, trackbot 14:01:35 Meeting: Efficient XML Interchange Working Group Teleconference 14:01:35 Date: 06 October 2015 14:03:43 dape has joined #exi 14:13:46 scribe: TK 14:13:52 scribeNick: taki 14:14:05 TOPIC: JSON support 14:14:41 DP: I sent the summary to XSLT group, Michael Kay forwarded to XQuery group. 14:15:12 DP: I am not sure how they handle it, whether it is in their telecon or email discussions. We will need to wait for their response. 14:16:06 CB: XQuery/XSLT, there is a weekly telecon. They have it on their agenda this week. 14:17:16 CB: XPath 3.1 is not yet a REC. 14:18:14 DP: With regards to schema, we can still decode the stream whether we use the original schema or our extended schema. 14:18:20 DP: I think. 14:21:44 TOPIC: Comments: Canonical EXI -- Last Call Working Draft 14:24:52 DP: Large integer issue, JS can live with it. 14:25:23 DP: As for datetime, both arguments are valid. JS recommends to use a switch. 14:25:39 DP: "preserveTimezone" 14:25:59 DP: similar to canonical XML's preserve comments, PIs 14:26:26 TK: How do we exchange those options? 14:27:26 DP: Fragment identifier. Similar to how Canonical XML does for comments. 14:32:13 DP: If it is the only option we would need to introduce, then I prefer not to have it. 14:32:46 DP: EXI options and schemaId in the header. 14:34:03 DP: I think YF described it well. 14:36:01 DP: I fear if we introduce many ways to do canonicalization, you need to exchange those options for canonicalization. 14:36:49 CB: In some applications, it can be exchanged static manner. 14:43:14 CB: JS is arguing to have flexibility to have or not have options. 14:44:05 CB: In his use case, applications know the settings in advance. 14:44:37 DP: It becomes less secure, I fear. 14:45:48 DP: We would need switches here again, right? 14:46:05 CB: In JS's use case, it may be hardcoded in application. 14:47:48 DP: His argument about stream bigger was not an issue. Additional code to handle was an issue for him. 14:48:55 DP: One goal I think is to eliminate the flexibility. We require sorting, for example. 14:50:12 CB: Canonical form is more constraint. 14:50:48 CB: It doesn't constrain the way we exchange options. 14:51:44 TK: Why didn't we converge on bitpacked? 14:53:05 DP: Changing coding mode requires a lot of more code. 14:56:40 DP: We require applications to exchange schemaId beforehand. 14:58:20 DP: We discussed, and decided it was safer to have schemaId. 15:10:01 TK: I think "preserveTimezone" is the real issue. This "options" issue is more design issue. 15:18:50 DP: For dateTime, at least we need to specify fractionalsec being zero is the same as no fractional seconds. 15:20:16 TOPIC: Support for Canonical EXI interoperability test in TTFMS 15:21:13 DP: I guess header options presence makes most of the differences. 15:21:59 DP: whitespace facet handling may be another issue causing some of the differences. 15:23:27 DP: schemaId is the location of the schema. 15:24:36 TOPIC: ACTION-725: Check whether we need to mention anything about which type to cast to in the case of profile stream 15:25:06 TK: I think it was a good catch. 15:32:35 rrsagent, create minutes 15:32:35 I have made the request to generate http://www.w3.org/2015/10/06-exi-minutes.html taki 15:54:19 taki has left #exi 16:26:26 Zakim has left #exi