Efficient XML Interchange - Wikipedia

DP: I do not know who to ping with regards to German wikipedia page on EXI. I keep getting a weekly reminder.
... I cannot make it to the EXI telecon next week.

<brutzman> thanks for alert Taki, my calendar had said an hour from now.

<brutzman> having trouble connecting +1-617-324-0000,640116166#,#

<brutzman> just found the mail update... am trying

<brutzman> fwiw last weeks minutes include some "delete me" diagnostic output https://www.w3.org/2017/04/04-exi-minutes.html

Canonical EXI test cases README

DP: I looked into what Grishma and TK said.
... I found missing implentation.
... There are some strange warnings.
... That's OK. There is one issue wrt performance measurement. I do not know where it comes from.
... I thought we are using Japex. I am not sure how much we changed Japex.

<brutzman> https://japex.java.net/

<brutzman> looks like last update was 6 years ago, when Oracle acquired Sun

<brutzman> also at http://japex.sourceforge.net/

DP: We are still using Japex 1.0
... The sourceforge link is for something else.

I found this. https://github.com/ModelDriven/fUML-Reference-Implementation/issues/26

TK: This person was able to avoid the warnings by using newer version xerces.

<brutzman> be careful that everything is backed up (i.e. fully checked in) before upgrading japex, it looks like it has been neglected for a long time

DP: Unless we have real problems, we should be ok as it is for now.
... The 1.2 version structure looks a bit different.
... Changing to the latest version may not be straightforward, and can cause other problems.

TK: We do not have datatype test cases yet.

DP: How do we make sure implementations do what the specification says it needs to do?

TK: I think we can assume each implementation did its best to implement the specification.

Daniel takes Decimal, Float and RCS test case development. TK takes Unsigned Integer, String Table and Datetime.

Wikipedia

<brutzman> Wikipedia page https://en.wikipedia.org/wiki/Efficient_XML_Interchange

<brutzman> in History section: "In November 2016, the working group was renamed to "Efficient Extensible Interchange (EXI)" from "Efficient XML Interchange (EXI)" to reflect the broader scope of EXI applicability"

<brutzman> suggest appending "beyond XML to other data-description languages."

<brutzman> under Uses, might we mention work in progress regarding CSS and JavaScript as well

<brutzman> proposed: EXI4CSS is exploring how to map Cascading Style Sheets (CSS) to EXI.

<brutzman> proposed: EXI for JavaScript appears to be possible if using the initial structured parse tree for source code.

<brutzman> that's all i had for today, thanks for discussion/review and continuous improvement!

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)

Present: Taki Daniel Carine
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: 10 Apr 2017
Guessing minutes URL: http://www.w3.org/2017/04/10-exi-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.