[Rfc-markdown] references in tables
Michael Richardson <mcr+ietf@sandelman.ca> Sat, 17 September 2022 19:57 UTC
Return-Path: <mcr@sandelman.ca>
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 E0CCEC14F733 for <rfc-markdown@ietfa.amsl.com>; Sat, 17 Sep 2022 12:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 XIpr0jMPwKP0 for <rfc-markdown@ietfa.amsl.com>; Sat, 17 Sep 2022 12:57:43 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 A1EE2C14F728 for <rfc-markdown@ietf.org>; Sat, 17 Sep 2022 12:57:43 -0700 (PDT)
Received: from dooku.sandelman.ca (dynamic-077-011-033-222.77.11.pool.telefonica.de [77.11.33.222]) by relay.sandelman.ca (Postfix) with ESMTPS id 483951F480 for <rfc-markdown@ietf.org>; Sat, 17 Sep 2022 19:57:40 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id EE7FF1A0FCB; Sat, 17 Sep 2022 21:57:31 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: rfc-markdown@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 17 Sep 2022 21:57:31 +0200
Message-ID: <473133.1663444651@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/CJuTWVtpResj-7CopPwAaSkADOk>
Subject: [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 19:57:45 -0000
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).
Is there some other way I could make this easier to manage?
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
- [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