Re: [rfc-i] Minor v3 question

Carsten Bormann <cabo@tzi.org> Tue, 21 January 2020 19:32 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 1A8EDF40710 for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 11:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GazvDZOAxf-A for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 11:32:00 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id 43802F4070F for <rfc-interest@rfc-editor.org>; Tue, 21 Jan 2020 11:32:00 -0800 (PST)
Received: from [192.168.217.119] (p548DC4D8.dip0.t-ipconnect.de [84.141.196.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 482JZZ6rwbz16HJ; Tue, 21 Jan 2020 20:32:06 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <44615ec6-5dfa-9750-6505-8b12c3d84231@joelhalpern.com>
Date: Tue, 21 Jan 2020 20:32:06 +0100
Cc: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 601327925.998316-06b26e3ab1b7e6d0a01608d1f44c3125
Content-Transfer-Encoding: quoted-printable
Message-Id: <900EBEC3-384D-4858-B115-BD19A604BED0@tzi.org>
References: <44615ec6-5dfa-9750-6505-8b12c3d84231@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Subject: Re: [rfc-i] Minor v3 question
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2020 19:32:04 -0000

On 2020-01-21, at 18:31, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> What is the v3 syntax for a reference to a URL?  (The specific case is an IESG statement I have been asked to reference by the AD.)

I also think that hasn’t changed.

But I also think eref is generally not useful for cases like this.
I’d do a full references entry with a target attribute for the URL.

Kramdown syntax (reference as {{IESG-Historic}}):
  IESG-Historic:
    target: https://ietf.org/about/groups/iesg/statements/designating-rfcs-historic-2014-07-20/
    title: IESG Statement on Designating RFCs as Historic
    date: 20 Jul 2014
    author:
      org: IESG

XML syntax (reference as <xref target="IESG-Historic"/>):
<reference anchor="IESG-Historic" target="https://ietf.org/about/groups/iesg/statements/designating-rfcs-historic-2014-07-20/">
  <front>
    <title>IESG Statement on Designating RFCs as Historic</title>
    <author >
      <organization>IESG</organization>
    </author>
    <date year="2014" month="July"/>
  </front>
</reference>

Rendering:
   [IESG-Historic]
              IESG, "IESG Statement on Designating RFCs as Historic",
              July 2014, <https://ietf.org/about/groups/iesg/statements/
              designating-rfcs-historic-2014-07-20/>.

(Tested with V2 because of some persisting brokenness in the V2-V3 converter, but this should work with V3, too, possibly with the full date.)

Grüße, Carsten