RE: Efficient representation for Web formats

Hi Daniel,

In Java implementation, you use Nashorn to convert JavaScript into AST,
then convert AST into EXI.  (JStoEXI.java [1])

On the decoder side, you convert EXI into AST. (EXItoJSAST.java [2])

I am not sure if Nashorn is available for C language. What is the input
and output of the C language implementation?

[1] https://github.com/EXIficient/exificient-for-javascript/blob/master/src/main/java/com/siemens/ct/exi/javascript/JStoEXI.java
[2] https://github.com/EXIficient/exificient-for-javascript/blob/master/src/main/java/com/siemens/ct/exi/javascript/EXItoJSAST.java

Takuki Kamiya
Fujitsu Laboratories of America


From: Peintner, Daniel (ext) [mailto:daniel.peintner.ext@siemens.com]
Sent: Wednesday, November 02, 2016 2:17 AM
To: public-exi@w3.org
Subject: Efficient representation for Web formats


Hi,

As Taki recently discussed in [1] the focus of the EXI working group has changed a bit.

Besides the work on XML, the working group is also exploring the idea of applying EXI to other Web formats. The WG is making JSON exchange more efficient by applying EXI to JSON [2]. We are recently also exploring the idea of applying EXI to CSS [3] and JavaScript [4].

EXI is a general format that sends an efficient stream of events and can have noticeable, measurable savings in CPU, memory & bandwidth over formats such as minify and/or gzip that require the receiver to reconstitute the original JSON/CSS/JavaScript/... and parse it again.

We encourage you to take a look at our exploration of EXI for CSS [3] and EXI for JavaScript [4] and to provide feedback/comments.

Thank you,

Daniel (for the EXI WG)

[1] https://lists.w3.org/Archives/Public/public-exi/2016Oct/0004.html
[2] EXI for JSON, https://www.w3.org/TR/exi-for-json/
[3] EXI for CSS, https://github.com/EXIficient/exificient-for-css
[4] EXI for JavaScript, https://github.com/EXIficient/exificient-for-javascript/