[apps-discuss] +exi (was: Re: type name suffixes)

Peter Saint-Andre <stpeter@stpeter.im> Wed, 16 November 2011 02:59 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABF521F8F25 for <apps-discuss@ietfa.amsl.com>; Tue, 15 Nov 2011 18:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.805
X-Spam-Level:
X-Spam-Status: No, score=-102.805 tagged_above=-999 required=5 tests=[AWL=-0.206, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJzB+KPDBMzu for <apps-discuss@ietfa.amsl.com>; Tue, 15 Nov 2011 18:59:14 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EFFE121F8F24 for <apps-discuss@ietf.org>; Tue, 15 Nov 2011 18:59:13 -0800 (PST)
Received: from dhcp-15ab.meeting.ietf.org (unknown [64.104.46.217]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id BE7834214E; Tue, 15 Nov 2011 20:05:27 -0700 (MST)
Message-ID: <4EC326FE.1010809@stpeter.im>
Date: Wed, 16 Nov 2011 10:59:10 +0800
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <4EBB2B83.3060901@it.aoyama.ac.jp> <01O88AB2EM7S00RCTX@mauve.mrochek.com> <4EBBB0EE.8050502@it.aoyama.ac.jp> <01O88YVG6MQY00RCTX@mauve.mrochek.com> <4EBCCE76.2090807@it.aoyama.ac.jp> <01O8AM6GDT5000RCTX@mauve.mrochek.com> <4EC0CCAE.5070402@stpeter.im> <01O8EWMK2T8E00RCTX@mauve.mrochek.com> <4EC2DC42.7010307@stpeter.im> <01O8GE5O3B5K00RCTX@mauve.mrochek.com> <C68CB012D9182D408CED7B884F441D4D0611DAC31D@nambxv01a.corp.adobe.com> <4EC31F1E.6070304@stpeter.im> <8p86c7d6chvadsku6k5dhct20qkl7uk73l@hive.bjoern.hoehrmann.de>
In-Reply-To: <8p86c7d6chvadsku6k5dhct20qkl7uk73l@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.3.3
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] +exi (was: Re: type name suffixes)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 02:59:18 -0000

On 11/16/11 10:45 AM, Bjoern Hoehrmann wrote:
> * Peter Saint-Andre wrote:
>> To be clear, the two suffixes I've seen interest in are:
>>
>> +json = <http://tools.ietf.org/html/rfc4627>
>>
>> +exi = <http://www.w3.org/TR/2011/REC-exi-20110310/>
> 
> (I was under the impression the W3C had decided against "+exi" suffixes,
> and instead use the "exi" content coding as the specification there re-
> commends. I'd rather not duplicate all "+xml" entries with "+exi" types)

So, let's say I have "foo" data that can be represented in either plain
old XML or as EXI. If I send that "foo" data as plain old XML, the
"application/foo+xml" media type is right. If I send that "foo" data as
EXI, the "application/foo+exi" media type seems wrong, and so does the
"application/exi" media type (just as "application/xml" would not be
right for the first encoding). Sure, I don't particularly want to
duplicate all "+xml" entries with "+exi" entries, but I don't think that
every protocol or community that sends around XML data will also send
around EXI-encoded data.

But I freely admit that I might be missing context or historical
information about the W3C's decisions in this area.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/