Efficient XML Interchange: Difference between revisions

Revision as of 07:54, 1 February 2023

Revision as of 07:54, 1 February 2023

Line 16:

| publisher= W3C |author= Robin Berjon and Jaakko Kangasharju editors

| date= 20 July 2006

| accessdate= 23 September 2016 }}</ref> The EXI format is derived from the AgileDelta Efficient XML format.<ref>{{cite web

| url=http://www.agiledelta.com/product_efx.html

| title=Lightning-Fast Delivery of XML to More Devices in More Locations

| publisher=AgileDelta

| date= 5 November 2015

| accessdate= 23 September 2016 }}</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>

Line 26 ⟶ 31:

| accessdate= 28 February 2017 }}</ref>

==AlternativesFeatures==

An advantage of EXI over Fast Infoset is that EXI (optionally) uses more constraints from the [[XML schema]]. This can make the EXI data more compact; for example, if the XML schema specifies that elements named 'bar' may only exist within elements named 'foo', EXI can assign a shorter token to the 'bar' element, knowing that it doesn't have to share the same token space as elements that occur elsewhere in the document. The main disadvantage to utilizing such "schema-informed" compression is that, not only does the document require a schema, but the decoder needs a copy of the same schema that the encoder used.

The EXI format is derived from the AgileDelta Efficient XML format.<ref>{{cite web

| url=http://www.agiledelta.com/product_efx.html

| title=Lightning-Fast Delivery of XML to More Devices in More Locations

| publisher=AgileDelta

| date= 5 November 2015

| accessdate= 23 September 2016 }}</ref>

An advantage of EXI over Fast Infoset is that EXI (optionally) uses more constraints from the [[XML schema]]. This can make the EXI data more compact; for example, if the XML schema specifies that elements named 'bar' may only exist within elements named 'foo', EXI can assign a shorter token to the 'bar' element, knowing that it doesn't have to share the same token space as elements that occur elsewhere in the document.

The main disadvantage to utilizing such "schema-informed" compression is that, not only does the document require a schema, but the decoder needs a copy of the same schema that the encoder used.

==Uses==