W3C home > Mailing lists > Public > public-exi@w3.org > August 2007

RE: How to distinguish XML and EXI

From: Vogelheim, Daniel <daniel.vogelheim@siemens.com>
Date: Tue, 7 Aug 2007 19:01:50 +0200
Message-ID: <D720D1DD80557241B9452630315560C30163D6C6@MCHP7IEA.ww002.siemens.net>
To: "Kenichi Taniuchi" <ktaniuchi@tari.toshiba.com>
Cc: <public-exi@w3.org>

Hello Kenichi,

> Another question is came.
> Do you think new MIME definition will be needed for EXI for
> some protocols ?

Probably yes, but that is still an open question. We've actually been
discussing this very issue at a recent meeting, and we plan on
publishing a 'Best Practices' document to accompany the spec to deal
with questions like this.

In an HTTP setting, the current thinking is that EXI would ideally be
used as an HTTP content encoding, so that it would work transparently
with the existing HTTP content negotiation features. For other settings
or protocols (like serving/storing static files), a MIME type might
indeed be useful or even required.

The EXI WG plans on collecting some more feedback on the issue, and then
determine whether to approach IANA on a new MIME type or not.


Kenichi, if you have some specific use cases or arguments for or against
an EXI MIME type, we would keep them in mind when making our decision.


Sincerely,
Daniel Vogelheim
Received on Tuesday, 7 August 2007 17:02:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:42 UTC