IETF Logo Mail Archive

Re: JFV and Common Structure specifications

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Wed, 23 November 2016 18:44 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 91127129CA9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 10:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, 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 51aAKlTEwB1w for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 10:44:00 -0800 (PST)
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 83B14129E23 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Nov 2016 10:44:00 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c9cSO-0002LJ-Jd for ietf-http-wg-dist@listhub.w3.org; Wed, 23 Nov 2016 18:39:44 +0000
Resent-Date: Wed, 23 Nov 2016 18:39:44 +0000
Resent-Message-Id: <E1c9cSO-0002LJ-Jd@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <phk@phk.freebsd.dk>) id 1c9cSI-0002KN-Ce for ietf-http-wg@listhub.w3.org; Wed, 23 Nov 2016 18:39:38 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by titan.w3.org with esmtp (Exim 4.84_2) (envelope-from <phk@phk.freebsd.dk>) id 1c9cSC-0002V8-DY for ietf-http-wg@w3.org; Wed, 23 Nov 2016 18:39:33 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 2F727273C2; Wed, 23 Nov 2016 18:39:07 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id uANId4WD089292; Wed, 23 Nov 2016 18:39:05 GMT (envelope-from phk@phk.freebsd.dk)
To: Julian Reschke <julian.reschke@gmx.de>
cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>, Patrick McManus <mcmanus@ducksong.com>
In-reply-to: <44dafe6e-3049-287d-34c8-994bdf27c02c@gmx.de>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <3A206EA7-57FB-4913-BC08-445BD2EFA783@mnot.net> <44dafe6e-3049-287d-34c8-994bdf27c02c@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <89290.1479926344.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 Nov 2016 18:39:04 +0000
Message-ID: <89291.1479926344@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-6.8
X-W3C-Hub-Spam-Report: AWL=0.012, BAYES_00=-1.9, RP_MATCHES_RCVD=-2.897, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c9cSC-0002V8-DY b56bd0759402c6feff5ba01ff6da816d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: JFV and Common Structure specifications
Archived-At: <http://www.w3.org/mid/89291.1479926344@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32974
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>

--------
In message <44dafe6e-3049-287d-34c8-994bdf27c02c@gmx.de>, Julian Reschke writes:

>That said, we need to keep in mind that at least one of the arguments 
>brought up against JSON applies to this proposal as well -- if we 
>consider the underlying data model to be a dictionary, we'll have to 
>figure out what to do when that parameter occurs multiple times.

Yes, we do, but only for each individual header which uses CS.

In difference from JSON, there is nothing in CS which cares either way.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

v2.23.0 | Report a Bug | By Email