IETF Logo Mail Archive

Re: [Json] Consensus call: document title

Barry Leiba <barryleiba@computer.org> Fri, 21 June 2013 19:19 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 BF7AC21F9FDA for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 12:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.02
X-Spam-Level:
X-Spam-Status: No, score=-102.02 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 2TcPDpCYibn8 for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 12:19:46 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 41E7221F9FA4 for <json@ietf.org>; Fri, 21 Jun 2013 12:19:46 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id p13so6234607vbe.14 for <json@ietf.org>; Fri, 21 Jun 2013 12:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Hl9adQ5218wUNya/jIN5zohc9GuWFlQC+eYEheOQ3pA=; b=fJmxTNy493EXuXoJ/naITSyyhM60xHimXFMCrwmvodjktmgho5mlvnOUsPXix13acl P8RTFIiG+6raHi9kTaUlpnMOAP/rr0DyEBeOa1NeJ5i1HlCl6yGpcPaF4D9J/SZ+kBUT NPEMRB2c3O9ojNy3m5/ZDQSanBlyNzSXRHRchA3sMl4AyNAm36653pUWQnCXeTC1wQRX AR2ddgPUZODuH8nPWWj9XjoZNkJ4AuU9klNqsK3vBkbX5rUrxRR40DsLMfgV3E1QAWS6 U2daXn9ecD34UpoJ4o2yKMW2HVdBgYPBn2wEaY/2QzgnXKBM2uQccAnyjCsi/r5l1p9y P5MQ==
MIME-Version: 1.0
X-Received: by 10.58.34.69 with SMTP id x5mr6559328vei.11.1371842385490; Fri, 21 Jun 2013 12:19:45 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.234.105 with HTTP; Fri, 21 Jun 2013 12:19:45 -0700 (PDT)
In-Reply-To: <833372357.126503.1371839504953.open-xchange@email.1and1.com>
References: <mailman.2511.1371834130.18953.json@ietf.org> <833372357.126503.1371839504953.open-xchange@email.1and1.com>
Date: Fri, 21 Jun 2013 15:19:45 -0400
X-Google-Sender-Auth: Vt0PU-67BzouH_YQ9BbK5QmNRcc
Message-ID: <CAC4RtVAu+dixWvJN4JOSFXkauCM9Qi=MuAJKxC9W41OMdgEkqg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "douglas@crockford.com" <douglas@crockford.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: json@ietf.org
Subject: Re: [Json] Consensus call: document title
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: Fri, 21 Jun 2013 19:19:46 -0000

> I think this call is premature. We first need to determine which document we are
> producing. That will determine the title. If we are making The JSON Data
> Interchange Format document, then it should obviously have that title. But if we
> are changing the status of the RFC, then it should retain its current title.

Procedural point:

This is certainly a valid opinion (that we shouldn't change the title
as we replace the document), but there's no *procedural* reason that
the title can't or shouldn't be changed in the process of changing the
status, as long as we're making changes and issuing a new RFC.

The only time the title *couldn't* be changed would be if we were
actually changing *only* the status metadata, and not publishing a new
RFC.

Barry

v2.23.0 | Report a Bug | By Email