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

Carsten Bormann <cabo@tzi.org> Fri, 06 September 2019 16:50 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 834E712080B for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Sep 2019 09:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level:
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_QP_LONG_LINE=0.001, 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 KkSoziwVsKe6 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Sep 2019 09:50:05 -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 41466120127 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 6 Sep 2019 09:50:05 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B5349B80C85; Fri, 6 Sep 2019 09:49:41 -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 929B3B80C85; Fri, 6 Sep 2019 09:49:40 -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 11wKv3Sv6lsx; Fri, 6 Sep 2019 09:49:38 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by rfc-editor.org (Postfix) with ESMTPS id 4EBECB80C83; Fri, 6 Sep 2019 09:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x86Gnl6x000713; Fri, 6 Sep 2019 18:49:52 +0200 (CEST)
Received: from [192.168.2.41] (unknown [213.91.211.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 46Q3SW0VQ8z1Bp8; Fri, 6 Sep 2019 18:49:47 +0200 (CEST)
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <04d701d564cf$d2b0aee0$78120ca0$@augustcellars.com>
Date: Fri, 6 Sep 2019 19:49:44 +0300
Message-Id: <A8502726-1459-488A-8116-A21E579EE189@tzi.org>
References: <20190906042325.GC12952@rfc-editor.org> <04c001d56478$21b94220$652bc660$@augustcellars.com> <5c9530d8-909b-7004-7e2e-e598efdceccd@gmx.de> <04d701d564cf$d2b0aee0$78120ca0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
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: Julian Reschke <julian.reschke@gmx.de>, 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: multipart/mixed; boundary="===============2579505895014300927=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

The (admittedly clumsy) way kdrfc handles nested lists triggers a problem in xml2rfc's text formatter. I'll change that code eventually (reduce clumsiness), but the XML should work as it is.  (Draft-ietf-cbor-sequence, section 6.4 iirc.)

Sent from mobile, sorry for terse

> On 6. Sep 2019, at 19:26, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> This is a Carsten draft - so yes he is aware of it.
> 
> -----Original Message-----
> From: Julian Reschke <julian.reschke@gmx.de> 
> Sent: Thursday, September 5, 2019 11:11 PM
> To: Jim Schaad <ietf@augustcellars.com>om>; 'RFC Editor' <rfc-editor@rfc-editor.org>rg>; 'RFC Interest' <rfc-interest@rfc-editor.org>
> Cc: 'RFC ISE (Adrian Farrel)' <rfc-ise@rfc-editor.org>
> Subject: Re: [rfc-i] The upcoming transition to xml2rfc v3
> 
>> On 06.09.2019 07:58, 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.
>> 
>> Jim
> 
> Would be good to have more details. Is this a kramdown2629 issue? Is Carsten aware?
> 
> Best regards, Julian
> 
> _______________________________________________
> 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