Re: EXI and XML Core

> > So in e.g. an HTTP transmission, EXI would
> > show up as a Content-Encoding:-option

This isn't quite right.  If EXI is a content encoding, the result of
EXI decoding should be a document of the specified content type,
application/xml for example.  It should be an octet stream that you
can feed to an XML parser.  But it isn't, it's an infoset.

The difference between XML and EXI is more like the difference
between JPG and GIF - you don't decode JPG to get a GIF; they
are alternative representations of the same abstract image, and
XML and EXI are alternative representations of the same infoset.

You could resolve this by saying that in theory an EXI implementation
serializes the result to produce an XML document, which is then
parsed.  The real implementation would then be considered just an
optimization.

-- Richard