From nobody Fri Apr 14 07:50:09 2023 Return-Path: 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 AA898C151B14 for ; Fri, 14 Apr 2023 07:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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, 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 (2048-bit key) header.d=igalia.com 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 lPbGKKIpU7Zb for ; Fri, 14 Apr 2023 07:50:03 -0700 (PDT) Received: from fanzine2.igalia.com (fanzine2.igalia.com [213.97.179.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49512C151551 for ; Fri, 14 Apr 2023 07:50:02 -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: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=As3I1WoydShBwPMYRPAMTjp0x2Ev9c9IS4V7KImYACw=; b=O7+c9sJ5VqglYQI0GSiU5suQtc v3AmbsHAbEquI9P1V0U7Km4M6t2A1PEPcYXf+oSE9oDiUkj5VPkUchPk0LxtczU9Q5hDqT1QHEIth PAWUZigvkGlgAiUFaEXW/nBefuVYGGu9uHRvIBRiMLn2ThP68GfUB9yA4vkS/w1YU0AxSa670je5/ G5d2jVntjjLN/NJ6g9CHmyABoQS6+mwVm0wlYQ7Zepi3CdwMLOW1/in1F0tVFQOMgOt1N1ZEuQwo6 fzM0EhixOMjAdxhP1HOQnes4YV5sHJnzCLZha1o/rp4L2qO3H6rgsvR9AMBObk8IMg/7FvCvQatjY dlAxv0VQ==; Received: from static-246-230-60-95.ipcom.comunitel.net ([95.60.230.246] helo=[192.168.0.13]) by fanzine2.igalia.com with esmtpsa (Cipher TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim) id 1pnKkS-0017C0-5I for ; Fri, 14 Apr 2023 16:49:59 +0200 Message-ID: <440bd5d8-cf52-f0c7-31e6-3752c1c4f3f8@igalia.com> Date: Fri, 14 Apr 2023 16:49:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 To: sedate@ietf.org References: <081d58e1-3402-4dc2-a019-ac96d80919c6@dogfoodapp.fastmail.com> <8DF7E2B9-F0AB-46C7-8E39-95FE6D4C5A99@paftech.se> Content-Language: en-US From: Ujjwal Sharma Organization: Igalia S.L. In-Reply-To: <8DF7E2B9-F0AB-46C7-8E39-95FE6D4C5A99@paftech.se> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2023 14:50:07 -0000 Hi Patrik! I believe the reason why Justin wanted to know how to lay out specific directions is to pinpoint the reference to the specific section which contains these calendar identifiers since otherwise a reader of the RFC might find it difficult to navigate the entire spec just to find out the list of permissible values. Hope that clarifies the situation, Ujjwal On 09/04/2023 15:41, Patrik Fältström wrote: > 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 `> >> 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 > > -- Ujjwal "Ryzokuken" Sharma (he/him) Compilers Hacker at Igalia