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

Julian Reschke <julian.reschke@gmx.de> Thu, 11 July 2019 15:58 UTC

Return-Path: <julian.reschke@gmx.de>
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 01084120399 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, 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=gmx.net
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 wcJRufVDYMNx for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:58:03 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 3D010120383 for <ietf@ietf.org>; Thu, 11 Jul 2019 08:57:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1562860647; bh=AyZ9xQXoiv9LdLW8VLSL3xX6seykopbpeAcq0TL/248=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=RJGQpCWdXI1qSU5Y+NRF5CxJ7r5dRI+iwU4phk9lBqFx+XxgLyaUnxS5ly3qme6Z5 a1wMCkHxY/qHLR+M2T8KD3GLQFWRo8Zcy2BHzsckTfno56WEo5i93+gpGXvunJiUg3 gq4V8ZM3fhFKOfRdxPcuwO7yxv9iQFII21E+J76w=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.156.30]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4WNA-1ihwEc3Z9w-00yhi1; Thu, 11 Jul 2019 17:57:26 +0200
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
To: Ted Lemon <mellon@fugue.com>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, Christian Huitema <huitema@huitema.net>, Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.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> <00b1edcc-719b-e095-7c90-057efe63ed63@gmx.de> <D01E5836-7BD2-4234-B14C-667D3739D037@fugue.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <3c98d675-d46c-c4c7-b331-35f22f097b5e@gmx.de>
Date: Thu, 11 Jul 2019 17:57:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <D01E5836-7BD2-4234-B14C-667D3739D037@fugue.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:4yelKQP/z9vBt8zj4x/oiyJlOz6X+DCk4j7wocaH/aTmiPf54AK GcwrdVGJCkRZ0OBolcl9EHHC6WsqRYj4n8fGXDveqAe1j6qxWeLiV2GJFcgZedfZnRSehQr lnSHu1el0HRn204MfohGsLglJpJH8IYwtofkECGutdK8cdFUcS6wI1Fxt6EJg8/NSpnd/rf Ha1L+EiRBVPp6Hn18UcFQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:m0eMQy8Ta/U=:OXErgp5LVF8mRuy9C0XaFu eNf+ZQAp++JkkVnoud8RMZwiApxnOAuNqDDAR4NCkMcfd8XCT+uCdEHaZXQ4JoNd9jZBKr6pp tgVebVCYWz8l7OLKaQusbBQX0+I92AwJp6S4SXBrsS8P4PAM+5vlT9q1lSo1vVIknp6m6PVdi 10lwn0WQVn4SK7BI6TPV6/fhxTel+HAFsqrdS/ORhyF7ZEpDy8Di1OhRZFRVHR0Id9M7r5EL3 5My3OwXP7Bu5ZIyDW0tBbFiJqkLRQFuA2/i1ZXNI19fNyKXYBWMMR2gTgpvK8uk9Y1N1AnZ0R jilG0Buad3ilOtgg5Cmclqf5atKQjgYfYod0bfPnLVsQ2ArrzPJHfV5l1638c/5dDBD20l1A3 UiuVGn2mOxjs215MkcEjVZ9Lou+SLwUBFTQqv0BnLu1i6GDeNVisPdwDJqs+DDgWfJtPnlWKy Ej9rrSQ4sRVdcaowmTLSgAnuHz6TeXx1+oaexVUmi96pu2i6QjPwBWqm85TdOSQ/aRWBkbzRE yPvt/7Nk89ao5cc2gcJIye7h/6qx7oeE9n2NKztxbzShHMh/8RpiN0YvV58+qYeZFMO94P/Tb XYXCuVcdB35/6+81xzF+P1ub/ZEsqIOQkBwYffe8RQnZjSrHk0CmzTroBwbcp6MjETZ0kTZJR hLNLhAuhg+3RGJ99kj44Nk3gy6j4PZXCguA1yptU7O6nz6OVVo3zDuN9Is76XsQ/JnHHodYb5 OQ4aKaoN/c3p86Mqz3JPGwj9AJODNwXF7kD2I0KhGeMAZR1bSl3NE/J95mjrsyqFqxygXhsn/ SzL3nFylo91sCK++E9M+31n8N+DEMdmm2nAIfXcFm0wO+1r6tZSCNbVtFVZGfIHwPNrVSl1Mm 2eZOqZ8ep3Bfpe/J1Se1Cm6fHIEZceP9noa5pftyB5SSlJ2NBNYCvS/ODPktmy2T62hMx7Mw6 1qUZUK3Q/Vdoc+zLjjJpDj5zJ2H1G7c15QHzlSNFOKGZK8nQdZ9z4K8AQTPk0E9qEK9hDB7fH UXy4VLFad+TGD2T9FgcnqzDWAnTklk+o3JQnR7K5H95oxW0XVX3OE5/1tPkUEXx3g43llehhi EGPB/KOYKnTsE+NVyWJ8F62MJoxTXQqklGP
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_yN4-88omdflppNksSyH8AkBB-E>
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:58:06 -0000

On 11.07.2019 17:30, Ted Lemon wrote:
> On Jul 11, 2019, at 11:20 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> If one says "normative", it's normative, no?
>
> In terms of process, yes.   But I might refer to it informatively and normatively in the same document, and that could be marked properly in the XML if we cared.   I don’t think it’s very important, but if you add the ability to mark a reference normative, you either have to allow this or forbid it, and if you allow it, I think this is the right way to treat it.   I’d prefer to allow it—I think it’s useful.  The downside is that it requires more care, and that would be a good reason to forbid it. :)
>
>>> It would also be nice if the publication date could default to “today”
>>> and if the draft number could be determined automatically based on what
>>> is most recent…
>>
>> It already does default to "today", unless I'm missing something.
>
> Oh cool.   Either I didn’t think to just leave the date tag empty, as Carsten suggests, or this was added at some point after I started using xml2rfc.   Of course, if the XML is normative, isn’t it the case that the published XML has to have a date tag that contains the publication date?

In RFCs, yes. Elsewhere? Would need to be decided.

>> Calculating the draft number *could* be done at submission time; I
>> wouldn't want to do it always, because then, if the last was "01", the
>> generated one will say "02" - even if it never gets submitted.
>
> Sure, but that’s effectively what happens anyway, isn’t it?   The difference is that I might generate several -01s after -01 is published, or I might generate several -02s before -02 is published, depending on my habit.   This would eliminate that variability.   It’s always possible to generate a -02 that’s not the published -02, so I think making this automatic doesn’ t make the situation any worse, and does increase usability.

I do not disagree; it's just a question when this should happen.

Best regards, Julian