Efficient XML Interchange: Difference between revisions

Revision as of 23:57, 3 November 2024

Revision as of 21:49, 11 December 2024

Line 21:

| date= 5 November 2015

| accessdate= 23 September 2016 }}</ref><ref>{{cite book|first1=Manvi|last1=Mishra|first2=Prabhakar|last2=Gupta|first3=SS|last3=Bedi|first4=Sudheer Kumar|last4=Singh|first5=Ankur|last5=Kumar|display-authors=2|year=2024|chapter=Rapid and Close-Packed Xml Solution with Efficient Extensible Interchange (EXI)|doi=10.1201/9781003535423-74|editor-first1=Suman Lata|editor-last1=Tripathi|editor-first2=Devendra|editor-last2=Agarwal|editor-first3=Anita|editor-last3=Pal|editor-first4=Yusuf|editor-last4=Perwej|display-editors=1|title=Emerging Trends in IoT and Computing Technologies|isbn=9781003535423|publisher=CRC Press}}</ref>

EXI was adopted as a [[W3C recommendation]] by the W3C on 10 March 2011. A second edition was published in February 2014.<ref>{{Cite web |title= Efficient XML Interchange Working Group |work= Public web site |publisher= W3C |url= https://www.w3.org/XML/EXI/ |accessdate= 23 September 2016 }}}</ref>

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 beyond XML to other data-description languages. <ref name="PeintnerBlog">{{cite web

| url= https://www.w3.org/blog/2016/11/efficient-representation-for-web-formats

| title= Efficient representation for Web formats

Line 49:

Multiple experimental initiatives continue to be pursued by the EXI Working Group.

* EXI4CSS is exploring how to map Cascading Style Sheets (CSS) to EXI. <ref name="PeintnerBlog"/>

* EXI for JavaScript appears to be possible if using the initial structured parse tree for source code. <ref name="PeintnerBlog"/>

* Considering potential composition of XML EXI with XML Encryption and XML Digital Signature.