EXI 27.4 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>Efficient XML Interchange Working Group Public Page</title>
  <link href="../Binary/binary.css" rel="stylesheet" type="text/css" />
  <style type="text/css">
     dt { font-style: italic; font-family:serif; }
  </style>
</head>

<body>

<div class="logos">
<a href="/"><img src="/Icons/WWW/w3c_home" alt="W3C" width="72" height="48"
border="0" /></a><a href="/Ubiweb/"><img src="/Icons/ubi212"
alt="Ubi Web Domain" width="212" height="49" border="0" /></a></div>

<div class="related">
Nearby: <a href="..">XML Activity</a> - <a
href="http://www.w3.org/XML/Binary">XML Binary Characterization work</a></div>

<div style="text-align:center">
<h1>Efficient XML Interchange Working Group</h1>

<h2>Public Page</h2>

<p><!--* toc *-->
<a href="#Publications">Publications</a> &bull;
<a href="#News">Status</a>&bull;
<a href="#Introduction">Background</a>&bull;
<a href="#Participation">Participation and Discussion</a>&bull;
<a href="#timeline">Timeline</a> &bull;
<a href="#implementations">Implementations</a>
</p>
</div>

<p>This is the public web page for the Efficient XML Interchange (<abbr
title="Efficient XML Interchange">EXI</abbr>) Working Group of the <a
href="http://www.w3.org">World Wide Web Consortium (W3C)</a>. The EXI group
is part of W3C's <a href="../">XML Activity</a>. Here we present literature
and data that may be of interest to the public. There is also a <a
href="../Group/EXI">private page</a> for members of the EXI group, for
internal information.</p>

<p class="summary">The objective of the Efficient XML Interchange Working
Group is to develop a specification for an encoding format that allows
efficient interchange of the XML Information Set, and to illustrate effective
processor implementations of that encoding. This work is based on the <a
href="http://www.w3.org/TR/xbc-characterization/#N107D4">conclusions</a> of the
<a href="http://www.w3.org/XML/Binary">XML Binary Characterization (XBC) Working Group</a>.
</p>

<p>The group's <a href="http://www.w3.org/XML/2010/10/exi-charter">charter</a>
covers the period February 2011 to 30 June 2012. <br/>
(Previous charters covered <a href="http://www.w3.org/XML/2009/02/exi-charter.html">January 2009 to January 2011</a> and <a href="http://www.w3.org/2005/09/exi-charter-final.html">December 2005 to December 2008</a>.)</p>

<h2><a name="Publications">Publications</a></h2>

<p>Selected publications in the order of most recent first:</p>
<ul>
  <li><strong>Efficient XML Interchange (EXI) Format 1.0, <a
    href="http://www.w3.org/TR/2011/REC-exi-20110310/">Recommendation</a>,
    10 March 2011. </strong> See the press release in
<a href="http://www.w3.org/2011/03/exi-pr.html.en">English</a>,
<a href="http://www.w3.org/2011/03/exi-pr.html.fr">French</a>,
<a href="http://www.w3c.de/Press/2011/exi-pr.de.html">German</a>,
<a href="http://www.w3c.es/Prensa/2011/nota110310_exi">Spanish</a> and
<a href="http://www.w3c.se/resources/office/press-releases/2011-03-10-exi.sv.xhtml">Swedish</a>.
There are <a href="http://www.w3.org/2011/03/exi-testimonials.html">Testimonials</a> that you can browse through to witness the moment.
</li>
  <li><strong>EXI Primer</strong>, <a
    href="http://www.w3.org/TR/2009/WD-exi-primer-20091208/">Second Public
    Working Draft</a>, 08 December 2009. </li>
  <li><strong>Efficient XML Interchange Evaluation</strong>, <a
    href="http://www.w3.org/TR/2009/WD-exi-evaluation-20090407/">Second Public
    Working Draft, 7 April 2009</a>.</li>
  <li><strong>EXI Impacts</strong>, <a
    href="http://www.w3.org/TR/2008/WD-exi-impacts-20080903">
    First Public Working Draft, 3 September 2008</a>.</li>
  <li><strong>EXI Best Practices </strong>, <a
    href="http://www.w3.org/TR/2007/WD-exi-best-practices-20071219">First
    Public Working Draft, 19 December 2007</a>.</li>
  <!-- li>Working Draft of the <a
    href="http://www.w3.org/TR/2007/WD-exi-measurements-20070725/">Efficient
    XML Interchange Measurements Note</a>, updated (25 July 2007)</li -->
  <li>The Working Draft of the <a
    href="http://www.w3.org/TR/2007/WD-exi-measurements-20070725/">Efficient
    XML Interchange Measurements Note</a>. This document describes
    measurements that had been made, by the Working Group, of the
    compactness and processing characteristics of various potential XML
    encoding formats (25 July 2007). The raw <a href="http://www.w3.org/XML/EXI/test-report.html">
    results</a> of candidates testing is available. The WG maintains a <a href="http://www.w3.org/XML/EXI/wiki/MeasurementsNoteErrata">wiki page</a> documenting inaccuracies that have been found with regards to the measurements note document.
