DB: Functionality of EXI support in W3D is done.
... Two W3D applications supporting EXI is underway.
... First implementation testing seems to be working.
... Hoping to verify by round-tripping.
... It leads to interesting questions.
... Do we have EXI validation?

DP: Is it meant for EXI in general? or JSON only?

DB: In general. How can we know it is a valid EXI file?
... By round-tripping?

DP: If you provide a wrong EXI file, for example, EXIficient will fail.

DB: John Schneider also mentioned Canonical EXI needs tests.

DP: A tool to validate EXI...
... Interoperability framework may be able to do it.
... If you do want XML-schema validation, there are various tools. But there are still corner cases.

DB: Corner cases are interesting. From RECOMMENDATION point of view.

DP: We encountered issues initally during interoperability tests.

Wikipedia

DP: I successfully reflect the changes to the page in German.
... I asked people to review it.
... It seems to be some people have previlege to approve the changes.

DB: Wikipedia page seems ok for now.
... Carine might want to do French version.

Canonical EXI

Canonical EXI Interoperability Test Framework?

DP: The desire he has is we publish it before Proposed Recommendation.
... We still do not have full set.
... Maybe we should implement datatype part, then publish?
... We can also set a deadline such as end of next week?

<caribou> either way could work

DP: Is it easy to move the repository in public space?

CB: We can use github.
... It depends on how many outside people will be contributing.
... If we really want to, we still can.

DB: Github seems to be better for larger groups.

CB: W3C already has a few hundred repositories.

DP: Are there any issues wrt licenses?

CB: We are making snapshots public, right?

DP: Both OpenEXI and EXIficient licenses are fine.
... Including them makes it easier for use.
... Github provides more functionalities.

DB: Agreed

DP: John can grab the latest framework that way.
... One option is making it public by moving it to github.
... Doesn't it make sense to put everything?
... TTFMS

<caribou> exi-testsuite

<caribou> https://github.com/w3c/exi-testsuite

<brutzman> my github account: https://github.com/brutzman

<brutzman> thanks for prior discussion... have posted to public-exi "suggestion: support EXI validation"

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)


WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: taki
Inferring Scribes: taki

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 02 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/02-exi-minutes.html
People with action items: