Re: [xml2rfc-dev] Script to generate RFC reference including abstract?

"Andrew G. Malis" <agmalis@gmail.com> Mon, 25 January 2021 13:07 UTC

Return-Path: <agmalis@gmail.com>
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 DC0EA3A11B9; Mon, 25 Jan 2021 05:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ix9LMwJR5bqr; Mon, 25 Jan 2021 05:07:49 -0800 (PST)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B07863A11B8; Mon, 25 Jan 2021 05:07:49 -0800 (PST)
Received: by mail-qk1-x735.google.com with SMTP id a7so5448459qkb.13; Mon, 25 Jan 2021 05:07:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bubFJmkZDbtXQc4I4XT/XJH3nx5+6DJRYipLTGhz25I=; b=hGmSPYwEL3SyaMUaQV+5OzzGs6CDu20ypFGuC9mUczqf9qTT8WahZBEAUDl71K0g8a 7AWkiSyjhksrR+k9ehhMlTxaGN9D4ZESANApfuqNnoUr5+BbKkvE74sXHxH+ConkaT3g p+AUOl2xnhLsjfnuUZuTOEA0BWd6J7UJp2jXH57MCy9y4+HdSZxN73dhHGAJMYmfaftx aC+k8LunJB58t6xBDC9f7GAVIluPmUVDauDrOv7jXFph+B99fH2zJlLi+PeY/w+2X7nl MNXCA61BnsuIkOilNMVZZ0RAOHXiYfAKkOMOstRH6SNXSV+cF83M+IxnRZmVKGz7v1bZ w34w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bubFJmkZDbtXQc4I4XT/XJH3nx5+6DJRYipLTGhz25I=; b=lNDHryKkKXFz7cJRfr+1Yd/E5bi1b+A3r+p+nO6abWu2Te06kKpKyVW5pVXUvVErRd 5onQiHjRTmfLZwZ1FKDj0fIVFyimC4yNrPNCv2ZXJwKWI9oqrkNsOJDiWye67siuDAH3 3tLoK1741WS4KqLG+z77vXq/3ZTyekSGpok9rZ9CMf9SGywZF06R5rvDumrrR25bb/nZ dgv89yr9j2q4rVgcrBJouxQBSchjJ4hMLGgHonvU92VzQF2k/sLVZAAnvOcx48NjK+4b ZZgRbsxttt5K6PNb0NEdK0NOpadix/thTS4P5PIzjy9fHg5ZcRFlrSkqaY+MReNC8A2N zObw==
X-Gm-Message-State: AOAM530//Iw5tveqsFEfNsVgOVRyaIgp58ff3OzZWqSDID0w/90sLqB8 2OHuWiC6HRexU82wXyi7AqYFJ5isuq86MfF6IMVVlYeS
X-Google-Smtp-Source: ABdhPJxc6MbqHwGXzdwaBGEw4FpQPltGqMppH7clmMsxM6xZ9jW0U9gqgYLAfPZcU/ebbSWs75q6r5RCv32NM+rLzWA=
X-Received: by 2002:a37:2796:: with SMTP id n144mr566380qkn.57.1611580068703; Mon, 25 Jan 2021 05:07:48 -0800 (PST)
MIME-Version: 1.0
References: <CAA=duU2nj0G2H9v3Fft5iBAA8bxTX0zNgZsevMpojZY3TZQ6dg@mail.gmail.com> <cc1bf4ec-3b5d-4b91-98de-1ee4e4fe0185@www.fastmail.com>
In-Reply-To: <cc1bf4ec-3b5d-4b91-98de-1ee4e4fe0185@www.fastmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 25 Jan 2021 08:07:32 -0500
Message-ID: <CAA=duU2ZZns7eF-rmx3_bt34MwN3upS4Qc5FZbkwGCwZA9ue0A@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: XML Developer List <xml2rfc-dev@ietf.org>, xml2rfc@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: multipart/alternative; boundary="00000000000085b37905b9b939a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/cKxR4YI5Y8Cv6-0wEHYRHL5Xpis>
Subject: Re: [xml2rfc-dev] Script to generate RFC reference including abstract?
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: Mon, 25 Jan 2021 13:07:52 -0000

Martin,

Thanks, that's an awesome use of curl, which I've used before for other
purposes.

And I had forgotten that the bibxml includes the abstracts.

Cheers,
Andy


On Mon, Jan 25, 2021 at 1:59 AM Martin Thomson <mt@lowentropy.net> wrote:

> To get the reference:
> curl -sSf
> https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml
>
> To get just the abstract:
> curl -sSf
> https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml |
> \
>   xmllint --xpath '//abstract/t/text()' /dev/stdin
>
> On Mon, Jan 25, 2021, at 04:03, Andrew G. Malis wrote:
> > Just to save myself a bit of work if this already exists ....
> >
> > Have any of you written a script when, given a list of RFC numbers,
> > will generate an xml2rfc-ish reference and pull out the abstract for
> > each RFC? Something like, when given "8660", will produce:
> >
> >    [RFC8660]  Bashandy, A., Ed., Filsfils, C., Ed., Previdi, S.,
> >               Decraene, B., Litkowski, S., and R. Shakir, "Segment
> >               Routing with the MPLS Data Plane", RFC 8660,
> >               DOI 10.17487/RFC8660, December 2019,
> >               <https://www.rfc-editor.org/info/rfc8660>.
> >
> >    Segment Routing (SR) leverages the source-routing paradigm.  A node
> >    steers a packet through a controlled set of instructions, called
> >    segments, by prepending the packet with an SR header.  In the MPLS
> >    data plane, the SR header is instantiated through a label stack.
> >    This document specifies the forwarding behavior to allow
> >    instantiating SR over the MPLS data plane (SR-MPLS).
> >
> > Thanks,
> > Andy
> >
> > _______________________________________________
> > xml2rfc-dev mailing list
> > xml2rfc-dev@ietf.org
> > https://www.ietf.org/mailman/listinfo/xml2rfc-dev
> >
>
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>