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

Carsten Bormann <cabo@tzi.org> Wed, 27 March 2019 08:10 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 584BE1200FB for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 27 Mar 2019 01:10:42 -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 P-KzCPTJmYVb for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 27 Mar 2019 01:10:40 -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 3249C120250 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 27 Mar 2019 01:10:40 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9D02BB80EDC; Wed, 27 Mar 2019 01:10:28 -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 E7D8CB80EDC for <rfc-interest@rfc-editor.org>; Wed, 27 Mar 2019 01:10:27 -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 rBUbmrhnnGhT for <rfc-interest@rfc-editor.org>; Wed, 27 Mar 2019 01:10:26 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 3E1E0B80ED9 for <rfc-interest@rfc-editor.org>; Wed, 27 Mar 2019 01:10:26 -0700 (PDT)
Received: from dhcp-8804.meeting.ietf.org (dhcp-8804.meeting.ietf.org [31.133.136.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 44Tgfd4QfxzySP; Wed, 27 Mar 2019 09:10:33 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <346B93E5-A3AC-4E11-B51A-E866004B81A5@ifi.uio.no>
Date: Wed, 27 Mar 2019 09:10:32 +0100
X-Mao-Original-Outgoing-Id: 575367030.341648-a6b355b3c6281cadf4b235881e0a5638
Message-Id: <C09870DB-A414-4EE2-91FF-5A169E411D03@tzi.org>
References: <9B960428-CDAD-4019-95C4-E2B236B2CB73@ifi.uio.no> <ADFC009B-6E01-43FF-ADEC-35E381AD57D5@fugue.com> <155dad06-660c-9d23-4d57-71433085e40c@it.aoyama.ac.jp> <346B93E5-A3AC-4E11-B51A-E866004B81A5@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3445.9.1)
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: "rfc-interest@rfc-editor.org" <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 Mar 27, 2019, at 00:44, Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> Sure - it’s easy to imagine such a tool just producing a long list of useless garbage,

Well, we have the not-quite-NLP “idnits”, and it certainly is useful.
What is missing from idnits, and should be in anything that has false positives, is a way to acknowledge each false positive that has been identified as such, in the source and suppress the listing of that.

Grüße, Carsten

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