W3C home > Mailing lists > Public > www-international@w3.org > October to December 2021

BCP 47 link (was: Re: [minutes] Internationalization telecon 2021-11-18)

From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
Date: Mon, 22 Nov 2021 15:01:56 +0900
Message-ID: <a8e6a954-f2d6-7536-ac7c-87ef32a8f0da@it.aoyama.ac.jp>
To: r12a <ishida@w3.org>, www-international@w3.org
On 2021-11-19 01:26, r12a wrote:
> https://www.w3.org/2021/11/18-i18n-minutes.html

> – DRAFT –
>             Internationalization Working Group Teleconference
> 
> 18 November 2021

>    Info Share
> 
>     <xfq> [17]https://github.com/w3c/i18n-drafts/issues/321
> 
>       [17] https://github.com/w3c/i18n-drafts/issues/321
> 
>     <xfq> [18]https://github.com/tobie/specref/issues/688
> 
>       [18] https://github.com/tobie/specref/issues/688
> 
>     xfq: looks like BCP47 URL has been moved and broken many links.
>     Has made PRs for our articles.

Yes, a long time ago, we thought that the tools links (e.g.
https://tools.ietf.org/html/rfc3987) were a good compromise between the 
raw ascii RFC without links and a completely differently looking 
hypertext version, and also were located at the IETF, so they should be 
safe.

The IETF has decided to over time get rid of the tools site, and to 
redirect these links to the datatracker (e.g. 
https://datatracker.ietf.org/doc/html/rfc3987). However, probably 
because they didn't have BCPs in the datatracker, they redirect those to 
rfc-editor (i.e. https://tools.ietf.org/html/bcp47 to 
https://www.rfc-editor.org/info/bcp47).

>     xfq: Filed an issue against techref regarding tools that broke
> 
>     addison: RFC editor link is not ideal

In what sense? I think the tools link showed both RFCs in sequence, 
maybe with an additional comment at the top (don't remember exactly, 
sorry). The page at https://www.rfc-editor.org/info/bcp47 doesn't show 
the actual text, only the abstracts and links, do you think that's the 
problem? Or that RFC 4647 appears before RFC 5646? That would need a 
one-time hack to fix.

>     jcK: RFC editor should be stable...
> 
>     xfq: Tools link to RFCs but they broke, is there an equivalent
>     for RFC editor

The tools links are redirected (at least for the time being).

>     ACTION: xfq: ping jck about link to BCP47
> 
>     <trackbot> Created ACTION-1096 - Ping jck about link to bcp47
>     [on Fuqiao Xue - due 2021-11-25].
> 
>     jcK: Contact me later to sort this out
> 
>     <xfq> See [19]https://github.com/w3c/i18n-drafts/pull/324
> 
>       [19] https://github.com/w3c/i18n-drafts/pull/324
> 
>     r12a: Found the link from ietf
> 
>     JcK: There are issues tools pointer has moved. It is all tied
>     up with the debate on what to do about RFC editor.

That's something that's barely related, and mostly long-term.

>     xfq: Data tracker link redirects to the RFC editor now.

Yes, https://datatracker.ietf.org/doc/html/bcp47 redirects to 
https://www.rfc-editor.org/info/bcp47. Not sure they had this before 
redirecting the tools links, but at least they got that far.

>     jcK: The URL will change
> 
>     Addison: Specref people need to fix links
> 
>     xfq: Many RFC links have been moved, but BCP is different

Regards,   Martin.
Received on Monday, 22 November 2021 06:02:16 UTC

This archive was generated by hypermail 2.4.0 : Monday, 22 November 2021 06:02:19 UTC