Re: [Json] I-JSON(2014-06-13) Section 4.3. Time and Date Handling

John Cowan <cowan@mercury.ccil.org> Sun, 15 June 2014 01:38 UTC

Return-Path: <cowan@ccil.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5053A1B2A5A for <json@ietfa.amsl.com>; Sat, 14 Jun 2014 18:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.251
X-Spam-Level:
X-Spam-Status: No, score=-5.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 CiugJJxydImc for <json@ietfa.amsl.com>; Sat, 14 Jun 2014 18:38:14 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D6F81B2946 for <json@ietf.org>; Sat, 14 Jun 2014 18:38:14 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1WvzOe-0008Vp-4J; Sat, 14 Jun 2014 21:38:12 -0400
Date: Sat, 14 Jun 2014 21:38:12 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20140615013812.GA22935@mercury.ccil.org>
References: <20140613195805.1386.5992.idtracker@ietfa.amsl.com> <CAHBU6ivy-aVuSZPQ1gMp0bXW0yMYq9Vhi1Bydb809rfBR_ag=g@mail.gmail.com> <539C3367.7090301@drees.name> <CAHBU6iuvOU6L7rhyiQnG_sqsdR6QkeqMHcT8HwH6Y8UFa_Ue3w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAHBU6iuvOU6L7rhyiQnG_sqsdR6QkeqMHcT8HwH6Y8UFa_Ue3w@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/json/3-2BqAShf5DlNTYTyXNcEIhlFDI
Cc: Stefan Drees <stefan@drees.name>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] I-JSON(2014-06-13) Section 4.3. Time and Date Handling
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jun 2014 01:38:17 -0000

Tim Bray scripsit:

> Also, could any date/time scholars here have a look at section 3.3 of
> RFC4287 - http://tools.ietf.org/html/rfc4287#section-3.3 - and see if they
> think some of that language should be adopted here.

That basically says to use T and Z rather than t and z, which I agree
is good.  So here's my proposal:

   Protocols often contain data items which are designed to contain
   timestamps or time durations.  It is RECOMMENDED that all data
   items containing timestamps conform to the "date-time" production
   in [RFC3339], with the additional restriction that uppercase rather
   than lowercase letters be used.  It is also RECOMMENDED that all data
   items containing time durations conform to the "duration" production
   in Appendix A of [RFC3339], with the same additional restriction.

I would further urge that the recommendation be changed to requirements.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
A few times, I did some exuberant stomping about, like a hippo auditioning
for Riverdance, though I stopped when I thought I heard something at
the far side of the room falling over in rhythm with my feet.  --Joseph Zitt