Efficient XML Interchange Working Group Teleconference

15 Nov 2016

See also: IRC log




EXI Renaming

<brutzman> TK confirmed that time, IRC, telcon and Webex information on group page are correct

DP: I remember Liam volunteered to update public EXI page.

TK: I will ping Liam about that.

Canonical EXI

<brutzman> https://lists.w3.org/Archives/Public/public-exi/2016Oct/0004.html said The plan is that the acronym "EXI" will stand for "Efficient Extensible Interchange"

TK: We successfully published Candidate Recommendation of Canonical EXI.

DP: Exificient is not complete in terms of Canonical EXI implementations yet.

DB: At some point, we will need Canonical EXI validation.

DP: Once OpenEXI and Exificient produce same stream, we can compare the stream and other implementations will produce.

DB: Content producer's perspective, they want to make sure it is correct.
... Correctness is security consideration. Validation is important for W3C validator.

DP: Canonical XML does not provide validator.
... Once we are settled and stable, I can provide GUI to check if it is canonical or not.
... We can prove the stream we produce is valid EXI.
... That should be sufficient, right?
... You can create EXI content that receiver will fail to decode.
... Once we implement new flags, we may want to run existing test cases first.
... Then we need to determine what do we need to create to test further.


TK: Daniel provided first blog post draft.

DP: I failed to add an item there.
... I am working with Carine to fix this issue.
... After that, we can add a blog post.
... Native implementation is event-based. I will need to take a look at Webkit implementation to know how to integrate.


TK: I would like to propose a change by pulling the paragraph that starts with "EXI is a format that sends an efficient stream of events..." up front.

DB: Should we say more about WG renaming?
... Also, we can mention XML security.
... Round-trip correctness?

DP: Some use cases do not need round-trip. RGB all number maps to integer.

<brutzman> Example of encoding CSS colors as enumeration values in Java: http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/java/fields/SFColorObject.html

<brutzman> here comes draft to you both...

<brutzman> Will post revised blog draft shortly.

<brutzman> Thanks for another great meeting! 8)

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/15 20:04:25 $

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/test//
No ScribeNick specified.  Guessing ScribeNick: taki
Inferring Scribes: taki

WARNING: No "Present: ... " found!
Possibly Present: DB DP TK brutzman exi https joined 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: 15 Nov 2016
Guessing minutes URL: http://www.w3.org/2016/11/15-exi-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]