Re: [dispatch] [Sedate] WG Review: Serialising Extended Data About Times and Events (sedate)

Ujjwal Sharma <ryzokuken@igalia.com> Fri, 04 June 2021 06:12 UTC

Return-Path: <ryzokuken@igalia.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD933A2AE8; Thu, 3 Jun 2021 23:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
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 Fu0bZoCg17zz; Thu, 3 Jun 2021 23:12:12 -0700 (PDT)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B243A2ABE; Thu, 3 Jun 2021 23:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=SnElsK9XY6sHEB0nmePpWfZBBC9BYtn5GrwnV8qK90g=; b=kxRV570D83bD/vmrhRdXDcNOI7Ye7JhD+hDDV9Ev4MElwzgP/gz2e1YQUj4E6Hi1rULp7lIEWFAdGbLFKYaQeL7Hn7GpJb827zpyMpxJLfmKWhpMYKaXpObYLD8CKgNiHMt9vp2moYeM/U+j12pboSm8Q6ecinVKCkLzqep4BytRo2ixhleRYXZBlzeRfe0ZcssbaDJmxgE90PSflC9Jbg1C9gEEFhX1IgZFT110tH7u2leG+7a9w1/rbMXTeX2uCbYE3YjBPBNEa3stZdIoAj5BNE99/zBi3jYkwvA2Ubkhzpsaw6Y0j/HAJUwwNQfD2eFFRG/G0RbAewGVDhKEiQ==;
Received: from [183.83.213.107] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1lp33r-0005cr-OC; Fri, 04 Jun 2021 08:12:03 +0200
To: Carsten Bormann <cabo@tzi.org>, ned+sedate@mrochek.com
Cc: DISPATCH <dispatch@ietf.org>, sedate@ietf.org, Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>
References: <162255609215.5567.6852158423318065168@ietfa.amsl.com> <EEA84B36-BEA8-43F2-98F1-7C1BD817278F@ericsson.com> <01RZPZV5ELIY0085YQ@mauve.mrochek.com> <48D3CA53295C2C8C1045A23D@PSB> <01RZSYH3BXYS00IM2V@mauve.mrochek.com> <D99F554C-543A-4244-B871-26308F3EC393@tzi.org>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <b85e1d9e-0376-1309-93f3-61172c7c5275@igalia.com>
Date: Fri, 04 Jun 2021 11:41:51 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <D99F554C-543A-4244-B871-26308F3EC393@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/agzxKr40t_tsL3diJo3OBDbxNyA>
Subject: Re: [dispatch] [Sedate] WG Review: Serialising Extended Data About Times and Events (sedate)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2021 06:12:17 -0000

Hey Carsten!

On 04/06/2021 04.31, Carsten Bormann wrote:
> My spies tell me ISO 8601-2:2019 was created as a container for a number of the ideas that aren’t so relevant for text-based date-times (uncertainties? Spring Northern Hemisphere?  Quadrimesters?).
> ISO 8601-1:2019 seems to have 6-digit years (±NNNNNN, so it’s +002021-06-03T22:44:37.095927Z here right now), which we should adopt (but certainly not century or decade references and lots of other innovations that are great for library managers but not so much on the Internet).
> 
> I think there should be a really high burden of proof for anyone wanting to bring anything else that hasn’t been part of the version of ISO 8601 that was used at the time RFC 3339 was published.
> (This should be in the charter, and the details can then be discussed in the WG.)

I agree here. There were parts of ISO 8601 that were excluded from RFC
3339 and we should adopt a similar strategy here, avoiding anything that
seems to be excessive.

As a matter of fact, I chose to only include the expanded year format as
well as sub-minute offsets because they were the only additions that
seemed reasonable to me at the time. I'd be happy to consider further
additions, but I agree that they should be well-justified to make the cut.

> The Temporal proposal in TC39, however, is highly relevant.
> However, it seems it is at stage 2...

This is no longer true, since Temporal has reached Stage 3 in the TC39
process and many delegates are already working on implementing it in
various engines. However, none of the implementations would ship
unflagged until we move ahead with this work since the format might
still be in flux...

Hope this helps,
Best,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker