W3C

- DRAFT -

Efficient XML Interchange Working Group Teleconference

22 Nov 2016

See also: IRC log

Attendees

Present
Regrets
Chair
SV_MEETING_CHAIR
Scribe
taki

Contents


<brutzman> am here, trying to connect

CB: Web Assembly is currently a community group.
... Currently, not a WG.

DP: They managed to get into many browsers.

CB: Not many JavaScript comminity are using it now

DP: 800 people are in the community group.
... Samsung has JavaScript engine that has very small footprint.
... It can be deployed to tiny devices.
... Ben Titzer from google presented Web Assembly in WoT call.

EXI Renaming

TK: Liam updated our public page.

DP: CB also made update.

CB: I also updated member-only page.

<caribou> https://www.w3.org/Member/Mail

CB: If you notice anywhere else that mentions old name, please let me know.

DP: We should announce that we change the name.

<brutzman> wondering if W3C Communications might get us some EXI shirts, or hats? Not too small please...

Canonical EXI

TK: I setup my eclipse environment. I will implement the parameters today.

DP: I plan to implement some missing features in EXIficient soon.

W3C Blog

DP: One comment was to move the link to EXI4CSS presentation up-front.
... Another was about "EXI to JSON" typo.

<caribou> https://www.w3.org/blog/?p=15827&shareadraft=baba15827_583495a2ddc34

<caribou> sentence about the name change should be updated

DB: Could we ask for a logo?

DP: We created a logo in WoT. We had a pushback.
... Therefore, I would say it is unlikely to happen.

<caribou> WoT is not yet a technology, EXI is a REC, we might get a different answer

<caribou> it's worth asking

DB: We should still be able to ask for one.

CB: I will ask. We have created for logo for HTML, CSS, etc. Also for some initiatives.
... I am going to ask.

DP: I will not wait for the logo before publishing the blog.

<brutzman> Link for implementaions: http://www.w3.org/XML/EXI/#implementations

<brutzman> change "We encourage you to take a look" to "We encourage everyone to take a look"

<brutzman> "Power-sensitive EXI efficiencies" sentence likely better as 4th bullet in preceding list

<brutzman> "Multiple implementations of EXI are available" (with url added) can then be lead sentence for last paragraph

<brutzman> perhaps add "Public" to "Participation and feedback are welcome!"

<brutzman> might help to add authors and date to cover slide for CSS-EXI http://www.w3.org/XML/EXI/outreach/2016/11/css.html#cover (as you wish)

<brutzman> perhaps "leave a comment in the blog" to "leave a comment here in the blog"

<brutzman> An early blog post by Cariine: "EXI Stance," 25 October 2007, https://www.w3.org/blog/2007/10/exi-stance

<brutzman> pretty cool that we achieved everything you said in that post!

<brutzman> Chris Lilley comment on that blog post: "Its just the tokeniser part that has to change, surely. The same tokens are being matched (elements, attributes, etc), the same DOM built. So instead of two parsers, its more like one parser with two possible input formats."

<brutzman> TK: "will eventually stand for" needs update... perhaps "now stands for"

<caribou> sure, go ahead

<brutzman> maybe "efficient stream of parse events" to "efficient data stream of parse events"

<brutzman> and then "and can have noticeable" to "that can have noticeable"

<brutzman> DP: 3 2 1 post!

<brutzman> https://www.w3.org/blog/2016/11/efficient-representation-for-web-formats/

<dape> https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html

<dape> https://lists.w3.org/Archives/Member/member-exi-wg/2016Oct/0035.html

Extended String

DP: I noticed that the issue of EXI is that between EXI and GZIP is not big. Newer compression scheme are emerging, too.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/11/22 19:58:31 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/!:/!"/
Succeeded: s/here in the blog/here in the blog"/
No ScribeNick specified.  Guessing ScribeNick: taki
Inferring Scribes: taki

WARNING: No "Present: ... " found!
Possibly Present: CB DB DP TK brutzman caribou dape exi https joined n8s trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

        <amy> Present+


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

Found Date: 22 Nov 2016
Guessing minutes URL: http://www.w3.org/2016/11/22-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]