14:02:35 RRSAgent has joined #exi 14:02:35 logging to http://www.w3.org/2016/05/10-exi-irc 14:02:37 RRSAgent, make logs public 14:02:37 Zakim has joined #exi 14:02:39 Zakim, this will be EXIWG 14:02:39 ok, trackbot 14:02:40 Meeting: Efficient XML Interchange Working Group Teleconference 14:02:40 Date: 10 May 2016 14:02:43 zakim, this is exi 14:02:43 got it, taki 14:09:33 Present: Taki, Daniel, Carine, Don 14:09:36 Chair: Taki 14:10:04 brutzman has joined #exi 14:10:34 scribe: TK 14:10:39 scribeNick: taki 14:10:45 dape_ has joined #exi 14:10:53 TOPIC: TPAC 2016 Registration Now Open 14:11:17 https://lists.w3.org/Archives/Member/chairs/2016AprJun/0033.html 14:20:53 CB: I will take care of WebEX change. 14:21:11 TK: Telecons will be on Thursday till June 16th 14:21:26 TOPIC: EXI4JSON 14:23:56 TK: I measured some numbers using one example JSON. 14:24:16 TK: The current form is 313 bytes and the new one suggested by Daniel is 332 bytes. 14:27:51 DP: Element Fragment Grammar contains the list of all element names. 14:29:25 TK: We may want to do it for EXI2. 14:29:56 DP: The proposal I made at that time was to use XSD anyType grammar. 14:31:46 https://www.w3.org/XML/EXI/wiki/EXI2#Fallback_grammar 14:31:55 DP: In EXI2 wish list, it already say we want easier mechanism to achieve a similar effect as EXI profile. 14:33:41 DP: EXI has version numbers. 14:34:08 https://www.w3.org/TR/exi/#version 14:34:16 1 0000 Preview version 1 14:34:22 0 0000 Final version 1 14:34:37 DP: Version can be a preview version. 14:34:51 1 0001 Preview version 2 14:36:13 DP: We can create a note by using preview version numbers. 14:38:01 DP: When implementation use the extension, you need to use the preview version. 14:40:42 DP: For shared-string work, we use DTRM to signal the change. 14:45:27 DP: I am interested in measuring how much effect the change would make by modifying EXIficient if I have time. 14:45:48 TK: I will also take a look at how it is easy to make the change in OpenEXI. 14:47:11 DP: Once we feel comfortable, we want to propose as a Note using preview number. 14:47:46 TOPIC: Canonical EXI 14:48:28 DP: We processed DB and TK comments. 14:49:31 DP: We need to settle schemaId. For UTC normalization, introducing a URL is an idea that we need to ask. 14:55:43 http://www.w3.org/2005/06/tracker/exi/issues/109 14:58:25 DP: Internally, we thought it would be sufficient. 15:05:07 DP: I can see some use cases that don't get much benefit from schemaId. 15:05:53 DP: DB and Youenn had strong opinion about requiring schemaId. 15:08:04 DP: The EXI spec itself was silent about schemaId. 15:08:27 DP: If we get to EXI2, we may need to rethink about this aspect. 15:08:59 DP: we may want to use hash of XML schema, as Daniel Vogelheim suggested. 15:09:33 DB: What if there was not a schema? 15:10:37 DB: We need to provide an explicit warning about schemaId's importance. 15:12:37 DP: I agree. EXI 1.0 spec provides only a help by providing schemaId. 15:13:14 DP: In the next EXI, we need to repair it. 15:13:48 DP: XMPP uses multiple schemas. They create a hash over schemas. Hash identifies the schema. 15:16:08 DP: We need to mention schemaId "should" be present in the spec, and propose it to the public. 15:16:31 DB: The consequence of not doing it may be the recipient may not be able to decode it. 15:16:55 DP: It is a problem common to schema-based formats. 15:19:22 TOPIC: canonicalization of url 15:20:24 https://lists.w3.org/Archives/Public/public-exi/2016May/0004.html 15:21:44 RFC 3986 is the latest IETF reference for URI/URL. It has an excellent section on normalization and comparison. 15:21:45 DP: It is desirable to have normalization for URIs. 15:22:18 DP: EXI implementations currently do not know when it encounter URIs. 15:22:45 There is a "stairstep" of increasingly strict checks that are possible. These are mostly application dependent. 15:23:11 DB: We can refer to the section. 15:23:24 So we might refer to this section, point out that C14N of uris should follow that guidance, and leave it up to the application. 15:23:30 DB: And suggest applications should follow that suggestion. 15:25:17 DP: We have one section about design decision. 15:25:33 DP: Is it sufficient that we describe it in there? 15:29:08 RFC 3896 only has a little about normalization https://tools.ietf.org/html/rfc3986#section-3.1 15:30:28 DP: If Don, you can propose a text for this, that would be great. 15:30:54 DB: Just a simple sentence, that would be fine. 15:33:08 Suggested sentence: "Normalization and comparison of url and uri values, if applied within a document, is best performed in accordance with [RFC 2896]." 15:34:15 s/2896/3986/ 15:36:02 If we could discuss on the mailing list how EXI supports the full range of float and double values supported by XML Schema, that would be great. Not sure I understand the draft prose, all help appreciated. 15:36:59 Seems like we are close... just need to finish checking the mail threads to ensure all points were addressed. Thanks for the steady great efforts! 15:37:35 rrsagent, create minutes 15:37:35 I have made the request to generate http://www.w3.org/2016/05/10-exi-minutes.html taki 15:55:32 taki has left #exi 16:29:55 Zakim has left #exi