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

Justin Grant <justingrant.ietf.public@gmail.com> Fri, 07 April 2023 18:28 UTC

Return-Path: <justingrant.ietf.public@gmail.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 1763EC151B3F for <sedate@ietfa.amsl.com>; Fri, 7 Apr 2023 11:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 AUFcm9ea6Nqn for <sedate@ietfa.amsl.com>; Fri, 7 Apr 2023 11:28:15 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 19CD5C151B31 for <sedate@ietf.org>; Fri, 7 Apr 2023 11:28:15 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id l11so2716367qtj.4 for <sedate@ietf.org>; Fri, 07 Apr 2023 11:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680892094; x=1683484094; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rcTKrdIspyDwszmzr6ZSCTIeNqYQcVe2VFTpvAjUmN8=; b=ecQQN+MG3vBtdEH17RpTgG1iMNP/nxsK7EQRyqlleXFGvehTO0/JMYPOZ1YpW2W8nk ewrnrJqMGFBpavBDB/SsB7cr+rPD6wr+mOIVBJp6VTk4CtQ24Jka9AYAW83fMCiOJvcz 6/9f9MobOTqJ9bbwPpveBUiqHOERNcloly+17rustcEQa0h+ZYQE5fY3L8oAgRJZQf77 6/BuSpkDtuN1K+DQnR7Snj1SEWnOfsvPEaZ8yY3QNDHQ8J6qlZ+akT5/z6Jd1pxgLKAm 7hv5MQZ/7evrV/zB2rSfLZuugT1wi8obOcLZkmASgbGk8OIlrETPbzUr8N/0jHMGEkjU veaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680892094; x=1683484094; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rcTKrdIspyDwszmzr6ZSCTIeNqYQcVe2VFTpvAjUmN8=; b=b95coB41KFhUR/9T1XukncYS025NSnfbnLqkZDvvx+kmlKvGP9x1/FKOC2mUJnJgpM +mdQJO5JB/vhBisET2FVqMbl3hqHAz78pHZ7aqCZy6D3pENNu487/huE+rUWi277VwC1 IweHXCDsIV5gmWODfN30UGWE71bSsNr3ja8Hcv65zxaU90ZDzfEvCMQSZ6/ZjeiuZmea N/GA3FkMelX//1NzntXf+VwGRuLafkWpjHg5nOSPxWTFsfJvFHi36IGze/pgidwxJQRe FsClcFyBC+fiXN+ma4LUAu0ApwmgV0d0gimMrX9ycbD+m733rAcrlKBVy7d0H8MGAsk6 dIgg==
X-Gm-Message-State: AAQBX9dPDPEUCp3I7AFFaGdhVjhwLqxLaKj4M/hdVuE9PyPwnaq2ItNI pR7nhuPxpO+3tu0kmWGfe7a2eV8MjGxi5X4y3oS19f58FiE=
X-Google-Smtp-Source: AKy350ZRjWzlEQpTECtgUQHxkctSLZpqvgMA90HncF/nS39rlynhLsB2e48osPpofoKGUoS2QE2RZSVi5kIjaUKW4o0=
X-Received: by 2002:a05:622a:1302:b0:3e6:720f:baed with SMTP id v2-20020a05622a130200b003e6720fbaedmr1040062qtk.0.1680892093800; Fri, 07 Apr 2023 11:28:13 -0700 (PDT)
MIME-Version: 1.0
References: <081d58e1-3402-4dc2-a019-ac96d80919c6@dogfoodapp.fastmail.com> <A0BF9F9C-06A2-42E1-B63E-D4397FF90E23@paftech.se>
In-Reply-To: <A0BF9F9C-06A2-42E1-B63E-D4397FF90E23@paftech.se>
From: Justin Grant <justingrant.ietf.public@gmail.com>
Date: Fri, 07 Apr 2023 11:28:03 -0700
Message-ID: <CACy7CfiwogGzK4fOgg=A+-VLQ6PU871AewTvtCoag1EHWjVquA@mail.gmail.com>
To: Patrik Fältström <paf=40paftech.se@dmarc.ietf.org>
Cc: Bron Gondwana <brong@fastmailteam.com>, sedate@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002823b005f8c33071"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sedate/ClWVCKRNbgc-L8XSo1Fu-eK81qk>
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: Fri, 07 Apr 2023 18:28:19 -0000

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?

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

Thanks
Justin


On Fri, Apr 7, 2023 at 9:04 AM Patrik Fältström <paf=
40paftech.se@dmarc.ietf.org> wrote:

> Hi,
>
> I have had a look at this, and believe the link into GitHub is not really
> what is what should be done, as you say. I also think that the link to
> "repos" is wrong as that is a redirect into GitHub.
>
> The correct reference is given by referencing the correct version of CLDR
> that you are using, and how to link is explained on this unicode consortium
> web site:
>
> <https://cldr.unicode.org/stable-links-info>
>
> I.e. if you go with version 22 you should use <
> http://cldr.unicode.org/index/downloads/cldr-22> etc.
>
> Best, Patrik
>
> On 6 Apr 2023, at 5:54, Bron Gondwana wrote:
>
> > Hi Patrik,
> >
> > I'm one of the chairs of the SEDATE working group.  I'm emailing you in
> your capacity as the IETF Liaison to Unicode.
> >
> > We have a document in our working group that references a Unicode
> registry:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-sedate-datetime-extended/
> >
> > Which currently has these references:
> >
> >    [CLDR]     "Unicode CLDR Project", <https://cldr.unicode.org> .
> >
> >    [CLDR-CALENDAR]
> >               "cldr/common/bcp47/calendar.xml", <https://github.com/
> >               unicode-org/cldr/blob/main/common/bcp47/calendar.xml>.
> >
> > We'd like to reference something better than github!
> >
> > We discovered during our session at IETF116 that the registry has been
> referenced before - in RFC7529 like so:
> >
> >    [UNICODE.CLDR]
> >               The Unicode Consortium, "CLDR calendar.xml Data", Unicode
> >               Consortium CLDR,
> >               <http://www.unicode.org/repos/cldr/tags/latest/common/ <
> http://www.unicode.org/repos/cldr/tags/latest/common/bcp47/calendar.xml>
> >               bcp47/calendar.xml <
> http://www.unicode.org/repos/cldr/tags/latest/common/bcp47/calendar.xml>>
> .
> >
> > Is there a preferred format for these references?  We're happy to do
> whatever is most likely to remain stable!
> >
> > Thanks,
> >
> > Bron.
> >
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com--
> Sedate mailing list
> Sedate@ietf.org
> https://www.ietf.org/mailman/listinfo/sedate
>