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

RFC Editor <rfc-editor@rfc-editor.org> Mon, 09 September 2019 20:35 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 1CFD11200C7 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 9 Sep 2019 13:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 iHpUXZmKBHBV for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 9 Sep 2019 13:35:36 -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 39BD3120048 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Mon, 9 Sep 2019 13:35:36 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BAD20B808B6; Mon, 9 Sep 2019 13:35:34 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 6000) id 46C59B8089C; Mon, 9 Sep 2019 13:35:33 -0700 (PDT)
Date: Mon, 9 Sep 2019 13:35:33 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: Jim Schaad <ietf@augustcellars.com>
Message-ID: <20190909203533.GA7678@rfc-editor.org>
References: <20190906042325.GC12952@rfc-editor.org> <04c001d56478$21b94220$652bc660$@augustcellars.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <04c001d56478$21b94220$652bc660$@augustcellars.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
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>
Cc: 'RFC Interest' <rfc-interest@rfc-editor.org>, "'RFC ISE \(Adrian Farrel\)'" <rfc-ise@rfc-editor.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

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.  

Thanks,
RFC Editor/sg


> 
> Jim
> 
> 
> -----Original Message-----
> From: rfc-interest <rfc-interest-bounces@rfc-editor.org> On Behalf Of RFC Editor
> Sent: Thursday, September 5, 2019 9:23 PM
> To: RFC Interest <rfc-interest@rfc-editor.org>rg>; ietf@ietf.org
> Cc: irsg@irtf.org; rsoc@iab.org; IESG <iesg@ietf.org>rg>; RFC ISE (Adrian Farrel) <rfc-ise@rfc-editor.org>rg>; iab@iab.org; RFC Editor <rfc-editor@rfc-editor.org>
> Subject: [rfc-i] The upcoming transition to xml2rfc v3
> 
> Greetings,
> 
> With the RFC format transition approaching quickly, we want to share some of the transition details.  
> 
> The RFC Editor will be switching to using xml2rfc v3 [0] [1] [2] to create RFCs. (Authors do not have to change what they submit as an
> Internet-Draft.)
> 
> There will be new publication formats (HTML, PDF, and text) and an XML source file, which uses the v3 vocabulary as described in [3] and [4]. 
> 
> Next week the RFC Editor's code base and database will be updated.
> >From 16 September 2019, the RFC Editor will be ready to publish in the new format.  See the transition details [6] for more information.  
> 
> For more details on why this change is taking place, see the "RFC Format Framework” [5]. 
> 
> * How does this affect you?  
> Please see the transition details page [6], especially if you currently have a document in the RFC Editor queue [7].
> 
> * What if you find a bug in xml2rfc? 
> Please add a ticket to the issue tracker [8] or send mail to the xml2rfc-dev list [9].
> 
> [0] Tool: https://pypi.org/project/xml2rfc/ [1] Intro: https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html
> [2] FAQ: https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html
> [3] RFC 7991: https://www.rfc-editor.org/rfc/rfc7991
> [4] Implementation Notes: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-09
> [5] RFC 7990: https://www.rfc-editor.org/rfc/rfc7990.txt
> [6] Transition Details: https://www.rfc-editor.org/rse/wiki/doku.php?id=v3implementation
> [7] Current Queue: https://www.rfc-editor.org/current_queue.php
> [8] Issue Tracker: https://trac.tools.ietf.org/tools/xml2rfc/trac/
> [9] XML Development Mailing list: https://www.ietf.org/mailman/listinfo/xml2rfc-dev
> 
> Thank you.
> RFC Editor
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest