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

Dick Franks <rwfranks@acm.org> Sat, 13 July 2019 12:24 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 18613120381 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 13 Jul 2019 05:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level:
X-Spam-Status: No, score=-4.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 6aWn9rPim96g for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 13 Jul 2019 05:24:29 -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 8EEBB1202B5 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sat, 13 Jul 2019 05:24:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5AA20B80BCE; Sat, 13 Jul 2019 05:24:22 -0700 (PDT)
X-Original-To: rfc-interest+banned@rfc-editor.org
Delivered-To: rfc-interest+banned@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 1E9FDB80BCE; Sat, 13 Jul 2019 05:24:21 -0700 (PDT)
X-Quarantine-ID: <3Mv3zvOdzwAt>
X-Amavis-Modified: Mail body modified (defanged) - rfcpa.amsl.com
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BANNED, message contains application/octet-stream,.exe,tag_keywords
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 3Mv3zvOdzwAt; Sat, 13 Jul 2019 05:24:19 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1563020661-25574-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by rfc-editor.org (Postfix) with ESMTPS id 99239B80BCD; Sat, 13 Jul 2019 05:24:19 -0700 (PDT)
Received: by mail-io1-f50.google.com with SMTP id o9so26282586iom.3; Sat, 13 Jul 2019 05:24:24 -0700 (PDT)
References: <62c8413d-c735-4ec3-8b22-eb0fa5356636@Spark> <38d0704f-348c-4ec0-9d94-340747960201@Spark>
In-Reply-To: <38d0704f-348c-4ec0-9d94-340747960201@Spark>
From: Dick Franks <rwfranks@acm.org>
Date: Sat, 13 Jul 2019 13:23:47 +0100
Message-ID: <CAKW6Ri4mN3vzN8Pg+aWNaD79YnSMeXU01m64UR7nxCDTzcPw+g@mail.gmail.com>
To: Heather Flanagan <rse@rfc-editor.org>
Subject: Re: [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>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

WARNING: banning rules detected suspect part(s),
do not open unless you know what you are doing
--- Begin Message ---
More robust solution that recognises keywords within quotes and/or
split across line break.

Dick Franks
________________________


On Fri, 12 Jul 2019 at 17:55, Heather Flanagan <rse@rfc-editor.org> wrote:
>
> 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
--- End Message ---
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest