IETF Logo Mail Archive

[apps-discuss] proposal: adding profile support to JSON

Erik Wilde <dret@berkeley.edu> Sun, 03 November 2013 17:27 UTC

Return-Path: <dret@berkeley.edu>
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 844AD11E821D for <apps-discuss@ietfa.amsl.com>; Sun, 3 Nov 2013 09:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0Qsydtxdrdcy for <apps-discuss@ietfa.amsl.com>; Sun, 3 Nov 2013 09:27:44 -0800 (PST)
Received: from cm05fe.IST.Berkeley.EDU (cm05fe.IST.Berkeley.EDU [169.229.218.146]) by ietfa.amsl.com (Postfix) with ESMTP id 3C35511E8196 for <apps-discuss@ietf.org>; Sun, 3 Nov 2013 09:27:43 -0800 (PST)
Received: from [207.194.238.3] (helo=dretair.local) by cm05fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1Vd1Sg-0007Ng-Gt for apps-discuss@ietf.org; Sun, 03 Nov 2013 09:27:43 -0800
Message-ID: <5276878A.6000802@berkeley.edu>
Date: Sun, 03 Nov 2013 09:27:38 -0800
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] proposal: adding profile support to JSON
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: Sun, 03 Nov 2013 17:27:48 -0000

hello.

seeing that http://tools.ietf.org/html/draft-ietf-json-rfc4627bis is 
making good progress, i wanted to raise the question of maybe adding 
profile support to the JSON media type.

http://tools.ietf.org/html/draft-wilde-atom-profile is a proposal for 
adding profile support to the atom media type, and the "profile" 
optional media type parameter 
(http://tools.ietf.org/html/draft-wilde-atom-profile-02#section-4.1.1) 
is what could be added to JSON as well.

the advantage would be that different JSON-based formats could be 
distinguished by their (mediatype+profile). this would allow JSON-based 
formats to become more visible on the web level, instead of always just 
saying "i am JSON", without any ability to differentiate.

thanks and cheers,

dret.

-- 
erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |

v2.23.0 | Report a Bug | By Email