Re: [Rfc-markdown] references in tables
Carsten Bormann <cabo@tzi.org> Sat, 17 September 2022 20:05 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C071C1522AF for <rfc-markdown@ietfa.amsl.com>; Sat, 17 Sep 2022 13:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 q44lAfAX4SKD for <rfc-markdown@ietfa.amsl.com>; Sat, 17 Sep 2022 13:05:18 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 921A5C1522A2 for <rfc-markdown@ietf.org>; Sat, 17 Sep 2022 13:05:17 -0700 (PDT)
Received: from [192.168.217.124] (p5089abf5.dip0.t-ipconnect.de [80.137.171.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4MVMP75NM7zDCcW; Sat, 17 Sep 2022 22:05:15 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_B0308C0C-3673-41E6-8458-AD782F6D8F33"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <473133.1663444651@dooku>
Date: Sat, 17 Sep 2022 22:05:15 +0200
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 685137914.784297-adc609376e3f42913fcb2423fc7bc1cf
Content-Transfer-Encoding: quoted-printable
Message-Id: <83DD423A-EABB-4BA4-9EC6-D3C1A6A7385A@tzi.org>
References: <473133.1663444651@dooku>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/XUau93oDfnXtZq5uF9hZg5mQbmo>
Subject: Re: [Rfc-markdown] references in tables
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Sep 2022 20:05:22 -0000
On 2022-09-17, at 21:57, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > Signed PGP part > > I have a document with a table of forward references. > It looks like this now: > > +------------------------+----------------------------+---------+ > | Trigger pledge- | /pledge-enrollment-request | Section | > | enrollment-request | | 5.5.1 | > | Returns PER | | | > > obviously, maintaining the literal "5.5.1" is a pain. > Trying to obvious to insert a reference: > > Operations and their corresponding URIs: > +------------------------+----------------------------+---------+ > | Operation |Operation path | Details | > +========================+============================+=========+ > | Trigger pledge-voucher-| /pledge-voucher-request | {{exchanges_uc2_1}} | > | request creation | | | > | Returns PVR | | | > +------------------------+----------------------------+---------+ > > doesn't work (not really surprising). Sure surprises me. https://raw.githubusercontent.com/cbor-wg/CBORbis/master/draft-ietf-cbor-7049bis.md#line-949:~:text=%7C%20Tag%20Number%20%7C%20Data,in%20RFC%207049%27%7D That worked well right into RFC 8949... > Is there some other way I could make this easier to manage? Send source. Grüße, Carsten
- [Rfc-markdown] references in tables Michael Richardson
- Re: [Rfc-markdown] references in tables Carsten Bormann
- Re: [Rfc-markdown] references in tables Carsten Bormann
- Re: [Rfc-markdown] references in tables Michael Richardson