[Rfc-markdown] <referencegroup>, was: [xml2rfc-dev] New xml2rfc release: v2.18.0

Julian Reschke <julian.reschke@gmx.de> Thu, 07 February 2019 20:56 UTC

Return-Path: <julian.reschke@gmx.de>
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 560DF129C6A; Thu, 7 Feb 2019 12:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vqc4E9-Uz5K3; Thu, 7 Feb 2019 12:56:27 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D044129A85; Thu, 7 Feb 2019 12:56:26 -0800 (PST)
Received: from [192.168.178.124] ([91.61.58.218]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M243n-1h7zcl3ggF-00u4KC; Thu, 07 Feb 2019 21:56:04 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1grUuZ-0001Xw-Ix@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e7b09ee3-511f-5db1-6273-0c6a40317752@gmx.de>
Date: Thu, 7 Feb 2019 21:56:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <E1grUuZ-0001Xw-Ix@durif.tools.ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:04puHcZ9henYAzgfEYewROd5KztJEd+Z3E72mHTs9DkZ2qcZ7Pj 5WqtMtjDgR90QqCNTXPyYn8TQlPNxC+ZQUCKF2hRbY+7AsEhyLNppWqwAZS5bFsk6us5aCe swGRzApZp+mPIEhBbZlHgd3Txuhrc8pzqLnefW20u7WSm/x71hYaEXk5rVS173O9ACtDhWP RdMczr9GQElxJ4unPityA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:XDUZKd9dv+k=:6NcXpkcq9BrsGvzWWxLaU+ zaaozD4KdKftVuWTwTqNZjTEKG+h+GyLFFos9MZTJuYpmPWWAKM6ubIzcz3eBovnGTxEL0L5g APoCjz6gcfwhPxb0JnGXeutScxk+0EMaAPAKIJainX2QCS0b0TmnSYDJqVrF+OBQIqWFxKKX1 w/Xx/7/QFBKI0ywpNnxELIq3mqBsjNgUetFQ98jKGAl03C08P6BXXlG03v4IRfqhwtmapZHjM zmZE8D9bK22r4X6TfYMHvF51mc51MIuP6HJMWI4I8h5SijZHHhCeF6hCv76B1p8rakNkvTYpo frfCYNNabvR1KwQPI2K74940KK/Q6CKUGG2KsnYWyVP9kgr3Ie+BEQ1Fya9t0iS8oYmqlioNL 0IByiAS/IoF/dupL6UySFoWEMEBx1E8v2gv9mgjJWn0a28i8vz2VaH+o5cjYftT+ndlChxWK1 ZkUU2rQ/7FCr4wlSp9Ad/3FYh6LPq9nrOhc+zUwF67HdgRGqXxNVdsMXqlqwlYS3M6hO0t1hE DSEI1w3/Rz09mhetAh/5IK4h+QMTh4sjges0P89Upne03ACE4lHsVu8pIve35f4FVfO47vYaG m21RD132ywb1dLgV+ToL13BICFUzhdZHk2n5lH/vEjAODfuqGytEn09BcoQXqfudQDKqN53Pd sy4naIaCKXCa11DYiBNXbqCKOfZ56xQBOYgfdlvAGBC89mx0vKs3Ecj2SbCHqrEwLhGp5D6qf xSVgGCrvkQHh18Ixy7c4G6BJAhGnGvIghOuLyYxPwdO7uuIc0E0lAckw2ju0raWlPGaqrZiea vpqK3ljgaBPQvERp9m9aGekV9VRjrIRu42jW1/WF2BJWadDr9+scZumiMMrxYkVPCPtW3246K OnAFs/mZpMnlMuZIPZSSwKKzEcgMVKN1nHwkXmF9UBCj1ua9nEm7dxo1hJHF1yrnsTXmyJNde tLLo8Uf0DBw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/XiEQpLqnZKj_b2hVwf4goOl7ZlA>
Subject: [Rfc-markdown] <referencegroup>, was: [xml2rfc-dev] New xml2rfc release: v2.18.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Feb 2019 20:56:29 -0000

On 06.02.2019 22:39, Henrik Levkowetz wrote:
> ...
>    * Adjusted the text rendering of reference annotations to match the html
>      rendering better.  Added support for <referencegroup> target rendering.
>      Suppressed rendering of target URLs for individual entries in a
>      referencegroup.
> ...

With that, I'm getting output such as:

>    [STD69]    Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
>               STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009.
> 
>               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
>               Domain Name Mapping", STD 69, RFC 5731,
>               DOI 10.17487/RFC5731, August 2009.
> 
>               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
>               Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
>               August 2009.
> 
>               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
>               Contact Mapping", STD 69, RFC 5733, DOI 10.17487/RFC5733,
>               August 2009.
> 
>               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
>               Transport over TCP", STD 69, RFC 5734,
>               DOI 10.17487/RFC5734, August 2009.

So the links to the RFCs are gone.

This matches slightly more what RFC 7322 says in 
<https://tools.ietf.org/html/rfc7322#section-4.8.6.3>:

>       [STDXXX]  Last name, First initial., Ed. (if applicable),
>                 "RFC Title", Sub-series number, RFC number, Date of
>                 publication.
> 
>                 Last name, First initial., Ed. (if applicable)
>                 and First initial. Last name, Ed. (if applicable),
>                 "RFC Title", Sub-series number, RFC number, Date of
>                 publication.
> 
>                 <http://www.rfc-editor.org/info/std#>

...but it still misses the link to the "aggregate" page.

Now doing this properly (without weird heuristics) requires a vocabulary 
change (see 
<https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/10>, 
raised over two years ago).

If we are in a hurry, and it seems we are, I would suggest to drop 
<referencegroup> for now instead of doing something that is known to be 
broken. And yes, I'm saying this after spending several hours over the 
previous weekend to get <referencegroup> support into rfc2629.xslt.

Best regards, Julian