IETF Logo Mail Archive

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

Martin J. Dürst <duerst@it.aoyama.ac.jp> Tue, 26 March 2019 23:40 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 4641212012F for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Mar 2019 16:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.02
X-Spam-Level:
X-Spam-Status: No, score=-4.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FROM_EXCESS_BASE64=0.979, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=itaoyama.onmicrosoft.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 dW2uzHkcZmEK for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Mar 2019 16:40:39 -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 4ED16120126 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Mar 2019 16:40:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 376F3B8219C; Tue, 26 Mar 2019 16:40: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 08F93B8219B for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 16:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 tlUfPxZwIlS8 for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 16:40:25 -0700 (PDT)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410119.outbound.protection.outlook.com [40.107.141.119]) by rfc-editor.org (Postfix) with ESMTPS id 23268B8219A for <rfc-interest@rfc-editor.org>; Tue, 26 Mar 2019 16:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2gs5PRhkvugevFSmTKIbaBvLx2HG14J7t+b8pnsG3hY=; b=jhMxr30Mq6s6TY0kvc4MLP98wr/JvpiFNDeFHoFJxBh8sfffJb/BWbf3ztHFawWToa314+zShqBS8ZQP9wg1/EeRdn99u4zD4maEBDeJTzUIGECu49DAU3CvxKpQJXEauqYQExqbM8i8BV7XwhIDJ3BBvUImwHBv+wMDCgbEQYc=
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com (20.179.187.18) by TYAPR01MB4639.jpnprd01.prod.outlook.com (20.179.174.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.18; Tue, 26 Mar 2019 23:40:32 +0000
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::98b6:d90e:9ae7:302]) by TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::98b6:d90e:9ae7:302%3]) with mapi id 15.20.1730.019; Tue, 26 Mar 2019 23:40:32 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Ted Lemon <mellon@fugue.com>, Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [rfc-i] Natural Language Processing (NLP) applied to RFCs
Thread-Index: AQHU48Ap4j0rM4uHE0WhOM3Q23pRjaYd4QCAgACyFoA=
Date: Tue, 26 Mar 2019 23:40:31 +0000
Message-ID: <155dad06-660c-9d23-4d57-71433085e40c@it.aoyama.ac.jp>
References: <9B960428-CDAD-4019-95C4-E2B236B2CB73@ifi.uio.no> <ADFC009B-6E01-43FF-ADEC-35E381AD57D5@fugue.com>
In-Reply-To: <ADFC009B-6E01-43FF-ADEC-35E381AD57D5@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYAPR01CA0189.jpnprd01.prod.outlook.com (2603:1096:404:ba::33) To TYAPR01MB5149.jpnprd01.prod.outlook.com (2603:1096:404:12e::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [223.218.133.122]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e69f5028-b148-413f-85f4-08d6b2446f80
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(5600127)(711020)(4605104)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7025125)(7027125)(7023125)(2017052603328)(7153060)(7193020); SRVR:TYAPR01MB4639;
x-ms-traffictypediagnostic: TYAPR01MB4639:
x-microsoft-antispam-prvs: <TYAPR01MB46395575A0CE23314271E39ACA5F0@TYAPR01MB4639.jpnprd01.prod.outlook.com>
x-forefront-prvs: 09888BC01D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(376002)(396003)(346002)(136003)(366004)(39840400004)(199004)(189003)(386003)(81156014)(53546011)(6246003)(71190400001)(105586002)(71200400001)(74482002)(68736007)(6436002)(256004)(81166006)(6486002)(106356001)(31696002)(53936002)(25786009)(14454004)(86362001)(186003)(85202003)(26005)(8676002)(102836004)(8936002)(66066001)(476003)(229853002)(446003)(85182001)(486006)(2616005)(4326008)(11346002)(6506007)(97736004)(2906002)(5660300002)(316002)(3846002)(786003)(4744005)(305945005)(76176011)(52116002)(6512007)(110136005)(508600001)(99286004)(31686004)(7736002)(6116002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:TYAPR01MB4639; H:TYAPR01MB5149.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ug8wOJc6KQtJJdLlTxeuswzO+QJyhx0xEvN3fU+9l03OplrLN8zJgt53PtOTmkdUJ4kb0hpjVbfrDwUxI2wZV6xfh72Iy/OHuNZQp9AiopJ6nS1Z7Aq/XYiHmsvBjzRjDlxrbGtcBMEeS78adIdqp3/jrYTVpdqHNklGXXq1TRKV54+/kycebNGptbhv+HH5TgRQSLHpgM0/1kd4+D5C77jzzsbDyjtYBdBoj+faqbe1YyXYWpfhRQozltr6dJNPim31j85hXJbanorg/0D6/Ta3OuVR/jMuskJ+JeVdvRMgI+dwhDdW8oRhtYPPdbWAGUtF/Abo00gnvfC6AoI/daLQW16YmcRQewiqB91ftQKsMHv0HFNWBhp+U1Qfoxpyc1AjZIoImLCoxI3SNWvaH0LDOuxknHsh4Jj/2hwUVCE=
Content-ID: <03D24E1EE21B6849BD30EF96240FF713@jpnprd01.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: e69f5028-b148-413f-85f4-08d6b2446f80
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2019 23:40:31.9779 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB4639
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 2019/03/26 22:03, Ted Lemon wrote:
> On Mar 26, 2019, at 11:39 AM, Michael Welzl <michawe@ifi.uio.no> wrote:
>> 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?
> 
> Yes, definitely.   This is a perennial problem.

I very much agree with the problem. Of course, it will depend on how 
useful the tool's output is :-).

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

v2.23.0 | Report a Bug | By Email