Re: [rfc-i] Guidance on linking added to the Web Portion of the Style Guide

Jean Mahoney <jmahoney@amsl.com> Thu, 22 February 2024 14:05 UTC

Return-Path: <jmahoney@amsl.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBA1BC14F616 for <rfc-interest@ietfa.amsl.com>; Thu, 22 Feb 2024 06:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 1661E7ooU31C for <rfc-interest@ietfa.amsl.com>; Thu, 22 Feb 2024 06:04:59 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 6FCC9C14F60C for <rfc-interest@rfc-editor.org>; Thu, 22 Feb 2024 06:04:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 45BB1424B432; Thu, 22 Feb 2024 06:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFP8wLSyxJEN; Thu, 22 Feb 2024 06:04:59 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 19EAA424B426; Thu, 22 Feb 2024 06:04:59 -0800 (PST)
Message-ID: <197233ab-2ec0-49fa-946e-d23c1e8701b1@amsl.com>
Date: Thu, 22 Feb 2024 08:04:58 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, RFC Interest <rfc-interest@rfc-editor.org>
References: <b00b1540-1c8c-4ef5-ba12-7949d444ad35@amsl.com> <2c83fa47-bf58-41d6-8af9-fd3e481608d1@it.aoyama.ac.jp>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <2c83fa47-bf58-41d6-8af9-fd3e481608d1@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/clnZBtCUlBf1sUouayAIioifwJs>
Subject: Re: [rfc-i] Guidance on linking added to the Web Portion of the Style Guide
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 14:05:03 -0000

Martin,

On 2/21/24 5:15 PM, Martin J. Dürst wrote:
> Hello Jean, others,
> 
> The Style Guide you cite says:
> 
>  >>>>
> An in-text citation may a) follow the subject for which it is being 
> cited as a silent pointer to the referenced document or b) be read as 
> part of the text.
> For example:
> 
> a) As part of the transition to IPv6, NAT64 [RFC6146] and DNS64 
> [RFC6147] technologies will be utilized by some access networks to 
> provide IPv4 connectivity for IPv6-only nodes [RFC6144].
> 
> or
> 
> b) Note that SAVI raises a number of important privacy considerations 
> that are discussed more fully in [RFC6959].
>  >>>>
> 
> I'm confused by the words "silent" and "read". Whereas the citation in 
> b) clearly cannot be silent, the citations in a) could be silent or 
> spoken/read. It's also not clear whether silent/read refer to screen 
> readers (accessibility) or to a general reading process (orally or just 
> mentally).

[JM] The RPC is working on clarifying this guidance. Thanks for calling 
out the issue.

Best regards,
Jean

> 
> Regards,   Martin.
> 
> 
> On 2024-02-21 23:37, Jean Mahoney wrote:
>> Hi all,
>>
>> The RPC has added guidance on the use of links in documents. Please 
>> see the Web Portion of the Style Guide at
>> <https://www.rfc-editor.org/styleguide/part2/#links>.
>>
>> Best regards,
>> Jean
>>
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest