[rfc-i] [IAB] draft-iab-rfcv3-preptool-latest, "5. What the v3 Prep Tool Does"

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Thu, 14 April 2016 19:46 UTC

From: jhildebr at cisco.com (Joe Hildebrand (jhildebr))
Date: Thu, 14 Apr 2016 19:46:35 +0000
Subject: [rfc-i] [IAB] draft-iab-rfcv3-preptool-latest, "5. What the v3 Prep Tool Does"
In-Reply-To: <570D186E.3040205@gmx.de>
References: <570B646A.3090706@gmx.de> <99F21705-E76F-411B-9687-131DE4D455DB@cisco.com> <570D186E.3040205@gmx.de>
Message-ID: <250C66D0-5E35-4EBF-BCFD-28B1D2EC60F7@cisco.com>

On 4/12/16, 9:46 AM, "Julian Reschke" <julian.reschke at gmx.de> wrote:



>On 2016-04-12 16:47, Joe Hildebrand (jhildebr) wrote:
>> Can we at least normalize the common case (English month names)?  Other values can be allowed, but those will always be detectable as not-useful-for-math very quickly after normalization.
>
>I think a cleaner solution would be to leave the dates in references 
>alone. What's the point in rewriting them?

This came up during the IAB review of the document set.  A couple of people complained about English month names being used for date semantics, rather than just local display.  I would be ok with this only applying to /rfc/front/date, if that makes a difference.

-- 
Joe Hildebrand