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:35 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 DDE2312023E for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:35:03 -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 IKhK2v0bGzdQ for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 08:35:01 -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 275A51201C5 for <ietf@ietf.org>; Thu, 11 Jul 2019 08:35:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1562859285; bh=42O2AgSfv3dBH1GOHUoEYjw3nMSP7xwAo5HR0l+h6Jc=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=TMPPK4YMz5dlK2rSX3R6B6l94pw8fuPga2ER3rWi2tfiDOFAghz7GwuceeHqjMys1 r/0FTrq5A/h3+1wjFqH5qqw8+FIlNALrhLkynJI7NdeEK0dhiahQ7Vurci8JTLxUNv a4+8YPIwIKKYH8r/w3pSIewlN04gc5rBhh0A1qQ0=
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 0Lfjxq-1iICtT2GdO-00pK8q; Thu, 11 Jul 2019 17:34:45 +0200
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
To: Carsten Bormann <cabo@tzi.org>, Ted Lemon <mellon@fugue.com>
Cc: 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> <34FAABF1-68CC-4433-B39D-6DA261ECFE66@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bc7fce1a-4a51-4e18-6f94-3fd1eac0c997@gmx.de>
Date: Thu, 11 Jul 2019 17:34:42 +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: <34FAABF1-68CC-4433-B39D-6DA261ECFE66@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:VDZM97gGTYmbJxHYgcUJjjINwWz98+LLEbMit1h1jL2cKJSZG8B EfPcT/QnKHq4nkNnLIxyqSdJ4/S3Iftpv3SiB1N7WYwxPfBUo0h/YGFmAAI+/ddMTq3gBfz P+vNc5c+SApgv9g+bbjvctjuWEKZC/npgC9be5RGw8192TP+JFdd2OHBkCzteOJ5nB4QrEl OJd05Llan0gIE5u5mlx3w==
X-UI-Out-Filterresults: notjunk:1;V03:K0:cczfuiYWS7g=:KGqGpCNiRQSirjiIMlE1U5 ct+qCVNcZjsk9AIMBOW6IrhkRDqP+0A9SnR2/uQlSOluAJghGKbhSn6dkv99sssUCqp/bnv1G BCNtxgnZ7YPna4KPb+5sP3Z98d76aGzUNWhS6yYsoNzV3fAxOqgORa8zvhCRyoXkpAyh3Nc9S D1uNX2FOrViUcEhF/yLoJRikazewO5e+j+owJ33XRk8TmhKsWwQRLBL42aWzFY7Jh5iYunt/j J93jCBpt2y6RR+fEUFu9UxIlNoU7g0rCxS/3FpW8n9gr30CqT0nbLhqh4E0Axp+cmzGrrVJZp ns1HbOKf1J3Ibwdgd6hjKO1rxn9gnbsROXiAkUaXUZvm55ycsCiI/x5jca7zvC2jA44oavAzS PSkAy+G+1a+UDaQ/uk7g41heoHQfi8n3HZy4x+Q/jU+e8xRjM0ovBQoVeliQXKkNR9fVfzfyG X+UO6JtAtGzPltYGCEr77fj+qUE1mRg+2QLMUKhFpze7VBhjJGy7GgUAJ4kwIKjVRg6QIHbF2 ieh0hNROG7tNGzK4He2iEF82C27qWhUXV8AB27gQa4c5+zYfkJ1OtmwvTwcePY1c41fIV/7cX XxfSd9KopkFvmgw/BTzh+vD9v+lYBCcLrXWop4SHn1XtlgBDlK+XleOS0G/SzsvfZWPiG+jLi XudluNaF83LQpeUV7gOEypQ4qVCjf94uspEQaAvLpn3oFmu7+z6ZpUgFEwljL1okuaB+VgFIe E6T5+5grdz8y3Mv18X9RHAqrGeEjdKEjKcLRVLqimC+9Fg+KNVh+6xCnojQPK4OM+HIcJfZ6I SmN4Dy1kNHc1p/4MnD17pSG61BWcYInBt4rAo0sNgsAQT1cyuMCHlaLONxpJBL0fI4QsohlqL hkL3QVnSnoJdfrkSCFgGOAkSqSf/3Pj6Qx3ZCSbQHoxibojU83ujNcHckBuxy62dOYSyChAG7 qJh+aK+6zz+5BGhe4HhL27AHNFfgnz3/J30jRWcqaAuH2+fuy+16MbC1b7ePiopgIoRG6e7It YvnFyhNsyRkMRNJQmvnhWd6/Pzk15ci7BowmocO5xd153qMbi4arRwXlVq6l2yoxBajglwUT0 tW+iPse1KrTVDppENE+O9vXcJ5WL6TEULVQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0Bs8UoYdOvePo1_xzRz1h7IJ4Uw>
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:35:04 -0000

On 11.07.2019 17:27, Carsten Bormann wrote:
>
>> 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.

Yes.

"When one or more of "year", "month", or "day" are left out, the
processor will attempt to use the current system date if the attributes
that are present are consistent with that date." --
<https://greenbytes.de/tech/webdav/rfc7749.html#rfc.section.2.13.p.3>

And in V3 it is actually optional, see
<https://greenbytes.de/tech/webdav/rfc7991.html#element.front>.

>> 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). (...)

+1000

FWIW:

"Furthermore, it is good practice to disambiguate current editor copies
from submitted drafts (for instance, by replacing the draft number with
the string "latest")." --
<https://greenbytes.de/tech/webdav/rfc7749.html#rfc.section.2.33.3.p.4>

It's very annoying that xml2rfc complains about something the spec calls
"good practice".

 > ..

Best regards, Julian