IETF Logo Mail Archive

Re: [Sedate] Reference to Unicode calendar.xml document

Patrik Fältström <paf@paftech.se> Sun, 09 April 2023 13:41 UTC

Return-Path: <paf@paftech.se>
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 C8B83C15154F for <sedate@ietfa.amsl.com>; Sun, 9 Apr 2023 06:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=paftech.se
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zN2mlKkCZX4Q for <sedate@ietfa.amsl.com>; Sun, 9 Apr 2023 06:41:23 -0700 (PDT)
Received: from mail.paftech.se (vm01.paftech.se [192.165.72.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12079C15154C for <sedate@ietf.org>; Sun, 9 Apr 2023 06:41:21 -0700 (PDT)
Received: from [172.16.5.85] (vpn01-stb.sth.netnod.se [192.71.80.86]) by mail.paftech.se (Postfix) with ESMTPSA id 50409402D2; Sun, 9 Apr 2023 15:41:17 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paftech.se; s=2022013001; t=1681047677; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=K8nlPYXW4qOyfgpD4B6E7GeQcMm7U1MboQOjMRS2zoo=; b=RX9cRn1TSD2/NXoGRtVr7GKt9GUwyh/LTNXyFpoWRE55f6kA7F8I2jhs/GUtGw/VcZy065 pthWQJf3Ok/rZxF4DdXtEw0sA5ZVDDM6No4yrzKO8fiaHL/5k5qF2N2zxVY9yTxtPR6z4r ENJrqOzpq93d74bwOg4cn8V9ddDwqko=
From: Patrik Fältström <paf@paftech.se>
To: Justin Grant <justingrant.ietf.public@gmail.com>
Cc: Bron Gondwana <brong@fastmailteam.com>, sedate@ietf.org
Date: Sun, 09 Apr 2023 15:41:15 +0200
X-Mailer: MailMate (1.14r5950)
Message-ID: <8DF7E2B9-F0AB-46C7-8E39-95FE6D4C5A99@paftech.se>
In-Reply-To: <CACy7CfiwogGzK4fOgg=A+-VLQ6PU871AewTvtCoag1EHWjVquA@mail.gmail.com>
References: <081d58e1-3402-4dc2-a019-ac96d80919c6@dogfoodapp.fastmail.com> <A0BF9F9C-06A2-42E1-B63E-D4397FF90E23@paftech.se> <CACy7CfiwogGzK4fOgg=A+-VLQ6PU871AewTvtCoag1EHWjVquA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_1AC92D56-9294-4F1E-8DF2-13CB248B2A6C_="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/2d-3es6eA7HEMFiNRMJgrfgtsTU>
Subject: Re: [Sedate] Reference to Unicode calendar.xml document
X-BeenThere: sedate@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 09 Apr 2023 13:41:28 -0000

On 7 Apr 2023, at 20:28, Justin Grant wrote:

> Thanks Patrik. Using those links, here's how I'd describe the steps required to get to the list of allowed calendars for the u-ca tag in the SEDATE RFC:
>
> 1. Download https://unicode.org/Public/cldr/latest/core.zip.
> 2. Extract /common/bcp47/calendar.xml from that ZIP file.
> 3. Allowed values for the tag name "u-ca" must be listed in the "name"
> attribute of sub-elements inside the `<key name="ca"...` element.
>
> Bron and Patrik - what is the right way to express those steps in the RFC text?

I do not understand why you have to explain how to dive into the standard :-)

> Or is it sufficient to just say "/common/bcp47/calendar.xml in https://unicode.org/Public/cldr/latest/core.zip" ?

My view, you can not reference any more details than what mentioned as "stable" in the Unicode specification.

But this is something to be tested and validated during last call of the I-D.

   Patrik

v2.23.0 | Report a Bug | By Email