Re: [Json] 2-step proposal 4627bis + I-JSON

"Pete Cordell" <petejson@codalogic.com> Thu, 04 July 2013 12:09 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A3621F934C for <json@ietfa.amsl.com>; Thu, 4 Jul 2013 05:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.482
X-Spam-Level: *
X-Spam-Status: No, score=1.482 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, SARE_HEAD_XUNSENT=1.666, STOX_REPLY_TYPE=0.001]
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 oRAT6JvYTwP6 for <json@ietfa.amsl.com>; Thu, 4 Jul 2013 05:09:16 -0700 (PDT)
Received: from codalogic.com (codalogic.com [94.136.60.219]) by ietfa.amsl.com (Postfix) with ESMTP id 6264121F9FC8 for <json@ietf.org>; Thu, 4 Jul 2013 05:09:14 -0700 (PDT)
Received: (qmail 3657 invoked from network); 4 Jul 2013 13:09:12 +0100
Received: from host86-184-169-224.range86-184.btcentralplus.com (HELO codalogic) (86.184.169.224) by codalogic.com with (RC4-MD5 encrypted) SMTP; 4 Jul 2013 13:09:12 +0100
Message-ID: <994CFCB1858040FA8C81A0A11CC1452D@codalogic>
From: "Pete Cordell" <petejson@codalogic.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, "Tim Bray" <tbray@textuality.com>, <json@ietf.org>
References: <CAHBU6itqGgndUKRUHH_q6fv8jonGL3VVHhkezFne0sC3T12c_Q@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151C19AD73@WSMSG3153V.srv.dir.telstra.com>
X-Unsent: 1
Date: Thu, 4 Jul 2013 13:09:09 +0100
x-vipre-scanned: 008D7F82004B50008D80CF
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Subject: Re: [Json] 2-step proposal 4627bis + I-JSON
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Jul 2013 12:09:20 -0000

Original Message From: "Manger, James H"
> To: "Tim Bray"
>> 2. Recharter in a way that will allow us to produce something like a
>> strawman I cooked up, I-JSON: https://www.tbray.org/tmp/i-json.html
>> Produce something like that. Second victory!
>> -T

+1, while I'm here, but...

> "urn:ietf:i-json":true  -- Ugh? Why? How do you think this would be used 
> by apps receiving
> JSON? Do they switch between rejecting dups vs accepting last dup based on 
> the presence
> of this element? Sounds unlikely.

I too am a bit 'meh' on the self identification part.  (Knowing it's I-JSON 
is not even half way to knowing what you really want to know surely.)

Extending it to something like:

    "urn:ietf:i-json:jose" : true

or:

    "urn:ietf:i-json:com.codalogic:myprotocol:v2" : true

has some attraction though.  Although I think this would be more in the 
realms of convention than requirement.

Or an alternative syntax of:

    "urn:ietf:i-json" : "jose"
or:
    "urn:ietf:i-json" : "com.codalogic.myprotocol.v2"


Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com