IETF Logo Mail Archive

Re: [Rfced-future] Welcome to the RFC Editor Future Development Program

Julian Reschke <julian.reschke@gmx.de> Fri, 03 April 2020 07:00 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E143A1115 for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 00:00:15 -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, 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 VXNO3-xQyaG5 for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 00:00:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 D08593A09DE for <rfced-future@iab.org>; Fri, 3 Apr 2020 00:00:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1585897193; bh=vdZ9Sz04AuDLsS9bjyycrvJ1EnxmspN+IQkLa/76TAs=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=JORXHY+/rKLbXjO7xQtJbGrD8rABHzG1kOnMot5oMr+V6U0+qp5SjERVNjALWatMG 1jGnetFnES2ZV45KF0yx2gLWu2BqGO8gGD+nu3ET/bQyQLtsAbE2nulWmZVn/v3OzH mmigdD4pPdRYaBYHsTaOag18t8kUyogz/EoRVOwM=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.49.230]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MybGh-1j8CZQ1T5x-00yzSX; Fri, 03 Apr 2020 08:59:53 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: "John R. Levine" <johnl@iecc.com>, "Andrew G. Malis" <agmalis@gmail.com>, rfced-future@iab.org, Larry Masinter <LMM@acm.org>
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com> <009601d60964$2648e7a0$72dab6e0$@acm.org> <alpine.OSX.2.22.407.2004022303110.37555@ary.qy> <1533669f-6891-e50a-be08-b5293fc5cbbf@gmx.de> <DF6A09DD-C7D4-4542-B83F-C687861F5492@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <3b1df23c-d1e4-46f9-d7d4-6fac978be8d3@gmx.de>
Date: Fri, 03 Apr 2020 08:59:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <DF6A09DD-C7D4-4542-B83F-C687861F5492@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:j5jr+Ay6STQ8YjxuxzRcn7p4zLydrJghWgwPrAJTA2dmZFwTyJx FSmn53OR9CkSxLjo2s50wavcRF/YTpSLN7Vp8uUEnO1iGE3R8sD0EHLPOA2vUn0+Vdj0eL1 EZzJ6NfjLxpZnbTx17nNXcXJycV5gVPEkekm+9mNvrPiRV1tnmbvQzz5zyJo4HNpegH5jBz 0hsnz1VJf87zqPdhnTz2A==
X-UI-Out-Filterresults: notjunk:1;V03:K0:mrMlTPpp8s4=:LO9n2C7Cd1B4VSVAIJi2aK Rv6cSu8V9XiuBAnTcDfD9M3PphzY0ko6oxMaAu8UvWEMlZ4uqLGwsm0R6Z1p552r6cEd8TWhR gB6m/T9xtIqihc/xRvg3o7t5w5lKgvqhYY2ziRBpJgHFVzUi1wTr7vhxOsBXQwCr9eD6cHmXX W3ZerC777EGUwDd3rk5OAjZYhdttaVZTQeqoHsnlY8De77RTPLjckTo0rIaDc1A8U7zLEpDPG t34yQL/0pwqmHVcV5Hghpgvv1JrYjx3MQkysHTO/xKAfxlzugpb2tZJrNjvan14/HC2RBdNdK B+Yhh2dvRgriudJjVqXVlFu2MgwX94OdtYwrepPLueLOJ/+Xuj4zc6K3kS4KxK8mVQk0hCc5X VPOJvF8l15lSjW59+LI4IFe35QvmJR1ML6ESEAm3o+lbr6Fn0X49fN7JbaTca8ZgC9cxHyQc4 CdKTQ31Rm3/g4Cs8P3yAnzqF0ev5sTarCYGxU6Kdadeir4UkEyQqEOZAE9fcGiuT+iCPo3TYb QWzCpWgq1BaEX0/3ztauobo1mwnzGMuNysx/y3k7zW2NjUwXM/klP9XD6aiTlhnP10VM0wxAZ UV6TfEW1stzb/x6DvxWHXQuOGtAGootvu4O9RQiMmpfQ64CtPB4COEEXA1mDJhXHy64FPs+bJ KYKQP+P94UGjKgEsjh1Kw7lBWc2TqsSwJGJR+dIqOuwwAFQNNHLCIYqZbI23xn0EEF5LMhFmU pcl4LXSeYOxeuSxP0Eia0C/BiiqCdX5IQpzZ2R7Fq9qzrEJzztH710bzPoqEoEHV8Cb24Nv4Q +rvp5L88EoL+I0zsSIIlCTUeIi3zcLBSxSdyd64xFFo4Y4TsAEOCUTnYnfyw2/XtNycfTFbRr HHF6igRK+j4gXFQiv2iynd5zmVNu83IERrOxMuNBQ2upMdV1sQXFIjasfIBlf74rNcQGrW5uL 5zBTBx5ASq/fy1re3a0iSZsfw5bmDZWUzVGtnck+DonqsvhmWfeHiQI916tEgQsd7gf7I2umg oMTSjSs/+7Q2P7YjmdjOlrD+xIExJvWcRoJInMLE1XfXBPiAAdDEqz2UKXktzbSJvKcAnzdiy jOzaHtiz8gj3/zGQfru9YrYhnwQ54xz4VWWu7Vb3R0wm5zEuzZXFP1yzbV2wsj6rDyPFFrrtK A3h5rq5bNuIzGbQkcyl03xWJnJdTE1zioAAMDb31yr7iKc2KPOMNfTvWmNo4h74Spa8AECpN8 AaBHY/HJSVm+3qFe+
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/-zki44YrmW8fN0E27unrQCFyYEY>
Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 07:00:16 -0000

On 03.04.2020 07:25, Carsten Bormann wrote:
> On 2020-04-03, at 06:46, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> On 03.04.2020 05:07, John R. Levine wrote:
>>>> During the AUTH48 period, whoever is reviewing the document needs to
>>>> check ALL of the formats, especially around examples and figures and
>>>> any non-ascii text.
>>>
>>> Currently the RPC people are proofreading all of the output formats,
>>> which takes a lot of work.  I hope authors are also, but that's up to them.
>>> ...
>>
>> That sounds like a bug in the process to me. And it won't scale if we
>> add ePub.
>>
>> There should be *one* format that is to be proofread, HTML. If the other
>> output formats have an issue, that's a tooling problem that needs to be
>> solved, and the other formats can be regenerated.
>
> This doesn’t work too well in an environment where the tooling is fluid, and in fact the format that the tooling works from and its interpretation is fluid as well.

If the tooling is that fluid (is it for HTML?), that shows that we
shouldn't have started the switch yet...

> When the tooling has a bug (read: it uses the interpretation of 2020-04-02), and the XML is adapted to work around this bug, and the tooling is then fixed (read: it now uses the interpretation of 2020-04-03), the new output may be erroneous.

The (canonical, published) XML never ever should be adjusted to work
around a bug. Is this happening?

> ...

Best regards, Julian

v2.23.0 | Report a Bug | By Email