</li>
  <li>Measurement Test Framework. See <a href="#TestingFramework">below</a> (18 May
    2007)</li>
 <li>Interoperability Test Framework. See <a href="#InteropTestingFramework">below</a> (1 March 2011)</li>

</ul>

<p>The <a href="http://www.w3.org/XML/2010/10/exi-charter">Charter</a>
of the Efficient XML Interchange Working Group defines the deliverables
expected of the group.</p>

<h2><a name="InteropTesting">Interoperability Testing</a></h2>

<p>As part of the W3C Process to reach the Proposed Recommendation status,
the Working Group has conducted interoperability tests during the Candidate
Recommendation phase. The Test Suite has been released publicly
(see <a href="#InteropTestingFramework">below</a>). The results of the
interoperability tests performed on 3 implementations are available in the <a
href="http://www.w3.org/XML/EXI/implementation-report/">implementation report</a>.</p>

<!--
<p>In order to promote interoperability between implementations and to
validate the clarity of the EXI specification, a number of <a
href="https://www.movesinstitute.org/exi">EXI encoded documents</a> have been
made available for example purposes. Those interested can compare their own
EXI encodings to these examples and discuss their questions/comments on the
<a href="mailto:public-exi@w3.org">public-exi@w3.org</a> (<a
href="http://lists.w3.org/Archives/Public/public-exi/">Archives</a>). The
U.S. Naval Postgraduate School generated the examples (on behalf of the Web3D
Consortium) using AgileDelta's implementation of the third draft of the EXI
format specification, but has not been tested by the EXI working group.
Although these examples are <b>not normative</b>, they should prove useful in
developing EXI implementations and in focusing discussion to improve the EXI
format specification.</p>-->

<h2><a name="News">Present Status</a></h2>

<p>(In reverse chronological order, as of March 2011).</p>

<p>In March 2011, "Efficient XML Interchange (EXI) Format 1.0" specification became a <a href="http://www.w3.org/TR/2011/REC-exi-20110310/">Recommendation</a>.
</p>

<p>In January 2011, "Efficient XML Interchange (EXI) Format 1.0" specification was published as
a <a href="http://www.w3.org/TR/2011/PR-exi-20110120/">Proposed Recommendation</a>.
</p>

<p>In December 2009, the <a href="http://www.w3.org/TR/2009/CR-exi-20091208/">
Candidate Recommendation</a> of the EXI format specification was published in tandem
with the <a href="http://www.w3.org/TR/2009/WD-exi-primer-20091208/">
second working draft</a> of the EXI Primer note.
</p>

<p>In April 2009, the second draft note on the <a href="http://www.w3.org/TR/2009/WD-exi-evaluation-20090407/">
Evaluation of the EXI Format</a> with reference to the
Properties identified by the XBC Working Group, relative to XML, gzipped XML
and ASN.1 PER, was published. </p>

<p>In September 2008, a draft note on
<a href="http://www.w3.org/TR/2008/WD-exi-impacts-20080903/">EXI Impacts</a>
describing the impacts of EXI that may potentially cause to affect existing XML
technologies, XML processors, and applications was published.</p>

<!-- p>In July 2008, a 4th and complete Working Draft of the format specification
is available for review. A draft note on the Evaluation of the EXI Format
with reference to the Properties identified by the XBC Working Group,
relative to XML, gzipped XML and ASN.1 PER, is published. The Working Group
plans to enter Last Call for comments during the summer.</p -->

<!-- p>In March 2008, a 3rd Working Draft of the format specification has been
published (see also: <a
href="http://www.w3.org/TR/2008/WD-exi-20080326/#changes3">list of changes
from the previous draft</a>).</p -->

<p>In December 2007, a draft note on the
<a href="http://www.w3.org/TR/2007/WD-exi-best-practices-20071219/">
EXI Best Practices</a> describing the guidelines for the interoperable
deployment of EXI was published.
</p>

