W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > March 2010

Re: Requesting IESG Approval for the Media Type application/exi

From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Thu, 04 Mar 2010 18:14:47 +0000
Message-ID: <4B8FF897.2020307@isode.com>
To: Philippe Le Hegaret <plh@w3.org>
CC: iesg@ietf.org, public-ietf-w3c@w3.org, Dan Connolly <connolly@w3.org>, Carine Bournez <cbournez@w3.org>
Philippe Le Hegaret wrote:

>Dear IESG participants,
Dear Philippe (and W3C),
IESG has no problems registering this MIME type.

However IESG would like to ask one (non blocking) question, which might 
result in update to the registration:

Many EXI documents can not be understood without the associated grammar 
which does not have to be provided inside the EXI doc. It might be good 
to define an optional parameter that provides a URI or some sort of name 
to find the associated grammar.

Please let IESG know if you would like to update the registration, or if 
you want to register it as is.

>This message is to request approval for the registration of the media
>type "application/exi", as described in Appendix F.2 of "Efficient XML
>Interchange (EXI) Format 1.0":
> http://www.w3.org/TR/exi/#internetMediaType
>This message follows the procedure described in the Media Type
>Specifications and Registration Procedures, section 5.2, "IESG
>Approval" [1]. The proposed media type were sent for preliminary
>community review on :
> http://www.alvestrand.no/pipermail/ietf-types/2008-October/002103.html
>Questions were asked regarding the need to have a media type for EXI,
>resulting after clarifications in the addition of the following
>paragraph in the document:
>Consideration of alternatives : 
>When transferring EXI streams over a protocol that can identify and
>negotiate the content coding of XML information independent of its
>media-type, the content-coding should be used to identify and negotiate
>how the XML information is encoded and the media-type should be used to
>negotiate and identify what type of information is transfered. 
>We believe the media type is now ready for IESG approval.
>Thank you, 
>[1] http://www.ietf.org/rfc/rfc4288.txt

IETF Application Area Director, <http://www.ietf.org/IESGmems.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address
Received on Thursday, 4 March 2010 18:15:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:09:55 UTC