17:34:19 <RRSAgent> RRSAgent has joined #exi
17:34:19 <RRSAgent> logging to http://www.w3.org/2017/05/02-exi-irc
17:34:21 <trackbot> RRSAgent, make logs public
17:34:21 <Zakim> Zakim has joined #exi
17:34:23 <trackbot> Zakim, this will be EXIWG
17:34:23 <Zakim> ok, trackbot
17:34:24 <trackbot> Meeting: Efficient Extensible Interchange Working Group Teleconference
17:34:24 <trackbot> Date: 02 May 2017
17:42:40 <taki> DB: Functionality of EXI support in W3D is done.
17:43:24 <taki> DB: Two W3D applications supporting EXI is underway.
17:44:06 <taki> DB: First implementation testing seems to be working.
17:44:31 <taki> DB: Hoping to verify by round-tripping.
17:44:52 <taki> DB: It leads to interesting questions.
17:45:15 <taki> DB: Do we have EXI validation?
17:45:59 <taki> DP: Is it meant for EXI in general? or JSON only?
17:46:22 <taki> DB: In general. How can we know it is a valid EXI file?
17:46:35 <taki> DB: By round-tripping?
17:47:07 <taki> DP: If you provide a wrong EXI file, for example, EXIficient will fail.
17:48:28 <taki> DB: John Schneider also mentioned Canonical EXI needs tests.
17:50:34 <taki> DP: A tool to validate EXI...
17:51:54 <taki> DP: Interoperability framework may be able to do it.
17:56:02 <taki> DP: If you do want XML-schema validation, there are various tools. But there are still corner cases.
17:57:06 <taki> DB: Corner cases are interesting. From RECOMMENDATION point of view.
17:58:34 <taki> DP: We encountered issues initally during interoperability tests.
18:03:00 <taki> TOPIC: Wikipedia
18:03:47 <taki> DP: I successfully reflect the changes to the page in German.
18:04:11 <brutzman> brutzman has joined #exi
18:04:17 <taki> DP: I asked people to review it.
18:04:40 <taki> DP: It seems to be some people have previlege to approve the changes.
18:06:07 <taki> DB: Wikipedia page seems ok for now.
18:06:40 <taki> DB: Carine might want to do French version.
18:08:05 <taki> TOPIC: Canonical EXI
18:08:33 <taki> TOPIC: Canonical EXI Interoperability Test Framework?
18:09:30 <taki> DP: The desire he has is we publish it before Proposed Recommendation.
18:09:56 <taki> DP: We still do not have full set.
18:12:06 <taki> DP: Maybe we should implement datatype part, then publish?
18:17:09 <taki> DP: We can also set a deadline such as end of next week?
18:17:56 <caribou> either way could work
18:18:56 <taki> DP: Is it easy to move the repository in public space?
18:19:04 <taki> CB: We can use github.
18:20:44 <taki> CB: It depends on how many outside people will be contributing.
18:21:32 <taki> CB: If we really want to, we still can.
18:22:59 <taki> DB: Github seems to be better for larger groups.
18:24:28 <taki> CB: W3C already has a few hundred repositories.
18:24:56 <taki> DP: Are there any issues wrt licenses?
18:25:23 <taki> CB: We are making snapshots public, right?
18:27:15 <taki> DP: Both OpenEXI and EXIficient licenses are fine.
18:27:41 <taki> DP: Including them makes it easier for use.
18:28:21 <taki> DP: Github provides more functionalities.
18:28:27 <taki> DB: Agreed
18:29:03 <taki> DP: John can grab the latest framework that way.
18:30:05 <taki> DP: One option is making it public by moving it to github.
18:33:58 <taki> DP: Doesn't it make sense to put everything?
18:35:07 <taki> DP: TTFMS
18:35:28 <caribou> exi-testsuite
18:36:55 <caribou> https://github.com/w3c/exi-testsuite
18:38:42 <brutzman> my github account:   https://github.com/brutzman
18:46:03 <brutzman> thanks for prior discussion... have posted to public-exi "suggestion: support EXI validation"
19:43:31 <taki> taki has joined #exi
19:43:40 <taki> rrsagent, create minutes
19:43:40 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/02-exi-minutes.html taki
19:47:21 <taki> taki has left #exi
20:13:40 <Zakim> Zakim has left #exi