IETF Logo Mail Archive

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

Erik Wilde <dret@berkeley.edu> Tue, 05 November 2013 21:47 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 0D88B21F9B10 for <apps-discuss@ietfa.amsl.com>; Tue, 5 Nov 2013 13:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.168
X-Spam-Level:
X-Spam-Status: No, score=-6.168 tagged_above=-999 required=5 tests=[AWL=0.431, 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 9w69jTzlp6PL for <apps-discuss@ietfa.amsl.com>; Tue, 5 Nov 2013 13:47:34 -0800 (PST)
Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) by ietfa.amsl.com (Postfix) with ESMTP id 7BFF611E80E3 for <apps-discuss@ietf.org>; Tue, 5 Nov 2013 13:47:32 -0800 (PST)
Received: from dhcp-a1c6.meeting.ietf.org ([31.133.161.198]) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1VdoTC-0001O1-CM; Tue, 05 Nov 2013 13:47:32 -0800
Message-ID: <52796772.7030000@berkeley.edu>
Date: Tue, 05 Nov 2013 13:47:30 -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: Tim Bray <tbray@textuality.com>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
References: <5276878A.6000802@berkeley.edu> <5278AF21.90605@it.aoyama.ac.jp> <CAHBU6iuAoNT1QYH3DKA_KFA4Ngm5Y2hyHm-2_8z5kv8fGKHY1Q@mail.gmail.com>
In-Reply-To: <CAHBU6iuAoNT1QYH3DKA_KFA4Ngm5Y2hyHm-2_8z5kv8fGKHY1Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [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: Tue, 05 Nov 2013 21:47:42 -0000

hello.

On 2013-11-05, 07:57 , Tim Bray wrote:
> Well, for example, http://www.tbray.org/tmp/draft-bray-i-json-01.html

while i of course like the idea of I-JSON being a profile of JSON, if 
that's supposed to work in the same way as RFC 6906 ("The 'profile' Link 
Relation Type") specifies, then

http://tools.ietf.org/html/draft-bray-i-json-00.html#section-2.1

and

http://tools.ietf.org/html/rfc6906#section-3.1

are in conflict. that's because RFC-6906 profile identifiers must be 
URIs. one option therefore might be to use something like 
urn:ietf:rfc:XXXX as the profile identifier (or something else, if it 
should be stable before the RFC number is assigned).

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