IETF Logo Mail Archive

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

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 03 April 2020 05:36 UTC

Return-Path: <jmh@joelhalpern.com>
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 5D03D3A0FC9 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 22:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=joelhalpern.com
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 G00tSKXXoM24 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 22:36:48 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46C993A0FC7 for <rfced-future@iab.org>; Thu, 2 Apr 2020 22:36:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 48tpb40h9Yz1p0VF; Thu, 2 Apr 2020 22:36:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1585892208; bh=ZDsl5QdsivWUVlPq0fH8ZbLfWH6NIyzFLIyGdG9xd74=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=bqPqcfZ6dGNByaDdjYXtmJg9O2Lcls2yFiSkuo3Ps8QrBrATv/ul0OSXY9rL/Ol9f SyxRR5ZI8QNxSVeOPW97r+FAAJ64HicK5+74m34ih5N5nn+99iE8wOMhaXPQAGbOvI Q9XncLuuvJr7I9PXuI/KC1cySZq6h/Y5dC2J7OSg=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 48tpb30mp9z1nxr5; Thu, 2 Apr 2020 22:36:47 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>
Cc: rfced-future@iab.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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <85cc8179-52ce-49f3-4412-c9403d3aec31@joelhalpern.com>
Date: Fri, 03 Apr 2020 01:36:44 -0400
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: <1533669f-6891-e50a-be08-b5293fc5cbbf@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HeIO2broLBEA8uLJ2duSqfqcBao>
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 05:36:49 -0000

Julian, on what basis do you assert that the HTML is all that matters. 
As far as I know, the agreements we have in place make the HTML one of 
the output formats, no more and no less privileged. You may want a 
different answer, but until we have rough consensus on such a different 
answer, asserting one does not make it so.

Yours,
Joel

On 4/3/2020 12:46 AM, Julian Reschke 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.
> 
>> ...
> 
> Best regards, Julian
>

v2.23.0 | Report a Bug | By Email