Re: [Sedate] Can offsets like [+02:00] be used instead of IANA names in brackets?

Ujjwal Sharma <ryzokuken@igalia.com> Tue, 08 March 2022 16:03 UTC

Return-Path: <ryzokuken@igalia.com>
X-Original-To: sedate@ietfa.amsl.com
Delivered-To: sedate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0471C3A0E53 for <sedate@ietfa.amsl.com>; Tue, 8 Mar 2022 08:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 6lywVuW2GcHZ for <sedate@ietfa.amsl.com>; Tue, 8 Mar 2022 08:03:16 -0800 (PST)
Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1AC3A11C8 for <sedate@ietf.org>; Tue, 8 Mar 2022 08:03:10 -0800 (PST)
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:From: References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=lApRIQJClmpP8HA7Ju2/eMDQviq1Qv3+3Wn8YaX1CMw=; b=awI5K8tCSegJY1eE5DnrGz7WDc +bFRBTBGNn4GMiVqe8qBkzXU9wHkWtgfgmJtg7cEuTDr8Tv9YlaHYXr5hrWOPUVYhNfOAHRsFbxTo 53gNCuQGBuTpuJgQ8ho07v76sBpYSYSRnhTW4x3GYZEI0M6TAUUCcEyY+8XmLyWsthORQzOVVvzRN +Pgpdf3SyyXkCy8GdD8Sh1x4OlGpf/pO3nX7bO0fAdDHhhDmaxTw0FAvQANf9ehmhct7NEaOLvGlZ gcZz6Edxk2JtxLiIwJGFdn+bxCWmdnuldPR526NPTXUg02vSNsaJgvm2n/rNdNlIOkTn8wnyD9q7t Styv4L4Q==;
Received: from [125.63.110.98] (helo=[192.168.55.108]) by fanzine2.igalia.com with esmtpsa (Cipher TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim) id 1nRcIl-0005sL-EW; Tue, 08 Mar 2022 17:03:07 +0100
Message-ID: <c8035af7-1302-a04a-e449-76db3ad1754e@igalia.com>
Date: Tue, 08 Mar 2022 21:32:54 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: Justin Grant <justingrant.ietf.public@gmail.com>, sedate@ietf.org
References: <CACy7CfhB63dgxatWHYSr-KMKP1SWwd6nRmumCSCPVijgYede4A@mail.gmail.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
In-Reply-To: <CACy7CfhB63dgxatWHYSr-KMKP1SWwd6nRmumCSCPVijgYede4A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/lySFIyvBYxcDroJ7Uoc5o6dSh4I>
Subject: Re: [Sedate] Can offsets like [+02:00] be used instead of IANA names in brackets?
X-BeenThere: sedate@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Serialising Extended Data About Times and Events <sedate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sedate>, <mailto:sedate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sedate/>
List-Post: <mailto:sedate@ietf.org>
List-Help: <mailto:sedate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sedate>, <mailto:sedate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2022 16:03:21 -0000

While this format certainly looks weird, I believe we should include it 
for backwards compatibility with the de-facto standard. Any compelling 
arguments to avoid this at all costs?

Ujjwal

On 08/03/2022 04.52, Justin Grant wrote:
> The current ABNF for the time zone extension does not support offset 
> time zones, e.g. [+08:45]. Offset zones are supported in java.time, 
> which is the prior art driving the bracketed time zone extension format. 
> Should the standard also allow offsets in brackets too?
> 
> https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/issues/12 
> <https://github.com/ietf-wg-sedate/draft-ietf-sedate-datetime-extended/issues/12> 
> has discussion relevant to this question.
> 
> FWIW, in the design of Temporal we've assumed that we should support 
> offsets in brackets for compatibility with Java. Here's a Java example:
> 
> public  class  MyClass  {
>      public  static  void  main(String  args[]) {
>        java.time.ZonedDateTime  zdt=  java.time.ZonedDateTime.parse("2021-12-09T00:00-08:00[-08:00]");
>        System.out.println(zdt.toString());
>      }
> }
> 
> Cheers,
> Justin Grant
> 

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

Compilers Hacker, Node.js Core Collaborator and Speaker