<p>
  Status history that predates the above events are described
<a href="public-status.html">here</a>.
</p>

<!-- p>The First Public Working Draft of the EXI specification was originally
expected in February 2007 (immediately after the <a
href="http://www.w3.org/2007/01/MGMoverview.html">W3C multi-group
meeting</a>, at which we consulted with other Working Groups). This has been
delayed while we have integrated features for efficient structural and value
encodings, schema mapping, support for specialized codecs, and compression.
The First Public Working Draft of the Efficient XML Interchange Format 1.0
has been published on July 16th, 2007. </p -->

<!-- p>In mid November 2006, the EXI group completed measurements of various
candidate encodings and processors for an efficient XML interchange. Based on
the results of that work the group has selected Efficient XML to be the basis
for the proposed encoding specification. Present work centers around
integrating some features from the other measured format technologies into
Efficient XML, particularly variations for both more efficient structural and
value encodings. Additionally, we are drafting the specification of this
format, making some further measurements of the format in a small variety of
network exchanges, and preparing a final release of the full measurements
data and accompanying analysis. </p -->

<h2><a name="Introduction">Background</a></h2>

<p>The Efficient XML Interchange Working Group was chartered to define an
alternative encoding of the XML Information Set, that addressed the
requirements identified by the <a href="http://www.w3.org/XML/Binary/">XML
Binary Characterization (XBC) Working Group</a>, while maintaining the existing
interoperability between XML applications and XML specifications. </p>

<p>The <a href="http://www.w3.org/XML/Binary">XML Binary Characterization (XBC)
Working Group</a> conducted work between March
2004 to March 2005, to gather information about <a
href="http://www.w3.org/TR/xbc-use-cases">uses cases</a> where the overhead
of generating, parsing, transmitting, storing, or accessing XML-based data,
might be deemed too great within the context of those use cases. XBC also
characterized the <a
href="http://www.w3.org/TR/xbc-properties">properties</a> that XML provides
as well as those that are required by the use cases, and established <a
href="http://www.w3.org/TR/xbc-measurement">measurements</a> to help judge
whether XML 1.x and alternate encodings provided the required properties. In
that group's <a
href="http://www.w3.org/TR/xbc-characterization">Characterization
document</a>, the XBC Working Group recommended future work.</p>

<p>The task of this Working Group is to jointly establish and optimize, the
performance of an alternate, non-textual, encoding of XML. At the same time,
disruption to existing processors, and impact on the complex real-world uses
of XML, must be minimized. The Working Group started by considering existing
solutions and has evaluated each in terms of implementability and performance
against the requirements produced by the <a
href="http://www.w3.org/XML/Binary">XBC Working Group</a>. We gathered
together a test data set of more than 10000 documents in 30 or so XML
vocabularies, from a broad range of use case groups, such as Scientific,
Financial, Electronic (those intended for human consumption), Storage
(intended as data stores), etc. The existing solutions, and candidate base
technologies for a potential EXI format, were then measured over a number of
merit criteria, within a benchmark framework based on <a
href="https://japex.dev.java.net/">japex</a>.

The measurements are presented in the <cite><a
href="http://www.w3.org/TR/2007/WD-exi-measurements-20070725/">Efficient XML
Interchange Measurements Note</a></cite></p>

<h2><a name="TestingFramework">Measurement Test Framework</a></h2>

<p>The EXI framework is <a href="framework/exi-ttfms.zip"> available for
download.</a> This measurement test framework was created for the purpose of obtaining
empirical data about format properties. In this release, the framework can be
used to measure <a
href="http://www.w3.org/TR/xbc-properties/#processing-efficiency">Processing
Efficiency</a> and <a
href="http://www.w3.org/TR/xbc-properties/#compactness">Compactness</a> over
a wide variety of XML documents collected by the WG. The framework includes
support for in-memory and network testing, the latter is particularly useful
to measure the performance of a format relative to the available bandwidth.
See the <a href="framework/RELEASE_NOTES.txt">Release Notes</a> for further
information. </p>

<h2><a name="InteropTestingFramework">Interoperability Test Framework</a></h2>

<p>The EXI interoperability framework is <a href="interop-framework/ttfms-interop-28022011.zip">
available for download.</a> This interoperability test framework was created for the purpose of
conducting interoperability assessment as a means to evaluate the clarity of the EXI Format
specification.  It uses XML test files designed to cover features in the EXI specification to
compare the behavior of EXI implementations. The EXI interoperability test framework is not
intended as a means to validate conformance.  However, it may facilitate EXI implementation
development efforts.  See the <a href="interop-framework/interop-README.txt">README</a> for more
information.</p>


