IETF Logo Mail Archive

Re: [xml2rfc-dev] Transition to V3, was: Please help review v3 files

Heather Flanagan <rse@rfc-editor.org> Wed, 21 August 2019 17:32 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAC9120D6F for <xml2rfc-dev@ietfa.amsl.com>; Wed, 21 Aug 2019 10:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 25IpA79YX_eR for <xml2rfc-dev@ietfa.amsl.com>; Wed, 21 Aug 2019 10:32:20 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE5BB120D6B for <xml2rfc-dev@ietf.org>; Wed, 21 Aug 2019 10:32:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6DD131C043F; Wed, 21 Aug 2019 10:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9cQd9Mef7HWI; Wed, 21 Aug 2019 10:32:08 -0700 (PDT)
Received: from [10.198.42.38] (c-71-231-216-10.hsd1.wa.comcast.net [71.231.216.10]) by c8a.amsl.com (Postfix) with ESMTPSA id 121F81C00CA; Wed, 21 Aug 2019 10:32:08 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <9c2b7979-d4ce-56bf-b5d8-e39095b7f042@gmx.de>
Date: Wed, 21 Aug 2019 10:32:19 -0700
Cc: IAB <iab@iab.org>, "rsoc@iab.org" <rsoc@iab.org>, Pete Resnick <resnick@episteme.net>, Sandy Ginoza <sginoza@amsl.com>, Alice Russo <arusso@amsl.com>, XML Developer List <xml2rfc-dev@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <02228276-EE5A-4BA4-AF53-037C1C6B47BE@rfc-editor.org>
References: <62908E23-2FC0-4ED7-84B2-E86454020206@amsl.com> <1f59bf66-f2e3-8ae2-823c-1e5002676f2f@gmx.de> <feb615d0-9820-8455-7c5a-3d5511b6d1f7@gmx.de> <c1074101-8d87-97a0-f9dc-da48bb2f23d2@gmx.de> <8111537C-642E-4396-8EE5-BDD1049FF957@rfc-editor.org> <7ef6463a-d695-bf3b-386d-6936c01eff26@gmx.de> <671F7DEA-3DD8-479F-A6BB-9C5CCD735DFB@rfc-editor.org> <9c2b7979-d4ce-56bf-b5d8-e39095b7f042@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/8TAsVnjF_Yz9SqANHVjbEd2dwpU>
Subject: Re: [xml2rfc-dev] Transition to V3, was: Please help review v3 files
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 17:32:22 -0000


> On Aug 21, 2019, at 9:47 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 21.08.2019 18:06, Heather Flanagan wrote:
>> ...
>> I’m working on the bis doc now.
>> ...
> 
> Please note that RFC 7749 and 7991 use a slightly complicated make
> process, where parts of the text is generated from the grammar. It would
> be good to keep that for consistency.

Instructions on how to do this would be appreciated, else I’ll do this by hand.

> 
> Let me know if you run into problems, and I can fix these for you.

First I have to figure out how to put together the necessary environment. If this is how this kind of thing should be maintained going forward, we should get it documented somewhere.

> 
> (See first PR at
> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/pull/85>)

I don’t understand how to read that as applying to how to compile the draft?

-Heather

v2.23.0 | Report a Bug | By Email