IETF Logo Mail Archive

Re: [Json] I-JSON Topic #1: Media Types?

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 30 April 2014 04:40 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 552481A08A8 for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 21:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.442
X-Spam-Level:
X-Spam-Status: No, score=-0.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=no
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 3D42kGx5mFDD for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 21:40:27 -0700 (PDT)
Received: from scintmta01-14.scbb.aoyama.ac.jp (scintmta01-14.scbb.aoyama.ac.jp [133.2.253.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8FA1A0A37 for <json@ietf.org>; Tue, 29 Apr 2014 21:40:27 -0700 (PDT)
Received: from scmeg01-14.scbb.aoyama.ac.jp (scmeg01-14.scbb.aoyama.ac.jp [133.2.253.15]) by scintmta01-14.scbb.aoyama.ac.jp (Postfix) with ESMTP id 2D84E32E557; Wed, 30 Apr 2014 13:40:23 +0900 (JST)
Received: from itmail2.it.aoyama.ac.jp (unknown [133.2.206.134]) by scmeg01-14.scbb.aoyama.ac.jp with smtp id 3dce_d0dc_c7162d94_a25a_4857_bf05_5de094f96c7c; Wed, 30 Apr 2014 13:40:22 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 8FC03C0358; Wed, 30 Apr 2014 13:40:22 +0900 (JST)
Message-ID: <53607EA9.50204@it.aoyama.ac.jp>
Date: Wed, 30 Apr 2014 13:40:09 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
References: <535EAFDF.2020403@cisco.com> <6456FCD4-E410-4FAB-96D0-E46260AABD9D@vpnc.org>
In-Reply-To: <6456FCD4-E410-4FAB-96D0-E46260AABD9D@vpnc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/EPxSC1V1LhO9GeoVvPWqJ41RfzM
Subject: Re: [Json] I-JSON Topic #1: Media Types?
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: Wed, 30 Apr 2014 04:40:29 -0000

+1. I have given my arguments already months ago, and they are much the 
same as given here recently by many.

Regards,   Martin.

On 2014/04/30 02:26, Paul Hoffman wrote:
> <no hat>
>
>> "Should there be an I-JSON media type, or a application/*+i-json
>> suffix?  Draft i-json-01 calls for it, but this is at best controversial."
>
> No. A receiver can check whatever data it gets against whatever rules it wants. I-JSON is a standardized set of rules that an emitter probably wants to follow. And emitter saying "Look! I followed those rules!" cannot be trusted anyway.
>
> --Paul Hoffman
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email