IETF Logo Mail Archive

Re: JSON headers

Julian Reschke <julian.reschke@gmx.de> Mon, 11 July 2016 07:31 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2AE612D0CE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 00:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.208
X-Spam-Level:
X-Spam-Status: No, score=-8.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zMFeJGULNqns for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 11 Jul 2016 00:31:06 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98CBF12B00A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 11 Jul 2016 00:31:06 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bMVcC-0000jC-KX for ietf-http-wg-dist@listhub.w3.org; Mon, 11 Jul 2016 07:26:52 +0000
Resent-Date: Mon, 11 Jul 2016 07:26:52 +0000
Resent-Message-Id: <E1bMVcC-0000jC-KX@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bMVc9-0000iG-Ly for ietf-http-wg@listhub.w3.org; Mon, 11 Jul 2016 07:26:49 +0000
Received: from mout.gmx.net ([212.227.15.15]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bMVc7-0001gY-J1 for ietf-http-wg@w3.org; Mon, 11 Jul 2016 07:26:48 +0000
Received: from [192.168.178.20] ([93.217.94.167]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MZkv0-1bgma43POo-00LTj9; Mon, 11 Jul 2016 09:26:10 +0200
To: Jim Manico <jim@manicode.com>
References: <74180.1468000149@critter.freebsd.dk> <A17D3EFD-A935-4971-BCF6-DC9D38302CAD@oracle.com> <564a72e8-b9d3-1f9c-5982-48f2b07272e5@greenbytes.de> <3924.1468137899@critter.freebsd.dk> <683f5f58-6046-d9fb-cc75-d0ab3890ce23@greenbytes.de> <4105.1468141779@critter.freebsd.dk> <5cdf0fa8-063c-7eaa-a9e3-fb6db7417254@gmx.de> <4213.1468143913@critter.freebsd.dk> <94e4a5c2-3465-fef3-6221-d9f4fcccb5fa@gmx.de> <4324.1468145426@critter.freebsd.dk> <CAB0No9kf6gje3Tc+impphV5tUHjksCkL1PJ1YAgNjXO+tLq=XA@mail.gmail.com> <176d58df-debf-e660-edf7-7d686c926ef6@gmx.de> <5939.1468189218@critter.freebsd.dk> <94d7c36a-7d6d-11bf-27b6-2e6a2b807b09@it.aoyama.ac.jp> <78B70240-C73B-4298-B811-9D165CEA540A@manicode.com> <c5391b2b-76d9-6122-2675-0208115923bc@gmx.de> <918A0393-5855-417E-B126-E5417FD53C22@manicode.com>
Cc: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Poul-Henning Kamp <phk@phk.freebsd.dk>, Yanick Rochon <yanick.rochon@gmail.com>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <35b56698-5d26-24a5-a049-258783e44998@gmx.de>
Date: Mon, 11 Jul 2016 09:26:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <918A0393-5855-417E-B126-E5417FD53C22@manicode.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:L6JJIDecCou/XCLR1YRQzcPPm+xTc3GOTONcIKcX0e2SSuJ8mCw SyZynySEFQad++qOwBwiQCCvX+Lwn++ECyyE5hW4ciRKCdnkitMqck+mRWc5y08sstSkQjr WM5BI9+ziRy9gAGtYxhtNubeWclNvrqAo6bGy8PIvyNeLaq2N+DtkD6liYK1GhtvFvxZd5m m9/L6+mKJEBevnE/Btgkg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:mb+BMDsZZ1U=:R/BwtbjeLIw8kUWiWrm0km ZMHwY0VCZvd/sEs6Tw1O2rwybgxfDLeogbv0gaKBfIFv/BHWmjgHpGDs1QsSFkXiMt4B/tp5M 0+vLZKrz5bQWeRAenzbm8GlX7P9WHeu0CnA6mk0/Omr6zSHK3P0ipOFDPDJ9pLNyiEGZyUQS2 1XdA/Hzz/4xwB66eN4TNil61WW0+rbG52sxKfVVgWCtwplSoEA90m46MWItzmPPoRAsepCcW2 6YQ16Tmtv0/5ZfDiyGJ8DteB2oSjoYnKyKzgxodnqGbvKF6i7R2RlHl2cTJuAU/Oxi4esODMT VLcizS5Ua9XQjycHBM0qnjlhkgWXBLqXKGM6NKylE9A8oLzsLAeoruUtGpbp6lPU/BDRIaIvB xU/sRbh+nbWzeS6UpJS959QIL0QFmoaIUElT9XETiC083kbeWYS4IP3pD+learyVNp8yFB2Tq 8ZSAFqHMh4gmnrQUjUowtsO3AvMx0Sn/JADUa1mB47+4xuFJk2xmkK3rR/APbmFYK6il0XKB3 TVfHOTzmBeTKiYzW21Kl0jQXgrzxgz7sG8DbzWvYq6/oul1pCKVT3FkAFktNhDBehwz/6qIZE FRY1iXq9g7Jh1gFGHBT6hBcl4IhY7BL26Ey5gHVlQbUj14Dr0By0mdz9AeI/apdc/BO3guDaJ B8B5Q41zfvMWc0J66EhT7WYiRvuxTqi0afeNLuVcI6+9/4ACVP2gF/phUAKK7HVKbdeKYH/BE t4CNMyVc50AH0oJLv759h89Hc0yk8bOEkNTkJrLmU8ywkNAOqSW6mdA8CtcrXEkk7sjcMKbGe zqo2RDK
Received-SPF: pass client-ip=212.227.15.15; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-6.7
X-W3C-Hub-Spam-Report: AWL=-0.077, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bMVc7-0001gY-J1 08b9ff5dd19fb069ab8283842373d5d7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: JSON headers
Archived-At: <http://www.w3.org/mid/35b56698-5d26-24a5-a049-258783e44998@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31885
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 2016-07-11 09:10, Jim Manico wrote:
> < How does JSON-Schema affect what a RFC7159-compliant JSON parser does?
> (Remember the problem is on the producing side)
>
> We're talking higher level standards that consume JSON in some way, right? So the producer would run the final JSON through a standard JSON-Schema before shipping off the JSON to ensure compliance (ensuring the producer work is accurate), and the consumer would use the same Schema to validate before parsing (so we can catch bad JSON way before a fragile parser gets involved).
>
> This is nothing special, many frameworks that do JSON-Object mapping do this already...

Just like senders validate what they send today :-)

Best regards, Julian

v2.23.0 | Report a Bug | By Email