15:11:58 RRSAgent has joined #exi 15:11:58 logging to http://www.w3.org/2017/07/31-exi-irc 15:12:00 RRSAgent, make logs public 15:12:00 Zakim has joined #exi 15:12:02 Zakim, this will be EXIWG 15:12:02 ok, trackbot 15:12:03 Meeting: Efficient Extensible Interchange Working Group Teleconference 15:12:03 Date: 31 July 2017 15:15:34 TOPIC: TPAC2017 for EXI? 15:16:06 DP: We can still use some other space even if we could not use ad-hoc meeting space. 15:16:17 TOPIC: Canonical EXI 15:17:08 TK: Thank you Daniel for the interoperability test results. 15:17:29 TK: It looks all problems are on OpenEXI side. 15:19:46 DP: If you observation is different, please let me know. 15:21:04 TK: I will give an update next week. 15:26:24 https://www.w3.org/wiki/TPAC/2017/ad-hoc-meetings 15:29:34 brutzman has joined #exi 15:29:46 TPAC 2017 agenda http://www.w3.org/2017/11/TPAC/Overview.html 15:30:14 TOPIC: TPAC2017 for EXI 15:30:40 DB: Thursday afternoon, there is AC meeting. 15:31:00 DP: Alternative is, to have ad-hoc meeting on Friday. 15:31:45 DP: I am not sure if I can join TPAC at this point, but if I can go, I will try to stay one day longer. 15:34:19 W3C Publishing Summit https://www.w3.org/publishing/events/summit2017.html 15:40:24 here is another area of work that might benefit from EXI: https://www.w3.org/blog/2016/10/w3c-and-big-data 15:41:29 am simply thinking that we might conceptualize a broader strategy for EXI, how does it help other areas of W3C work and the Open Web Platform. 15:42:23 ... then we might use TPAC week as a goal for upcoming communications, and an opportunity to interact with other groups and consider joint endeavors. 15:45:48 TOPIC: EXI4JSON 15:45:58 TK: moved EXI Ad Hoc meeting to Friday 10 NOV 1500-1800. https://www.w3.org/wiki/TPAC/2017/ad-hoc-meetings#EXI_ad-hoc_meeting 15:46:57 DP: I tried to share feedback from my experiences with WoT. 15:47:13 DP: Thing Description is written in JSON. 15:47:29 DP: We are looking at EXI4JSON, CBOR, etc. 15:47:35 DP: I noticed several things. 15:47:44 DP: I categorized into three. 15:48:01 DP: General EXI4JSON issue. 15:48:41 DP: For small documents, character escaping makes names with "@" sign bigger. 15:49:15 DP: One character becomes 4 characters for those for the first occurrence. 15:49:33 DP: Second category is EXI4JSON with dedicated schema. 15:49:46 DP: UPA issue. 15:50:10 DP: Valid in XSD 1.1, but not in XSD 1.0. 15:50:45 DP: Media-types. We want to use enumerated values. 15:50:58 DP: With strict mode, we cannot deviate. 15:51:26 DP: URI strings are very similar, with only the last part of strings are different. 15:52:07 DP: I am not sure if we need to stick with "strict" mode. 15:52:35 DP: Last category is how to standardize EXI4JSON. 15:52:49 DP: People were against using non-standard specification. 15:53:17 DP: EXI is a standard. How can we make EXI4JSON a standard? 15:55:26 question: A1. keyname escaping, is the basic issue that @ symbol is not allowed as a key? 15:55:56 Don you are right @ is not a valid character in XML... and since we wanted to keep compatibility with XML we decided to escape @ and similar characters 15:56:28 thanks, next question 15:57:07 # B Issues with dedicated schemas in EXI4JSON: it would seem we most want compatibility with XSD 1.1 version... 15:58:09 ... alternatives might be to either only support 1.1, or else list deviations such as this that might be known limitations of some sort. 15:59:37 B2. Pre-populated strings based on enumerated values: it is also possible to define enumeration values and use them as attribute values, even if they are optional/extendible (meaning not strict but allowed)... 16:00:18 no mentioning of 1.1 is made 16:00:31 ... wondering if we can handle this case. (in X3D schema we have been informally documenting such relationships as appinfo) 16:00:58 B2. Pre-populated strings based on enumerated values: seems very valuable, hope we can do it. 16:01:18 EXI refers to xml schema 1.0 in the spec 16:03:54 TK: I suggest to continue discussion on EXI4JSON next week. 16:05:15 Daniel maybe next time we could talk about JSON schema efforts, looks like you posted over on that list. 16:06:03 rrsagent, create minutes 16:06:03 I have made the request to generate http://www.w3.org/2017/07/31-exi-minutes.html taki 16:08:17 dape_ has joined #exi 17:42:06 Zakim has left #exi