00:08:00 RRSAgent has joined #exi 00:08:00 logging to http://www.w3.org/2015/10/26-exi-irc 00:08:02 RRSAgent, make logs public 00:08:02 Zakim has joined #exi 00:08:04 Zakim, this will be EXIWG 00:08:04 I do not see a conference matching that name scheduled within the next hour, trackbot 00:08:05 Meeting: Efficient XML Interchange Working Group Teleconference 00:08:05 Date: 26 October 2015 00:08:07 scribe: TK 00:08:12 scribeNick: taki 00:08:27 DP: Value string handling. 00:08:57 DP: strings are well-known. Many of them in WoT, for example. 00:09:36 DP: For small documents, it is a problem. 00:10:01 DP: We do not know whether and when EXI 2 happens. 00:10:13 DP: We could do it now without a lot of effort. 00:10:55 DP: I would tell them to create enumeration of string values in schema. 00:11:17 DP: e.g. enumeration of "Audi", "Golf", "BMW" 00:12:01 DP: The drawback is that you have to modify the schema. 00:12:22 DP: Extending a schema is much better than modifying it. 00:13:04 DP: EXI bases on schema-knowledge only. We should keep it. More dependency is not good. 00:14:57 DP: We could define a document that defines shared string values. 00:15:17 DP: How the string table gets created. 00:15:49 DP: Define a new EXI datatype. (exi:sharedStringValues) 00:16:32 DP: Use DTR to map string to sharedStringValues 00:19:24 DP: WoT uses JSON-LD 00:20:03 DP: There is an issue. Lots of pre-known vocabulary. 00:21:01 DP: JSON-LD 1464 bytes, CBOR 807, JSON EXI 523, EXI with shared string values 283 bytes 00:25:09 YF: If you define enumerations with lots of values, they get populated. I wonder whether it is good idea to put all enumerations in schema into table. 00:26:30 YF: Maybe we should have had it in EXI 1.0 00:32:06 YF: Can we have shared values in the header? 00:37:24 YF: sharedStringValues element can have value? 00:54:14 DP: Those from schema and those from header should be handled separately. 00:56:52 liam has joined #exi 00:58:36 YF: In schema-informed, we have DTR. 00:59:32 YF: In schema-less, we don't have sharedStringValues. 01:05:08 DP: schema-less support will be in EXI2. 01:13:13 TK: Will we have a REC for this? 01:13:20 DP: No. Just a NOTE. 01:16:50 YF: We can leave open how schema-less case is supported. 02:09:42 DP: We should check with Carine if we can produce a Note for this. 02:10:30 YF: We should check whether there is no negative impact. 02:16:41 DP: Are there any schema constructs other than enumeration? 02:21:14 s/extendim/extending 02:27:59 DP: I am going to add better "union" support to EXI2 02:37:20 YF: If we can have a way to always fallback to string, that would be better. 02:37:32 Zakim has left #exi 02:37:49 zakim, this is exi 02:44:26 /invite rrsagent 02:44:30 /invite zakim 02:47:17 TK: Do we have resolution to start working on Shared String Working Note? 02:47:32 DP: Let's check with CB about procedure. 02:49:54 DP: Do we have a template for Note? 02:51:47 Zakim has joined #exi 02:53:33 ACTION: DP to convert Shared Strings idea slides into document format. 02:53:34 Created ACTION-728 - Convert shared strings idea slides into document format. [on Daniel Peintner - due 2015-11-02]. 03:14:40 DP: JAXP may have an issue with union. 03:14:53 s/JAXP/JAXB 03:25:03 DP: JAXB uses java string for union typed data. 03:25:45 DP: We can still plugin EXI via SAX events. JAXB has special treatment for FastInfoset. 03:28:25 TOPIC: Open Source 03:28:48 DP: EXIficient will be changed to MIT-license based in a few weeks. 03:31:29 DP: I use JSON-based EXI grammar for YF's JS implementation. 03:37:48 DP demoing XML/EXI processing in browser based on Javasceipt-based EXIficient. 03:39:18 DP: I re-wrote EXIficient in JavaScript. 03:41:18 YF: You can use JS minifier. 03:43:18 DP demoing JSON/EXI processing in browser. 03:45:41 YF: SharedString implemented in JS as well? 03:45:57 DP: Currently implemented in neither JS or Java. 03:51:34 YF: Do you produce text while decoding? 03:51:49 DP: I use SAX-like events, and give to handler. 03:53:40 YF: I am interested about the speed. Compared with JSON parser. 03:54:52 YF: You need to prepare your code for making optimization possible. 03:59:34 DP: We plan to publish on the mailing list. 04:48:02 liam has joined #exi 05:04:43 readinf the sharedStringValue idea, it looks much like using a schema but not an XML schema 05:04:56 s/readinf/reading 05:06:08 it could a WG Note for additional schemas support 05:07:05 it might be interesting to have something on REC track, though, at least for interop purposes 05:10:37 Zakim has left #exi 05:27:30 [ https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview.html#json-to-xml-mapping ] 05:31:06 TOPIC: JSON schema 05:35:36 DP: I noticed some differences between latest and the one we use. 05:36:40 Sebastian_Kaebisch has joined #exi 05:37:26 present+ Sebastian_Kaebisch 05:39:44 DP: The latest one has anyAttributes all over the place. 05:39:53 LQ: It increases entropy. 05:40:05 DP: Yes, but it does not affect much. 05:41:54 LQ: The more people use the same schema, it is better. 05:42:52 DP: We have not gotten any response so far for the request we have made. 05:47:00 Johannes: Can you define extended schema yourself? 05:50:21 LQ: We can send it in to the public list. 05:50:51 [ public-xsl-query ] 05:57:28 Sebastian: There may be an issue in distinguishing float from double. 06:09:53 LQ: We will know in a few weeks whether the request will be met or not because the spec is supposed to become CR soon. 06:13:49 DP: We could use type cast, but the issue was type cast is costly. 06:17:07 I'm logging. Sorry, nothing found for 'where are we' 06:17:32 rrsagent, make logs public 06:17:51 jhund has joined #exi 06:18:06 RRSAgent, draft minutes 06:18:06 I have made the request to generate http://www.w3.org/2015/10/26-exi-minutes.html jhund 06:18:18 dape has joined #exi 06:18:35 RRSAgent, make logs public 06:18:38 RRSAgent, draft minutes 06:18:38 I have made the request to generate http://www.w3.org/2015/10/26-exi-minutes.html jhund 06:27:30 LQ: Regarding the difference between REC and Note, one thing important is patent. 06:28:55 DP: Shared String extention will be just a few pages short document. Starting as a Note should be appropriate. 06:31:53 ACTION: TK to ask Liam to write a blog article about JSON support when the work is done. 06:31:53 Created ACTION-729 - Ask liam to write a blog article about json support when the work is done. [on Takuki Kamiya - due 2015-11-02]. 06:32:15 Sebastian: It is a bit confusing to name EXI as "xml"-based when it is about to support JSON. 06:40:05 LQ: CSS support. If EXI can be used for multiple formats, it makes EXI more useful. 06:40:41 DP: In WoT, the motivation is for code footprint. 06:41:17 LQ: How much it would help in browser, I don't know. 06:41:20 CSS payload is not as high as payload for a data format, though 06:43:09 LQ: I made it optional whether JSON support should be REC or not. 07:08:24 liam has joined #exi 07:41:06 jhund has joined #exi 07:45:14 yes, WD then Note 07:45:30 WD would mention that it's not on REC Track 08:06:48 it's fine to specify options per test case, as long as we cover all possible set of options 08:58:41 Tomorrow, we plan to have lunch 12:00-1:00. 08:59:46 Thank you Carine. 09:12:04 taki has left #exi 10:00:45 liam has joined #exi