<h2><a name="Participation">Participation and Discussion</a></h2>

<p>The Efficient XML Interchange Working Group operates according to this <a
href="http://www.w3.org/XML/2010/10/exi-charter">charter</a>. You can
get involved by <a href="http://www.w3.org/Consortium/#membership">joining
the W3C</a>. The list of the Working Group's participants is available on the <a
href="http://www.w3.org/2004/01/pp-impl/38502/status">WG status page</a>.</p>

<p>The public mailing list for technical discussion with the Working Group is
<a href="mailto:public-exi@w3.org">public-exi@w3.org</a> (<a
href="http://lists.w3.org/Archives/Public/public-exi/latest">Archives</a>).</p>

<p>The public mailing list for sending feedbacks on the EXI format specification is
<a href="mailto:public-exi-comments@w3.org">public-exi-comments@w3.org</a> (<a
href="http://lists.w3.org/Archives/Public/public-exi-comments/latest">Archives</a>).
</p>

<h2><a name="timeline">Timeline</a></h2>

<p>We delivered Efficient XML Interchange (EXI) Format 1.0 Recommendation in March 2011. The definition of further work is soon to be described.
</p>
<!-- p>We plan to reach the Proposed Recommendation stage in January 2011, and publish the Recommendation in February 2011.</p -->
<!-- <dl>
  <dt>January 2007</dt>
    <dd>First Public Working Draft</dd>
  <dt>May 2007</dt>
    <dd>Last Call Working Draft</dd>
  <dt>July 2007</dt>
    <dd>Candidate Recommendation</dd>
  <dt>November 2007</dt>
    <dd>Proposed Recommendation</dd>
  <dt>December 2007</dt>
    <dd>Recommendation</dd>
</dl>
-->

<h2>Patent Disclosures</h2>

<p>W3C maintains a <a rel="disclosure"
href="http://www.w3.org/2004/01/pp-impl/38502/status#specs">public list of
any patent disclosures</a> made in connection with the deliverables of the
group; that page also includes instructions for disclosing a patent.</p>

<h2><a name="implementations">EXI Implementations</a></h2>

<p>Here is a list of publicly available implementations of the EXI 1.0 specifiction, in alphabetical order. </p>

<ul>
  <li><a href="#Efficient_XML">Efficient XML</a> (AgileDelta, Inc.)</li>
  <li><a href="#EXIficient">EXIficient</a> (Open source project initiated by Siemens AG)</li>
  <li><a href="#OpenEXI">OpenEXI</a> &#x2012; Open source project led by Fujitsu</li>
</ul>

<p>If you have an implementation and wish to have it listed, contact the WG chairs or staff (info at the end of the page) with required information specified in <a href="http://lists.w3.org/Archives/Public/public-exi/2008Nov/0000.html">the preliminary Call for Implementations</a>.
</p>

<p>
Enumerated below are summary information pertinent to each implementation listed above, in chronological order determined by when the information was first provided.
</p>

<h3 id="EXIficient">&bull;&nbsp;EXIficient</h3>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Organization</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Open source project initiated by Siemens AG</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >EXIficient Project</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td><a href="http://exificient.sourceforge.net/">http://exificient.sourceforge.net/</a></td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Platform, Language</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Java, OS Independent (written in an interpreted language)</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >License</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>GPL v2</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Description</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>The open source project EXIficient supports all EXI's features and
all coding modes (e.g., bit-packed and compression) in
schema-less as well as in schema-informed mode. More information
about the project can be found on the <a href="http://exificient.sourceforge.net/">project site</a>.
</td>
  </tr>
  </tbody>
</table>

<h3 id="Efficient_XML">&bull;&nbsp;Efficient XML</h3>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Organization</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>AgileDelta, Inc.</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="3" align="left" >About The Project</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td colspan="2"><b>Efficient XML</b></td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td><a href="http://www.agiledelta.com/product_efx.html">
  http://www.agiledelta.com/product_efx.html</a></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td>Efficient XML optimizes the performance, bandwidth utilization and power
consumption of server, desktop, and embedded/mobile XML applications using a
combination of network, processor and small device optimizations. Efficient
XML is built on open web standards and includes support for XML, EXI, XML
Schema, XML DOM, SAX, StAX and other APIs.
</td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td colspan="2"><b>Efficient XML for Web Services</b></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td><a href="http://www.agiledelta.com/product_wsiks.html">
  http://www.agiledelta.com/product_wsiks.html</a></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td>Efficient XML for Web Services provides a turn-key solution for rapidly
