IETF Logo Mail Archive

Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)

Carsten Bormann <cabo@tzi.org> Thu, 11 July 2019 15:27 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40276120157 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 x8HhJGaNouHw for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:27:09 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A831A1200F9 for <ietf@ietf.org>; Thu, 11 Jul 2019 08:27:09 -0700 (PDT)
Received: from [192.168.217.110] (p5089AF0A.dip0.t-ipconnect.de [80.137.175.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 45l0KR43blzybC; Thu, 11 Jul 2019 17:27:07 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0477F142-49A3-4BB4-A763-0BC90A3BF3C7@fugue.com>
Date: Thu, 11 Jul 2019 17:27:07 +0200
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 584551625.1777329-737fe6cee0febc0803783d020ca877e5
Content-Transfer-Encoding: quoted-printable
Message-Id: <34FAABF1-68CC-4433-B39D-6DA261ECFE66@tzi.org>
References: <20190706185415.GB14026@mit.edu> <CABcZeBPgNr5UqQ0pLwwNu5wh0g9L9wCd6YyYKCUDO37SPru-_Q@mail.gmail.com> <20190708202612.GG60909@shrubbery.net> <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <20190710045202.GA3215@localhost> <20190710064451.GB3215@localhost> <06EF2608-038E-400F-86BA-34F57630B53F@fugue.com> <CAMm+LwjFgSK7DSaN2CpLxmL=PO22s2qjBvBHC48jH9UnFy8=wg@mail.gmail.com> <4d10d37c-f6cc-f818-6ecd-244f54e6512f@gmx.de> <0477F142-49A3-4BB4-A763-0BC90A3BF3C7@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9z6WNYDUBjJI5MoIz5tP-VL6rC0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2019 15:27:15 -0000

> On Jul 11, 2019, at 17:09, Ted Lemon <mellon@fugue.com> wrote:
> 
> It would also be nice if the publication date could default to “today”

    <date />

or in kramdown-rfc, just leave off the date: member, and kramdown-rfc will insert the date of conversion into the XML.

> and if the draft number could be determined automatically based on what is most recent…

I think, more generally, there should be some support for the -latest convention (e.g., in idnits, or in xml2rfc that is currently spewing a warning).  I think it is a good thing to have an explicit action for actually spending a number.
(But the number of times I got that specific number wrong, only to be reminded by idnits, is amazing.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email