IETF Logo Mail Archive

Re: [Json] JSL: Clarifying purpose, and renaming it to JDDF

Ulysse Carion <ulysse@segment.com> Sun, 01 September 2019 23:03 UTC

Return-Path: <ulysse@segment.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 0664A1200C5 for <json@ietfa.amsl.com>; Sun, 1 Sep 2019 16:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=segment.com
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 m4Lkv2cO1CvE for <json@ietfa.amsl.com>; Sun, 1 Sep 2019 16:03:43 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2502120074 for <json@ietf.org>; Sun, 1 Sep 2019 16:03:42 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id b136so1517655iof.3 for <json@ietf.org>; Sun, 01 Sep 2019 16:03:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=segment.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N3KIwb++/xHyYCdwdiMHRHT+XRbKiWy3Kb0azerPD0o=; b=fYLk5hWnqvJNB2ADlVQbbiZJeEaXuQf3t+T1Ti8sEK5BwvLzOIexZSW0SrjGYMjQok 5Cp6Jxg3ftOHZnL6wfUNpPDOtvXvcIS3Kcc4LJAcH3ciIism5Yo3UshQjaelr++ij5id OSeV3IdgRbhzLpxn1N4hCISqmbCDhmG2jLQek=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N3KIwb++/xHyYCdwdiMHRHT+XRbKiWy3Kb0azerPD0o=; b=VHvCWTCdeGvSsQDcwZdzuOBQRjJwfu697Doyb8ODxgVLjIW7NFujUYZt85zyAHdDOD kALsgXCL0H3J9mv5cEwlB+jGRWwi1fAfVcPdNSCmPLlcJM56+3PNf9pnoVEQX895CetU I4AwTBi0B5ESmAZzZq4pK3Zch5x2FgfOhEN3JcpwFAUh6cgcpkdxjh3yMOSIoXzaMMpM 6szDQeKTYcpUZojgEdzu1SqyYXpt3Iuplluj6499c8Y7BjmPRn9PoEL7QIyHFZo9dQvj KWD6JCsCtmcneHZVvXhMXLZFMxktSKU5h7YzSuPUHVkkX5Q35haqYbrCpq3+Sd6x7EDp Ao1A==
X-Gm-Message-State: APjAAAUVE/AKLt7e1SfERXsGoXiOlN4yqKLRRi5N8QEExRV7jxZlxc0x NYb+9iYNaaJkJeyWPjfae8QKtW+8VeMeRdUp/64Uzw==
X-Google-Smtp-Source: APXvYqzxmAfK+NNebUw1otl7WOtZyLaBr3LgvffAEiyAxMcFqJgZCmmXFAhv9yHcvmfKw86DDiZmfoa5SO/Fl+nysCU=
X-Received: by 2002:a02:65cd:: with SMTP id u196mr1440254jab.3.1567379022049; Sun, 01 Sep 2019 16:03:42 -0700 (PDT)
MIME-Version: 1.0
References: <CAJK=1Rj6zW_MffKvsOiQh28KY5yDeoALGSYqve+vGj52s1Owag@mail.gmail.com> <CAD2gp_Qw2=J8vuimyVAta=cZEos9qmzLd-RsK3czkM5LvFSi7g@mail.gmail.com> <CAJK=1Rh927YqLgqhewT+EOEjtbpFsVvUnE=9cr+ng0+CY-7rSg@mail.gmail.com> <CAD2gp_SS3yvk4TMXAuuhKmjv1wucycOp9MKS+vKwn4tj1oqp0Q@mail.gmail.com>
In-Reply-To: <CAD2gp_SS3yvk4TMXAuuhKmjv1wucycOp9MKS+vKwn4tj1oqp0Q@mail.gmail.com>
From: Ulysse Carion <ulysse@segment.com>
Date: Sun, 01 Sep 2019 16:03:31 -0700
Message-ID: <CAJK=1Riir-7bGODo3rSnTZrh2tvxTR4Kbs56ic0sGfAwZHL7YQ@mail.gmail.com>
To: John Cowan <cowan@ccil.org>
Cc: JSON WG <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/lZ9akV_F_Fn6tLAlGPpwu7pW61M>
Subject: Re: [Json] JSL: Clarifying purpose, and renaming it to JDDF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Sep 2019 23:03:45 -0000

Sure -- but you could use the length validation as a hint to code
generators, and a warning to data producers that the application will,
post JDDF-level validation, do additional length checks.

I'm not sure the need for length validation is strong enough to merit
its inclusion in this version of the spec.

On Sun, Sep 1, 2019 at 3:42 PM John Cowan <cowan@ccil.org> wrote:
>
> Section 2.3 says that extensions can't be validation-related, so a length limitation would most certainly be a matter of validation.
>
> On Sun, Sep 1, 2019 at 6:28 PM Ulysse Carion <ulysse@segment.com> wrote:
>>
>> Fixed-length strings and arrays both sound like things one could
>> implement with extensions, no?
>>
>> Tuples are a very sensible suggestion. But I wonder if we can live
>> without them? I very much want to keep JDDF as small as possible.

v2.23.0 | Report a Bug | By Email