Re: [Tools-discuss] Idnits-1.84 feedback

Henrik Levkowetz <henrik@levkowetz.com> Wed, 04 January 2006 13:40 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eu8sX-0008Ux-6m; Wed, 04 Jan 2006 08:40:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eu8sW-0008Us-0Z for tools-discuss@megatron.ietf.org; Wed, 04 Jan 2006 08:40:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01217 for <tools-discuss@ietf.org>; Wed, 4 Jan 2006 08:39:19 -0500 (EST)
Received: from av6-2-sn3.vrr.skanova.net ([81.228.9.180]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eu8xy-0000CM-Nd for tools-discuss@ietf.org; Wed, 04 Jan 2006 08:46:16 -0500
Received: by av6-2-sn3.vrr.skanova.net (Postfix, from userid 502) id DC23F3CA86; Wed, 4 Jan 2006 14:40:03 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av6-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 6B15D3C9EE; Wed, 4 Jan 2006 14:40:03 +0100 (CET)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 5558037E45; Wed, 4 Jan 2006 14:40:03 +0100 (CET)
Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.60) (envelope-from <henrik@levkowetz.com>) id 1Eu8ry-0000xp-EK; Wed, 04 Jan 2006 14:40:02 +0100
Message-ID: <43BBD032.3000103@levkowetz.com>
Date: Wed, 04 Jan 2006 14:40:02 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Hollenbeck <sah@428cobrajet.net>
Subject: Re: [Tools-discuss] Idnits-1.84 feedback
References: <courier.43BAC9B5.00000E26@zeke.ecotroph.net>
In-Reply-To: <courier.43BAC9B5.00000E26@zeke.ecotroph.net>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: tools-discuss@ietf.org
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
Sender: tools-discuss-bounces@ietf.org
Errors-To: tools-discuss-bounces@ietf.org

Hi Scott,

on 2006-01-03 20:01 Scott Hollenbeck said the following:
> I just ran a document through the idnits checker.  It produced some
> unexpected results:

[snip]

> It looks like the tool is checking for 2006 copyright dates now that we're
> in 2006, but that will be a problem for documents that were written in 2005.

You're right, it's checking for copyright dates matching the current year.
I think this is strictly speaking correct, but wouldn't mind adding a grace
period just after each new year.  (Of course, that conflicts with the
current policy with respect to boilerplate, which is to require letter-
perfect adherence, with a male author not even being permitted to change
"he or she" to "he"; something I personally think is silly, but nevermind.)

Any suggestion as to the length of such a grace period?

Or should I instead add a switch to make it possible to say something like

  $ idnits --year 2005 draft-ietf-sieve-3431bis-04.txt

and have idnits accept the given year instead of the current year in copyright
text, maybe?

> The BCP 78 error is interesting.  The text is in the document, but it exists
> after the copyright notice.  Did the tool skip it because of the copyright
> date error?

Yes.  If the text had been in a separate paragraph, it would have been
recognized, but I do some extra work to also recognize multiple boiler-plate
paragraphs which has been contracted into one.  This is done by concatenating
potential boilerplate paragraphs and matching the aggregate against the
current paragraph, and thus fails when one of the parts in the input text
fails to match.

A strategy of instead trying to split paragraphs in the draft input into
potential individual boilerplate paragraphs would not fail in this way, but
would also (I think) be quite a bit more complex.  I may consider re-writing
to do in the future, but won't do it now.


	Henrik

_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/tools-discuss