- From: Takuki Kamiya <tkamiya@us.fujitsu.com>
- Date: Fri, 21 Oct 2016 16:54:37 -0700
- To: "public-exi@w3.org" <public-exi@w3.org>
Hi, Since the start of the working group, the focus of this WG has been on how to make XML interchange more efficient between applications. We will further continue this effort by making improvements to what we have achieved as EXI and its related specifications. As we informed the audience of this public mailing list in August (please see [1]), the WG is working on making JSON exchange more efficient by applying EXI to JSON. We are recently also exploring the idea of applying EXI to CSS and JavaScript. There are more ideas on the table to apply EXI to HTML5, MathML, etc. (see [2]) Reviewing how best position these ongoing work in relation to our current charter [3], we started to fiddle with the idea of reflecting the widening scope of our work to the working group name. The Working Group agreed that it should seek to change the name of the working group to better represent what we want to achieve while preserving the acronym "EXI". Changing the acronym would seem more difficult. Among the causes for the difficulty is that the WG page URL [4], for example, contains it. Therefore, we do not propose to change the acronym, and the WG will be still called as "EXI" WG. The plan is that the acronym "EXI" will stand for "Efficient Extensible Interchange" instead of "Efficient XML interchange." This change is to indicate EXI is not only for XML, all while causing no changes to the acronym. If you have any comments or questions, please let us know as soon as possible. Thank you, [1] https://lists.w3.org/Archives/Public/public-exi/2016Aug/0004.html [2] https://lists.w3.org/Archives/Public/public-exi/2016Sep/0001.html [3] http://www.w3.org/XML/2015/05/exi-charter.html [4] http://www.w3.org/XML/EXI/
Received on Friday, 21 October 2016 23:55:19 UTC