adding high performance, native EXI support to popular web-service platforms
and clients. It optimizes the performance, bandwidth utilization and power
consumption of web service applications without requiring code changes.
Efficient XML for Web Services automatically detects clients and servers
that support Efficient XML and falls-back to XML for those that don't.
</td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td colspan="2"><b>Efficient XML HTTP Proxies</b></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td><a href="http://www.agiledelta.com/product_proxies.html">
  http://www.agiledelta.com/product_proxies.html</a></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td>Efficient XML HTTP Proxies provide a turn-key solution for rapidly adding
high performance Efficient XML support to individual web applications,
wireless links or entire networks. They optimize the bandwidth utilization
of XML network traffic without requiring code changes. Efficient XML proxies
automatically detect clients, servers and networks that support Efficient
XML and fall-back to XML for those that don't.
</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="3" align="left" >Platform, Language</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td colspan="2"><b>Efficient XML</b></td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>
	Java Standard Edition and Java Mobile Edition (any Java platform)
	.NET Framework and .NET Compact Framework (any .NET language)
	Native C/C++ (servers, desktops and small devices)
</td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td colspan="2"><b>Efficient XML for Web Services</b></td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>
	Apache Axis 1.x and Apache Axis2
	Oracle/BEA WebLogic
	Microsoft Windows Communication Framework (WCF)
</td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td colspan="2"><b>Efficient XML HTTP Proxies</b></td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>
	Any Java SE platform (OS independent)
</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >License</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Commercial with free 30-day trial</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="3" align="left" >Maturity Statement</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td colspan="2"><b>Efficient XML</b></td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Efficient XML is a mature, 4th generation, commercial product that provides
complete, high performance and low-footprint implementations of the EXI
standard. It is professionally supported and continuously improved by the
company that developed the Efficient XML technology.
</td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td colspan="2"><b>Efficient XML for Web Services</b></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td>Efficient XML for Web Services is a mature, commercial product that provides
complete, high performance implementations of the EXI standard. It is
professionally supported and continuously improved by the company that
developed the Efficient XML technology.
</td>
  </tr>
  <tr>
  <td colspan="2"></td>
  <td colspan="2"><b>Efficient XML HTTP Proxies</b></td>
  </tr>
  <tr>
  <td colspan="3"></td>
  <td>Efficient XML HTTP proxies are mature commercial products that provide
complete implementations of the EXI standard. They are professionally
supported and continuously improved by the company that developed the
Efficient XML technology.
</td>
  </tr>
  </tbody>
</table>

<h3 id="OpenEXI">&bull;&nbsp;OpenEXI</h3>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Organization</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Open source project led by Fujitsu</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >OpenEXI Project</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td><a href="http://openexi.sourceforge.net/">http://openexi.sourceforge.net/</a></td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Platform, Language</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>OS Independent</td>
  </tr>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Written in Java</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >License</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>Apache License, Version 2.0</td>
  </tr>
  </tbody>
</table>

<table>
  <thead>
  <tr>
  <th>&nbsp;&nbsp;&nbsp;&nbsp;</th>
  <th colspan="2" align="left" >Description</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
  <td>
OpenEXI is a implemention of the EXI specification in Java. For more information about the project and its status, please visit the <a href="http://openexi.sourceforge.net/">project page</a>.
</td>
  </tr>
  </tbody>
</table>

<hr />
<address>
  Michael Cokus, <a href="mailto:tkamiya@us.fujitsu.com">Takuki Kamiya</a>, Chairs,<br />
  <a href="mailto:carine@w3.org">Carine Bournez</a>, W3C Team contact. <br />
  <small>$Id: index.html,v 1.68 2011/08/10 19:51:05 carine Exp $</small>
</address>

<p class="copyright"><a rel="Copyright"
href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a>© 2008 <a
href="/"><acronym
title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a
href="http://www.lcs.mit.edu/"><acronym
title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
href="http://www.ercim.org/"><acronym
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a
href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a
rel="Copyright" href="/Consortium/Legal/copyright-documents">document use</a>
and <a rel="Copyright" href="/Consortium/Legal/copyright-software">software
licensing</a> rules apply. Your interactions with this site are in accordance
with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="/Consortium/Legal/privacy-statement#Members">Member</a> privacy
statements.</p>
</body>
</html>