Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments

Peter Saint-Andre <stpeter@stpeter.im> Wed, 09 November 2011 16:31 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 2FC7421F8B03 for <apps-discuss@ietfa.amsl.com>; Wed, 9 Nov 2011 08:31:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 MEBxnNLQSIm4 for <apps-discuss@ietfa.amsl.com>; Wed, 9 Nov 2011 08:31:24 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 013A221F8A70 for <apps-discuss@ietf.org>; Wed, 9 Nov 2011 08:31:24 -0800 (PST)
Received: from normz.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A558D420DE; Wed, 9 Nov 2011 09:37:19 -0700 (MST)
Message-ID: <4EBAAAD8.8000903@stpeter.im>
Date: Wed, 09 Nov 2011 09:31:20 -0700
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: Julian Reschke <julian.reschke@gmx.de>
References: <4EB923CF.7080600@wp.pl> <566A345F-15CD-473B-8472-11EDF73A3862@vpnc.org> <9D5B00CA-9370-45D6-835B-3C7A1ADFEBBC@mnot.net> <4EB97122.7010206@gmx.de> <D75C8075-C8DF-4AA2-9DFC-CED719A0564E@mnot.net> <4EB98090.5020203@gmx.de>
In-Reply-To: <4EB98090.5020203@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, Paul Hoffman <paul.hoffman@vpnc.org>, apps-discuss Discuss <apps-discuss@ietf.org>, Dominik Tomaszuk <ddooss@wp.pl>
Subject: Re: [apps-discuss] draft-saintandre-json-namespaces-00 comments
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, 09 Nov 2011 16:31:28 -0000

On 11/8/11 12:18 PM, Julian Reschke wrote:
> On 2011-11-08 20:10, Mark Nottingham wrote:
>> I don't think URIs should be used for this.
>> ...
>
> Well, one use case that the proposal is addressing is the transport of
> data from frameworks that *already* use URIs; such a WebDAV properties
> or JCR identifiers. In these cases you really have only the choice of
> using the identifiers you have, or establishing a completely new
> identifier system.
>
> And yes, it would be helpful if the draft was just saying that and not
> make the impression that it was solving the generic problem for JSON.

There's always an opportunity for publishing -01. ;-)

I agree that a range of approaches might be appropriate among JSON-using 
communities -- pretty much the same range of approaches mentioned in the 
x- draft:

        implementation-specific and
        private-use parameters could at least incorporate the
        organization's name (e.g., "ExampleInc-foo" or, consistent with
        [RFC4288], "VND.ExampleInc.foo") or primary domain name (e.g.,
        "com.example.foo" or a Uniform Resource Identifier [RFC3986] such
        as "http://example.com/foo").

I'll work with my co-authors to submit -01 next week or soon thereafter.

Peter

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