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

Stefan Drees <stefan@drees.name> Sat, 14 June 2014 11:35 UTC

Return-Path: <stefan@drees.name>
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 857E61B27DB for <json@ietfa.amsl.com>; Sat, 14 Jun 2014 04:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 ZZYPfpGjlD1O for <json@ietfa.amsl.com>; Sat, 14 Jun 2014 04:35:08 -0700 (PDT)
Received: from mout.web.de (mout.web.de [212.227.15.14]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D27641A0325 for <json@ietf.org>; Sat, 14 Jun 2014 04:35:07 -0700 (PDT)
Received: from newyork.local.box ([80.187.96.183]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0LqXBp-1WIZfl2Zw9-00e8kT; Sat, 14 Jun 2014 13:35:04 +0200
Message-ID: <539C3367.7090301@drees.name>
Date: Sat, 14 Jun 2014 13:35:03 +0200
From: Stefan Drees <stefan@drees.name>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Tim Bray <tbray@textuality.com>
References: <20140613195805.1386.5992.idtracker@ietfa.amsl.com> <CAHBU6ivy-aVuSZPQ1gMp0bXW0yMYq9Vhi1Bydb809rfBR_ag=g@mail.gmail.com>
In-Reply-To: <CAHBU6ivy-aVuSZPQ1gMp0bXW0yMYq9Vhi1Bydb809rfBR_ag=g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:tvfV0RAuWtRqHji0z7Eq10wByM++V2qWEuBs+R3GzSszZDxwmt+ IhqggiK4IHvXamMf+I8lcSH4pQStT5UiQM0PnU68WZTE+T7RhqEhxVEYcDTEJvD1ooPdCqW Qy7VPSPdw7mofy9/ahTbM5/dzZkgkz46fvV/2ahSUXdNIjffN2Vp2j04t6B+Sx2GMlwGHU4 WjBbFQpzfdAQ26nD2Nr2w==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/hpc1aOACqVJPkyfcNihsAESaSfM
Cc: json@ietf.org
Subject: [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
Reply-To: stefan@drees.name
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: Sat, 14 Jun 2014 11:35:09 -0000

Thanks for providing this, Tim.
On 2014-06-13 22:01 +02:00, Tim Bray wrote:
> Real HTML is at http://www.tbray.org/tmp/draft-ietf-json-i-json-01.html
>
>
> On Fri, Jun 13, 2014 at 12:58 PM, <internet-drafts@ietf.org
> <mailto:internet-drafts@ietf.org>> wrote:
>
>
>     A New Internet-Draft is available from the on-line Internet-Drafts
>     directories.
>       This draft is a work item of the JavaScript Object Notation
>     Working Group of the IETF.
>
>              Title           : The I-JSON Message Format
>              Author          : Tim Bray
>              Filename        : draft-ietf-json-i-json-01.txt
>              Pages           : 6
>              Date            : 2014-06-13
>
>     Abstract:
>         I-JSON is a restricted profile of JSON designed to maximize
>         interoperability and increase confidence that software can
>     process it
>         successfully with predictable results.
>
>
>     The IETF datatracker status page for this draft is:
>     https://datatracker.ietf.org/doc/draft-ietf-json-i-json/
> ...

I read over it and section 4.3 "Time and Date Handling" might profit 
from one or two small changes:

OLD:
4.3.  Time and Date Handling

    Protocols often contain data items which are designed to contain
    timestamps or time durations.  It is RECOMMENDED that in all such
    data items be expressed in in ISO 8601 format, as specified in
    [RFC3339].

NEW (suggested):
4.3.  Time and Date Handling

    Protocols often contain data items which are designed to contain
    timestamps or time durations.  It is RECOMMENDED that in all such
    data temporal items be expressed in ISO 8601 format, as specified
    in [RFC3339].


{"end_of_changes": true}

Removing the doubled "in" is a sure thing for me, but if others would 
also subsume "the targeted items" as "temporal items" I do really not 
know and thus happily delegate to the native english speakers on this list.

The motivating sentence reminds me a bit of the significance of sister 
phrases like "Life often is ..." but as it is true (in my experience) 
and if no one else is irritated by quantifiers like "often" I see no 
need to discuss.

All the best,
Stefan.