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

[Tim Bray <[e-mail]>]

Superfluous “in” nuked, thanks.

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.


On Sat, Jun 14, 2014 at 4:35 AM, Stefan Drees <[e-mail]> wrote:

> 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, <[e-mail]
>> <mailto:[e-mail]>> 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.
>
>


-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)