[rfc-i] looking for a volunteer to write a simple script

Heather Flanagan <rse@rfc-editor.org> Fri, 12 July 2019 16:55 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 13FFA120165 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 12 Jul 2019 09:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.199
X-Spam-Level:
X-Spam-Status: No, score=-5.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 t9NHVqi7xy4m for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 12 Jul 2019 09:55:18 -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 2D14512004E for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 12 Jul 2019 09:55:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B4A93B811A4; Fri, 12 Jul 2019 09:55:12 -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 CC33CB811A4 for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:10 -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 N_b54YEA-DWC for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:09 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id B34B0B80C87 for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4BB661C135B for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:05 -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 u_joh2ytA5l5 for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:05 -0700 (PDT)
Received: from [172.16.4.218] (unknown [65.213.217.186]) by c8a.amsl.com (Postfix) with ESMTPSA id 04CB41C1351 for <rfc-interest@rfc-editor.org>; Fri, 12 Jul 2019 09:55:04 -0700 (PDT)
Date: Fri, 12 Jul 2019 09:55:04 -0700
From: Heather Flanagan <rse@rfc-editor.org>
To: RFC Interest <rfc-interest@rfc-editor.org>
Message-ID: <38d0704f-348c-4ec0-9d94-340747960201@Spark>
References: <62c8413d-c735-4ec3-8b22-eb0fa5356636@Spark>
X-Readdle-Message-ID: 38d0704f-348c-4ec0-9d94-340747960201@Spark
MIME-Version: 1.0
Subject: [rfc-i] looking for a volunteer to write a simple script
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>
Content-Type: multipart/mixed; boundary="===============8842649008795458982=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hola a todos!

The RFC Editor has the need for a comparatively simple script that would automatically add <bcp14></bcp14> tags to requirement language in v3 RFCs.

Specifically, this would take a v3 XML input file, and create a v3 XML output file with <bcp14></bcp14> added around each instance of a 2119 keyword in the file. (MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL)

Anyone up for helping us out with that?

Thanks! Heather
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest