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

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Tue, 12 April 2016 14:47 UTC

From: jhildebr at cisco.com (Joe Hildebrand (jhildebr))
Date: Tue, 12 Apr 2016 14:47:11 +0000
Subject: [rfc-i] [IAB] draft-iab-rfcv3-preptool-latest, "5. What the v3 Prep Tool Does"
In-Reply-To: <570B646A.3090706@gmx.de>
References: <570B646A.3090706@gmx.de>
Message-ID: <99F21705-E76F-411B-9687-131DE4D455DB@cisco.com>

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.

-- 
Joe Hildebrand





On 4/11/16, 5:46 AM, "IAB on behalf of Julian Reschke" <iab-bounces at iab.org on behalf of julian.reschke at gmx.de> wrote:

>The editor's copy of the spec says in 
><draft-iab-rfcv3-preptool-latest.html#rfc.section.5>:
>
>"Normalize the values of ?month? attributes in all <date> elements to 
>numeric values."
>
>Yet <draft-iab-xml2rfc-03.html#element.date> says:
>
>"The date information can have prose text for the month or year. For 
>example, vagu"e dates (year="ca. 2000"), date ranges (year="2012-2013"), 
>non-specific months (month="Second quarter") and so on are allowed."
>
>...so I don't see how rewriting month attributes would be always possible.
>
>Best regards, Julian
>