18:36:19 <RRSAgent> RRSAgent has joined #exi
18:36:19 <RRSAgent> logging to http://www.w3.org/2017/03/07-exi-irc
18:36:21 <trackbot> RRSAgent, make logs public
18:36:21 <Zakim> Zakim has joined #exi
18:36:23 <trackbot> Zakim, this will be EXIWG
18:36:23 <Zakim> ok, trackbot
18:36:24 <trackbot> Meeting: Efficient Extensible Interchange Working Group Teleconference
18:36:24 <trackbot> Date: 07 March 2017
18:39:35 <taki> DP: I caught up with TK's email.
18:39:57 <taki> DP: Canonical EXI 4.3.1 and 4.3.2.
18:40:06 <taki> DP: I propose two sections together.
18:40:32 <taki> DP: I added an example.
18:40:35 <dape> dape has joined #exi
18:40:40 <dape> https://www.w3.org/XML/EXI/docs/canonical/canonical-exi.html#excludeExtraneousEvents
18:41:24 <taki> DP: The example is about simple type and strict is on.
18:43:14 <caribou> Present: DP, TK, CB, DB
18:49:04 <brutzman> brutzman has joined #exi
18:49:44 <taki> DP: I will update section 4.3.1 to make the second paragraph more generic.
18:50:40 <dape> Section, 4.2.2 issue: https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0003.html
18:51:32 <taki> DP: Section 4.2. I added a list of two steps.
18:51:33 <dape> Section, 4.2.2 issue: https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0002.html
18:53:45 <taki> DP: There are situations that Canonical EXI processor behaves differently from XML-schema validator.
19:00:37 <taki> DP: We might want to avoid using the term "canonical exi" processor.
19:10:33 <taki> TK: I suggest we use "should not", instead of "must not".
19:12:12 <taki> DP: schemaId issue.
19:12:18 <taki> https://lists.w3.org/Archives/Public/public-exi-comments/2017Mar/0000.html
19:13:02 <taki> DP: I used "MAY" because it is optional.
19:13:17 <taki> DP: JS is in favor of removing it.
19:14:22 <taki> DP: I think the warning in constraint item 4 in section is important.
19:16:00 <taki> DP: Do we want to remove item 4 constraint, and move the warning to after the constraints list?
19:28:32 <taki> TOPIC: integer in EXI4JSON
19:29:28 <taki> DP: We have various types.
19:31:27 <taki> DP: It may increase event code size.
19:32:13 <taki> DP: There are some other types in "otherType"/
19:32:33 <taki> s/\// /
19:34:25 <taki> DP: I also confirmed most JSON library differentiates floats from integers.
19:40:29 <taki> DP: I will check what would be the impact.
19:42:32 <taki> CB: A draft about "+exi" was re-submitted in IETF.
19:43:25 <taki> CB: In my opinion, they should work-around it because the situation is the same.
19:44:20 <taki> DP: One person pushed back.
19:44:35 <taki> s/DP/CB/
19:45:00 <taki> CB: Without knowing the schame, you cannot process the document.
19:45:27 <taki> CB: Some people started to use "+exi" already.
19:47:04 <taki> DP: My recollection is that seml walked away from EXI. I think they now use JSON.
19:47:38 <taki> DP: For senml, they did not allow "senml+exi".
19:48:15 <taki> CB: I think there is "senml-exi".
19:48:30 <taki> CB: I wonder who are using "+exi".
19:51:18 <taki> DB: In addition to XML, there are JSON, etc.
19:51:54 <taki> DB: EXI is somewhat special.
19:52:40 <taki> CB: With "+exi", you can use various schemas.
19:54:33 <taki> CB: I will keep watching.
19:55:51 <brutzman> thanks Carine for all of the information about media type efforts.
19:56:16 <brutzman> Not finding anything on our public or private working group pages regarding media type efforts.
19:58:18 <brutzman> EXI has many similarities to gzip in that there can be both application/gzip [RFC6713] https://tools.ietf.org/html/rfc6713 and http content encoding
19:59:21 <brutzman> EXI also has similarities to XML for media types, where it is possible to consider something+XML as well as something+exi encodings.
20:00:01 <brutzman> EXI is now going beyond the functionality of each with the emergence of extensible encodings for JSON, CSS, JavaScript etc.
20:00:25 <brutzman> So a comprehensive strategy will need to be pursued, this is very important.
20:00:56 <brutzman> The X3D media types will want to exercise each of these options.
20:03:17 <brutzman> we should likely expect additional future work to emerge as we achieve Canonical EXI and begin to align it with XML Encryption and XML Authentication.
20:04:14 <taki> rrsagent, create minutes
20:04:14 <RRSAgent> I have made the request to generate http://www.w3.org/2017/03/07-exi-minutes.html taki
21:01:32 <Zakim> Zakim has left #exi