IETF Logo Mail Archive

Re: [Anima] looking for practical advice on managing YANG source in XML format RFCs

Carsten Bormann <cabo@tzi.org> Mon, 14 June 2021 15:02 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 618433A27C2; Mon, 14 Jun 2021 08:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_FAIL=0.001, SPF_HELO_NONE=0.001] autolearn=no 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 GWUqQPDZ2fUO; Mon, 14 Jun 2021 08:02:35 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 883303A27AC; Mon, 14 Jun 2021 08:02:20 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4G3ZRr6BYJz2xGR; Mon, 14 Jun 2021 17:02:16 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <16776.1623679777@localhost>
Date: Mon, 14 Jun 2021 17:02:16 +0200
Cc: anima@ietf.org, tools-discuss@ietf.org, netmod@ietf.org
X-Mao-Original-Outgoing-Id: 645375736.406337-96927f24cec31a4d1e4e51c805b6ccc7
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CA387C6-6058-46DC-882B-BCBEB848FE7B@tzi.org>
References: <6795.1623632992@localhost> <D907A27E-2A70-4292-ADFA-5D8B350E676C@tzi.org> <16776.1623679777@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yWqOkg-2-rbAfMTp9J1MzUAzc7w>
Subject: Re: [Anima] looking for practical advice on managing YANG source in XML format RFCs
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 15:02:43 -0000

> One possibility is that kramdown-rfc ought to look for, and include the
> latest foo-YYYY-MM-DD.yang file, when told to ::include foo.yang.
> Alternatively, it could perhaps do the YYYY-MM-DD substitution itself.

How about

{::include foo-????-??-??.yang}

and, if there is no such file, kramdown-rfc expands the wild card in the directory and uses the numerically latest file?

(There might also be a use-case for actually including all these files, so I’m still in thinking mode, but I think this is close.)

> for when not working with kramdown.

What? :-)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email