Re: [rfc-i] The upcoming transition to xml2rfc v3

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 10 September 2019 15:19 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 331CD1201AA for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 08:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.199
X-Spam-Level:
X-Spam-Status: No, score=-5.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 6Kxw6o-XYN2s for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 10 Sep 2019 08:19:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA0B12012D for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 10 Sep 2019 08:19:14 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 006C5B827D7; Tue, 10 Sep 2019 08:19:12 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id A49C9B827D7 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 08:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ykQ-SNrRVdaa for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 08:19:09 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) by rfc-editor.org (Postfix) with ESMTPS id 39320B827D1 for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 08:19:07 -0700 (PDT)
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x8AFJ6SH002309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <rfc-interest@rfc-editor.org>; Tue, 10 Sep 2019 11:19:08 -0400
To: rfc-interest@rfc-editor.org
References: <20190906042325.GC12952@rfc-editor.org> <04c001d56478$21b94220$652bc660$@augustcellars.com> <20190909203533.GA7678@rfc-editor.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <b20a405c-7e08-cb5c-9c9c-88a6e5715969@alum.mit.edu>
Date: Tue, 10 Sep 2019 11:19:06 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20190909203533.GA7678@rfc-editor.org>
Content-Language: en-US
Subject: Re: [rfc-i] The upcoming transition to xml2rfc v3
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

On 9/9/19 4:35 PM, RFC Editor wrote:
> Hi Jim,
> 
> On Thu, Sep 05, 2019 at 10:58:37PM -0700, Jim Schaad wrote:
>> Will the RFC Editor potentially be editing output to make the v3
>> vocabulary look cleaner?  I know of a kramdown file that is having
>> some formatting problems, at least in part due to how it is creating
>> the xml file.
> 
> We will do some cleanup of the v3 file, but we are hoping to keep the
> cleanup minimial.

How about some automated cleanup, such as XML pretty printing?

Or perhaps there could simply be some tools available on the tools site 
that authors can use for such cleanup.

	Thanks,
	Paul
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest