IETF Logo Mail Archive

Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Sun, 06 July 2014 04:48 UTC

Return-Path: <jhildebr@cisco.com>
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 02B751A01A9 for <json@ietfa.amsl.com>; Sat, 5 Jul 2014 21:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.697
X-Spam-Level:
X-Spam-Status: No, score=-12.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 69QoCeo1kQYS for <json@ietfa.amsl.com>; Sat, 5 Jul 2014 21:48:35 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDA9E1A019A for <json@ietf.org>; Sat, 5 Jul 2014 21:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=772; q=dns/txt; s=iport; t=1404622115; x=1405831715; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=POwb2lYth/hVhNFIDnyTQmwsy0NUWiD+waVD9xRBptg=; b=emZwG5kCuNvHjL0EjlNEYQBXoThKbrxzxQ78NKD7C/NgE/0ojmU8ypGe NlcaOFNyYS+keYY4+I7/CRWJqYivawuWpSrjucwef+NxHwJfAfdR7HmTC YL1dWCCncHQSWYKJrIFPAN7Lt9uA2w1ZQ2c/4sxYaWmD+isWJBLVF5yN6 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAOjTuFOtJV2a/2dsb2JhbABagw6BLIJvwXmBQwEZcRZ1hAQBAQQjEUUQAgEIGgImAgICMBUQAgQBDQWIQrAWmVUXgSyNQzMHgneBTAEEmnaUDINDgXAkHA
X-IronPort-AV: E=Sophos;i="5.01,610,1400025600"; d="scan'208";a="337954278"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 06 Jul 2014 04:48:34 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s664mYZE030486 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 6 Jul 2014 04:48:34 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Sat, 5 Jul 2014 23:48:33 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Larry Masinter <masinter@adobe.com>, Mark Baker <distobj@acm.org>, Tim Bray <tbray@textuality.com>
Thread-Topic: [Json] Media types, extensibility in draft-ietf-json-i-json-02
Thread-Index: AQHPli3TeLKmyOx7w0yav7qrcKonZpuQpE0AgADBdgCAAQgygA==
Date: Sun, 06 Jul 2014 04:48:33 +0000
Message-ID: <CFDE30C2.52BE7%jhildebr@cisco.com>
References: <CALcoZionwZ1gn0hkhq4sKcDKg3LK13+d-XvBzXUA4iHjS6PHNA@mail.gmail.com> <CAMm+LwgU5veinaNJ6ptLJ509QD3R5=LEbpfmNjZSy5C+8jfPXg@mail.gmail.com> <CAHBU6iuc2j4a5VYnrboMEMnAPxhs5i+iZxfpbfnN1oa3740TfQ@mail.gmail.com> <CALcoZioTakxzkuvrt1EgNAKS==NNskWJ1TLUjxtZ1TBGPD+EXw@mail.gmail.com> <CFDCB00F.52A7B%jhildebr@cisco.com> <3b407fff0cc14d5ba291cea58bacac4f@BL2PR02MB307.namprd02.prod.outlook.com>
In-Reply-To: <3b407fff0cc14d5ba291cea58bacac4f@BL2PR02MB307.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.82.226.107]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1AC291DB0FAA694CAD949D9A4CC90517@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/g2zxsts6Jdt2gFFF6JUhxbwqj_4
Cc: Phillip Hallam-Baker <ietf@hallambaker.com>, JSON WG <json@ietf.org>
Subject: Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02
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: Sun, 06 Jul 2014 04:48:37 -0000

On 7/5/14, 1:02 AM, "Larry Masinter" <masinter@adobe.com> wrote:

>In this particular case, I can't think of a situation
>where you wouldn't also want to validate other constraints
>as well.

I think the implication of us publishing I-JSON at all is that there are
many people that might want to start with this set of constraints.  If we
don't think that is the case, we shouldn't publish the doc as an RFC.
None of the I-JSON constraints are domain-specific, unlike most of the
other constraints you will want to check.

-- 
Joe Hildebrand

v2.37.1 | Report a Bug | By Email | System Status