See also: IRC log
https://en.wikipedia.org/wiki/25_de_Abril_Bridge
We discussed TPAC topics
We discussed EXI renaming, Taki's point to avoid confusion is well taken
Carine's suggested name of EXI = Efficient eXtensible Interchange = Efficient Extensible Interchange sounds good to attendees
<taki> DB: We should ask the public what they think about WG name change idea.
(discussion) can/should we change? we could pose this to exi-member or exi-public list for possible comment
of related interest: here is our wikipedia page https://en.wikipedia.org/wiki/Efficient_XML_Interchange
likely we should ask Liam (it was his idea) and perhaps other W3C leadership
scribe: since we all want the rationale and messaging about a possible renaming to make sense
<taki> ACTION: CB to check whether it is feasible to change the WG name [recorded in http://www.w3.org/2016/10/04-exi-minutes.html#action01]
<trackbot> Created ACTION-742 - Check whether it is feasible to change the wg name [on Carine Bournez - due 2016-10-11].
<taki> DB: We may need to improve wikipedia page about EXI
<taki> DP: We can put a note there as well, and they will catch up.
<taki> ACTION: DB to improve Wikipedia description about EXI [recorded in http://www.w3.org/2016/10/04-exi-minutes.html#action02]
<trackbot> Created ACTION-743 - Improve wikipedia description about exi [on Don Brutzman - due 2016-10-11].
<taki> DP: I can prepare what we should present to CSS WG for what we did so far.
<taki> DP: I talked to one person who was leading security activity. We should keep talking to them. I could not join their meetings.
<taki> DP: We discussed in TPAC that if we provide support for CSS, JavaScript targeting browsers, it will make it easier to support other things such as HTML5.
(that is an interval)
i just belatedly posted some simple editorial comments about Canonical EXI and EXI4JSON https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0005.html
RESOLUTION: From next week 10/11, telecon starts at 7:30pm (Europe), 10:30am (US Pacific).
these are simple and do not need to delay any decision regarding publication - editor's choice
<taki> TK: Does everybody agree to ask to publish Canonical EXI as Canididate Recommendation?
<taki> DP: I do.
<taki> TK: I do, too.
<caribou> +1
+1
RESOLUTION: The group decided to ask W3C to promote Canonical EXI as Candidate Recommendation, after incorporating several editorial stuff discussed today.
looking ahead: Taki, I plan to be in your neighborhood 19-20 OCT at Samsung for the W3C Workshop on Web & Virtual Reality
https://www.w3.org/2016/06/vr-workshop/
Participant position statements are available at https://www.w3.org/2002/09/wbs/1/vr-workshop/results
Web3D Consortium is adding EXI plus geometric compression as an efficient binary encoding for X3D, Extensible 3D Graphics international standard.
The combination of EXI compactness/performance along with potential for XML Security compatibility will be important in this domain.
it may be that everyone is so "headset happy" that they don't care about performance or privacy, we shall see! 8)
list of expected participants https://www.w3.org/2016/06/vr-workshop/participants.html
TK: we will meet at the later time next week.
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Carinne/Carine/ Succeeded: s/or related/of related/ Succeeded: s/combinataion/combination/ No ScribeNick specified. Guessing ScribeNick: brutzman Inferring Scribes: brutzman WARNING: No "Present: ... " found! Possibly Present: DB DP TK caribou dape exi https joined taki trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 04 Oct 2016 Guessing minutes URL: http://www.w3.org/2016/10/04-exi-minutes.html People with action items: cb db[End of scribe.perl diagnostic output]