DP: Two topics.
... Vacation plan. I won't be available second part of June. June 19 till the end of June.

TK: I plan to take a couple of days in August.

DB: I will be in Australia. After that, I plan to take some, but will likely be able to dial-in.

DP: What's geek week, Carine?

CB: There will be limited availability, since team contacts will be working on internal geek projects.
... Maybe it will not overlap with EXI telecon.

DB: TPAC will be in November this year.

<caribou> https://lists.w3.org/Archives/Member/chairs/2017AprJun/0084.html

DP: I will try to be there.

CB: We might be able to work on community group.
... But not sure if we can use rooms at TPAC.
... Community group needs five supporters.
... By individuals.
... I am not sure if we can use member-only list, repositories, so on.
... Github, yes.
... The charter goes till end of August. We can extend it to finish canonical EXI.
... I am not sure if we can re-charter as a WG.
... Canonical EXI is the only thing that we have as REC track item.

DB: We still have EXI2, interoperability with XML security, EXI4JSON, etc.
... We need to describe how we can proceed.

CB: XML security side, there is no longer a WG for that by now.
... WoT people are good candidates to interact with.

DP: There is some interest in EXI4JSON. We need to stabilize it as soon as possible.
... I am not sure it is ok to keep working on it in community group.
... JSON-LD is now community group, and is publishing a document for version 1.1.

CB: Trying to move into WoT is another idea eventually.
... Community groups can stay small. I don't think it harms discussion. Only drawback is that we cannot work on Recommendation Track.

DB: We need to think about our goals first.

CB: We might find other ideas in the meantime while we work on Canonical EXI.

<brutzman> Many goals might well be suitable for Recommendation track. Additionally we do need more people to execute effectively. So thinking it through will be good.

DP: We need to sketch different possibilities among options.
... WoT people are interested in us, but the impression is they are not eager to work on new stuff on this.
... How can a community group publish JSON-LD 1.1?

<dape> https://json-ld.org/spec/latest/json-ld/

CB: It is not yet published as W3C.

DP: WoT WG requires specifications to be RECOMMENDATION to make normative references.
... It is also relevant to our specs when WoT makes references to us.
... In the case of Canonical EXI, we were already references by vehicle industry people (ISO specs).

Canonical EXI

TK: DP accounced the availability of TTFMS on Github.
... I checked out Github repository. I plan to make sure if it runs ok or not.
... I will work on test cases after that.

DP: We need to show interoperability before PR?

CB: Yes. Before the end of August, so that we can get extension.

DP: It should be do-able.
... If found necessary, we can still add some missing test cases.
... We also need to resolve those test cases where we found differences between implementations already.
... I will wait for some weeks. I will try to ping people then.

DB: It may also be good to ask people which mode the group should be work in.
... We can also reach out our old alumni as well.
... We may get support from there.

DP: Our former member (David Lee) is on the Balisage page.

DB: How we can tell our story to external group, such as HTML, IoT, etc?

DP: We created a blog page a couple of months ago.

EXI4JSON

DP: We found that it would be good to priotize integer representation and make it parallel to "number".
... It is also the case that for some people it may be a trouble.
... When people use json-ld, there will be no difference since they can define their own schema.

TK: So today people seem to prefer to stay with the current structure.

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)

Succeeded: s/work on/work in/

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: 30 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/30-exi-minutes.html
People with action items: