Re: [rfc-i] Natural Language Processing (NLP) applied to RFCs

Colin Perkins <csp@csperkins.org> Wed, 27 March 2019 06:56 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 6547412025B for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Mar 2019 23:56:32 -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, HEADER_FROM_DIFFERENT_DOMAINS=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 v8s4B72Z_tEO for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Mar 2019 23:56:30 -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 857AD120256 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Mar 2019 23:56:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1BA38B81EA8; Tue, 26 Mar 2019 23:56:19 -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 29E44B81EA7 for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 23:56:17 -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 67IXMNJUi_JN for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 23:56:15 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by rfc-editor.org (Postfix) with ESMTPS id 565B2B81EA6 for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 23:56:15 -0700 (PDT)
Received: from [2001:67c:1232:144:f8a5:6cf8:2709:4491] (port=53703) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1h92U3-0002ug-T6; Wed, 27 Mar 2019 06:56:24 +0000
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <9B960428-CDAD-4019-95C4-E2B236B2CB73@ifi.uio.no>
Date: Wed, 27 Mar 2019 07:56:21 +0100
Message-Id: <CA47B1AD-25C1-4BD9-AA62-81CD23811C54@csperkins.org>
References: <9B960428-CDAD-4019-95C4-E2B236B2CB73@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Subject: Re: [rfc-i] Natural Language Processing (NLP) applied to RFCs
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: Gareth Tyson <g.tyson@qmul.ac.uk>, rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

> On 26 Mar 2019, at 11:39, Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> I’m planning to do research with colleagues in NLP, with various ideas on applying it to RFCs (and, perhaps more importantly, Internet-drafts, which means that we can give feedback *before* RFC publication).
> One example outcome of this is that we could perhaps produce a tool that automatically gives feedback on language clarity - e.g. “You may want to check this sentence again, are you sure it specifies what should go into that header field clearly enough?”  Heck, perhaps we can even give feedback like “shouldn’t this be an uppercase SHOULD here?”.
> 
> I’d like to understand what people think about doing such stuff, in general - would a tool that gives some such feedback as a result of using NLP be useful to have?
> (obviously, *I* think so…)


I definitely think it could be useful. I’ve got a proposal under consideration, with Gareth Tyson and colleagues at QMUL, to try to get funding do something similar – we should sync-up.

Cheers,
Colin



-- 
Colin Perkins
https://csperkins.org/




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