IETF Logo Mail Archive

Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)

Larry Masinter <masinter@adobe.com> Thu, 13 March 2014 21:39 UTC

Return-Path: <masinter@adobe.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742EC1A075E for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLuxny-bEFia for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:39:51 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id 733A61A0754 for <json@ietf.org>; Thu, 13 Mar 2014 14:39:51 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB306.namprd02.prod.outlook.com (10.141.91.19) with Microsoft SMTP Server (TLS) id 15.0.893.10; Thu, 13 Mar 2014 21:39:43 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0893.001; Thu, 13 Mar 2014 21:39:43 +0000
From: Larry Masinter <masinter@adobe.com>
To: Nico Williams <nico@cryptonector.com>, Matthew Morley <matt@mpcm.com>
Thread-Topic: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
Thread-Index: AQHPPK1+m0ZN/rvGs0aL4VgGaA1MH5ra4iQAgAEiVACAABS3AIADdeeg
Date: Thu, 13 Mar 2014 21:39:43 +0000
Message-ID: <3416a6327a8a4cd3b49bee3c2e548870@BL2PR02MB307.namprd02.prod.outlook.com>
References: <CAK3OfOj_XQJq-JKAjNdH-GuH0_UwZfeWntgyyizMpTLmSaWQoA@mail.gmail.com> <CAK3OfOio58+1yuxQOcvWep1CADMfE1PVC48XDid0dWvd8=SVjA@mail.gmail.com> <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com> <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com>
In-Reply-To: <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.150.10.210]
x-forefront-prvs: 01494FA7F7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(199002)(189002)(81686001)(53806001)(76482001)(69226001)(83322001)(86362001)(54356001)(51856001)(46102001)(65816001)(93516002)(83072002)(66066001)(74706001)(59766001)(80022001)(77982001)(93136001)(85852003)(50986001)(76796001)(76786001)(76576001)(80976001)(33646001)(56776001)(49866001)(4396001)(81342001)(81816001)(74366001)(47736001)(2656002)(92566001)(95666003)(87266001)(74662001)(31966008)(97186001)(94316002)(97336001)(74502001)(47976001)(79102001)(74876001)(74316001)(56816005)(95416001)(94946001)(81542001)(47446002)(90146001)(87936001)(85306002)(63696002)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR02MB306; H:BL2PR02MB307.namprd02.prod.outlook.com; CLIP:192.150.10.210; FPR:D326E60C.94121E61.C0EB304B.88E52ED8.20146; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/json/ObiDTwFvVoFhwoSEhXV_BwAVU0c
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Mar 2014 21:39:53 -0000

> Arguably JSON text sequences are a new format,

yes

> deserving of its own MIME type and so on.

no, not all formats need MIME types. There are infinitely many formats. 
MIME is one way of noting a file format and distinguishing it from others, but most applications don't NEED to name the types they accept and in general, they can't.

I think to justify a new MIME type, you need to provide a concrete use case that would actually use it and need it.  In most of the content-negotiation scenarios, MIME types are far too course-grained to express content-features.

v2.23.0 | Report a Bug | By Email