From nobody Fri Jun  7 00:00:32 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA46120164 for <xml2rfc-dev@ietfa.amsl.com>; Fri,  7 Jun 2019 00:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level: 
X-Spam-Status: No, score=-1.198 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 55edaqlhLpLA for <xml2rfc-dev@ietfa.amsl.com>; Fri,  7 Jun 2019 00:00:24 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 7C6B6120100 for <xml2rfc-dev@ietf.org>; Fri,  7 Jun 2019 00:00:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1559890819; bh=aWpcfrZmxSMBvZDB98FZF+ekiYZWJQ+R+DVcidFL5ec=; h=X-UI-Sender-Class:To:From:Subject:Date; b=WqHp1CHwl6XIN7+bH7WLutfJtQHctvO7PciR8K166StlOCAWoBelVwKK98SGHcW+A FUoirZ6lZr9d51DLFaKxdTjrLW0R1ERra7ORA9H6yJ/rNUalusRzhNiHi6pDp04bX4 PDyZODWcSsK9GYrHITadhbBbLG7zxQJWlqx5iWSM=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.6] ([178.166.122.247]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M1SLt-1ggcIc1csb-00tS2H; Fri, 07 Jun 2019 09:00:19 +0200
To: XML Developer List <xml2rfc-dev@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de>
Date: Fri, 7 Jun 2019 09:00:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:pO7x4jMvpoY+T+xEn3GFp3i+QLBMlyLEVWzS2DzJF8rtmazEmin XfBcUaT5AHkbqnoqWhnP7ypnj47zM/lwY2IONIxres00UvBcofpweJLcoE+651KX3bN6YD9 iVHFqbPoaoDrBQMndCkkpoNqCXxziVMoMYkWrVewfnqn8iMozQSrmKdcqZ6JtBfMfv4nIg/ MaR8pnYCUpmZnsW3vNGng==
X-UI-Out-Filterresults: notjunk:1;V03:K0:CaPSBsya+Bw=:E7N/qgzsn1gs3tMa2y5nK/ WvEgktWhDAXBv9ALB5cD2DwPKUXxw8oByt5b+ivvLGWgXvZ0IG+uAJVlKab6nvjfxqFj5xdzn Ac9b3lJGDL0oSgrapID9gtfbWX/U3w5+jI0Ylc8p4BvhoMha3i+2Oi9AMFbP6CTY/MKKgIAZS zaS4Drq9ba5WXhsUQeSRuMIGScttROUXcblD9ZyIYJw9K7V6L5+JsKaxI7nszoaGo9TFNzdp2 zE5plPKb47Dh3gz0BxkhiH1ROCZw+R+d2HcUHtY69y3EDYJ8bPgC7UVt8p1YbwYZNErIIyEkb aMvj6GifVfVoIvbJrvKDBB20OBtNVfS97NezCYRJwF5d5ErYGNR0lkCiakHeWmDMVl6xNLVMM ezTsaoRPknKLdL9EoKp/ThWYK43ChDpYJPZYD2gsmcctlJ/7auDmWVV5PtCDBs1TWD5PFl1MJ QxcfzVoAieSJOS8tz+BTozF35X0jeful1D71Hm4rfua7Nkb4RMvCUwiV8MrVINRf+GVvt/FqR dKHnIdas1vLhF931+7q9cUQrnpjsKnkB5xRQw/WA6KvQSe1XJaVVha9yu1SokN39vjJQEtrsl NU88XLv6cvZqy5vxRxw1otujVJi0ep6ilUXoOgr5+zQYRfJbZSxRFH3lxlPH0nsEXLxfHJvw0 9WU9KN4A8l10ld1hXSZn1U/I0yFUU5EyqF0O587QzBVoHsDi/egTWmRA36ws3DTp4SsPpqpQL Dtk5KPspoP7SdISTEoeEOjvIhYRLYTW8Unlk7nhoNcNTTLEnOujfAvHrMC2yyvceFiFKK2F5Q Ki9ix/zOkRS/XqI9lI/g0M6OGLPJuO6MJbu9RNKgC3tg9JeSAuCPDdm4MwIQ3mYQCIgUhhI3U IhhDg/6VXjZoHNCp8TUt6gm46KmQLChV+mFxIEUtWGiQc6BUk7I/bnjtY+YQOFA2suVkCXseg 2wbjni3TddDU3ZE6iiYppsGliu2bteYTRgb63n2GRANHgl+D7T0vyIqAebY+PrHDR7yuKpBMW ZA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/V2SHaVAZLxplyXMRtqCnUu4rwJA>
Subject: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 07:00:27 -0000

Hi there,

I just noticed
<https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.

This seems to contradict the style guide
(<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>)
and also doesn't seem to make any sense to me.

What was the reason for this change?

Best regards, Julian


From nobody Mon Jun 17 01:45:48 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4058120100 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 17 Jun 2019 01:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 x9ovpneCpfdK for <xml2rfc-dev@ietfa.amsl.com>; Mon, 17 Jun 2019 01:45:44 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 2DBAA12004E for <xml2rfc-dev@ietf.org>; Mon, 17 Jun 2019 01:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1560761136; bh=dLg0pBhEMDIlGA2H2CtpwfmC5o1ny3VoF3SHf1pGiYc=; h=X-UI-Sender-Class:Subject:From:To:References:Date:In-Reply-To; b=Q5c6fxY+gnAT61kRLiMnvrMDT6IqSAIHmxw95gWd9V+g6256q3ar7fIY9PdpI8tpf VzSkGbxq1OeAd5LuUQvJYcseoSFmu7s8135FAP1W/GR99fkcC3G/nPbgkEPw7W0LUY 5zTH5sy1krIscrVLcBSonyaglAjwHsFZMFgwdZO8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.54.125]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MkYXm-1iLWXB3sC6-00m6os; Mon, 17 Jun 2019 10:45:35 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: XML Developer List <xml2rfc-dev@ietf.org>
References: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de>
Message-ID: <9d6ebde3-af87-7874-a809-2306f5612fe2@gmx.de>
Date: Mon, 17 Jun 2019 10:45:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:/AqkL+bC7otfwCoLc90cVYUmWV3wRGAbFwhW5knvUyBxAeeciPP MEGRehhxgHRZyVONnFcey/rC/38J/goXG4E9hDK4M+Kdx1nnFcM+nGoPrcY1+OIBlyBSN9i k+x8zPpqLP96RBseUDJoH2Sh5LvtwaCk5AuhXpIeR4QXeIQPXkwdJST5a7Ni6pjNk5WqUrF wDIvyM7K1vfp4rNtBBFVg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:KPMihgDNDNw=:OQ+ymUYDRuGTc7jeuiCMzy PQYZWtIN0fXueS3HUEPoNuAN2L+aCyXEZIOm/YqVLaAiUcymj7f3RhGv1zP4nt0QlwAul0LXe Sfz6KEl6IQ61nPFvBWFAxXs1jYTXIzCgH3+uFwy02kVckQn8pIrKQCUvuKw7REW1zJMyqwkN/ qb80Zl9IZagqtZFo6aASEwiitPThqvuX6yEGkAkf1k1tIgbGGt2XiHXPecC/oizk6PjggnpN+ tLZNhaovgapy/kTXYJ2YuLAXsPOf2aUowRYB8AXy/JElybpuRKbBnkbEm6NbidZcRmDwmhLap 3kcIsfbvmWnb38mXIHx6OMLwDdWG3N2ln107Iv/5qHIQ1Ymq4fzJCy11D3Dc1O16yzewLjQi+ pHIJ7cwZlDY9blm1n+z0RA/Ydfc0sDB5zuHv1xAB7oyMPUatoo5S1/fCxGHh2hcnUCsThJuZ6 RVX8YBR6Y8f4YvCDlZiIoqH1M6xb5ULfYJHlM6BeOyMwNjFvC9qIZtT3z1hk3R9pKqXlkT6by RvpK2DtqVrq52E4kp49bgBsY1C82s58Kn0nS5qkm/GQeyPBSZMAVsoS3ba0rq26nhgx9YlpCp mVOOjeJCUd1S6Hk38x7iRj1c0f43avf4TsuQ1efRBsTt5oL5BktPPjZZJqPFR9F91Cv87HPVr 1/gl8eOA3MH94IgALoR6AtzR5wZ4fKdPiLzNApkYOY6FkvgR63Fr0cQG8HsfVRyCovx/M5e84 Y+oHmvVSTq9DxFpsFxorNVFjbKqLHqZV5UUGYK1uCb3r0i6/yjd+itsX34mZqXxkiSkugFMuP VsHKYXA19JKCqatQtNba8ATaAMCSa/BSjn2INx5jYwicQdhdnZOxI7fCneKHCrgbqej8JwhC+ Vp6VuYuVpruoqBDc/uejK/yOHLbFj106ywieEdNVMV8V4Ya/zdXflmkMVZoIBGMPkIc1RloUo TZvKOCPq4jGrZVqWhprWFxfUvoN4z7/OQnYnVyyDurrdhPsGE4bOxPhIoWyYZwTDMkxzhc7Tu 6g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/yL02J1uonXQLonpOcVjImI5MGbk>
Subject: Re: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2019 08:45:47 -0000

On 07.06.2019 09:00, Julian Reschke wrote:
> Hi there,
>
> I just noticed
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.
>
> This seems to contradict the style guide
> (<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>=
) and
> also doesn't seem to make any sense to me.
>
> What was the reason for this change?
>
> Best regards, Julian

Ping?

Best regards, Julian


From nobody Mon Jun 24 05:51:55 2019
Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20094120289 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 05:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 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] 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 KPQ-gE45DOIS for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 05:51:51 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A22712027E for <xml2rfc-dev@ietf.org>; Mon, 24 Jun 2019 05:51:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 09B321C1346; Mon, 24 Jun 2019 05:51:50 -0700 (PDT)
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 rOsinH8bYwxv; Mon, 24 Jun 2019 05:51:49 -0700 (PDT)
Received: from [10.119.9.50] (unknown [209.135.211.167]) by c8a.amsl.com (Postfix) with ESMTPSA id A6F081C1343; Mon, 24 Jun 2019 05:51:49 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Heather Flanagan <rse@rfc-editor.org>
In-Reply-To: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de>
Date: Mon, 24 Jun 2019 08:51:49 -0400
Cc: XML Developer List <xml2rfc-dev@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E04A36E-E9A6-495D-8237-196320BB7E26@rfc-editor.org>
References: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/jIo3kfvoa6hcYfKy1aTRFreQ_no>
Subject: Re: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 12:51:53 -0000

> On Jun 7, 2019, at 3:00 AM, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> Hi there,
>=20
> I just noticed
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.
>=20
> This seems to contradict the style guide
> =
(<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>)
> and also doesn't seem to make any sense to me.
>=20
> What was the reason for this change?
>=20
> Best regards, Julian
>=20

Sorry for the delay!

The subseries collections don=E2=80=99t have DOIs; only individual RFCs =
do. If the reference is to a subseries set, then no DOI should be =
included.

-Heather=


From nobody Mon Jun 24 06:09:35 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB224120155 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:09:33 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 JtByfmyl__Rd for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:09:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 4C48F120157 for <xml2rfc-dev@ietf.org>; Mon, 24 Jun 2019 06:09:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1561381768; bh=9GP9cHOvaV839zeYueP7k/+aGPeoNXNMOfjaBLGXLrQ=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=iI+9V1UP1eE2+eryyYXL/twAG9pvFhx1mKF/9Sc3boQUxdhRTXiiFiyuaZu5Thn8g ztJNoion0vesQF6O7tga2yghgiTQ5u1zvXWDBSUXBvk52xr+IGFMZKzEv0qrkfBy9d RQFlZqvHPjNOda61GDSct54mVIyCrsrzhr6C5ujw=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MLR30-1hfwgk2i5i-000Ys1; Mon, 24 Jun 2019 15:09:28 +0200
To: Heather Flanagan <rse@rfc-editor.org>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
References: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de> <6E04A36E-E9A6-495D-8237-196320BB7E26@rfc-editor.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <d9f46a41-16f8-d10b-9769-611bc75d6d54@gmx.de>
Date: Mon, 24 Jun 2019 15:09:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <6E04A36E-E9A6-495D-8237-196320BB7E26@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:diSepNPAjHyAiT0OuBjtwRV4dRPVpX+PzQaPurhJoLJV2pVYir8 0l/Gh6RtTFtPVA2dKg+FOeUCXWQAo4hiY553gWSo9orlgkBHBHuc8oR5Cr7ZjFWXpq3RZKg h3UjwwAlC2V5socaLHphffQHDyJBjP5I9gZeRgL1oVli9b0tE9XZ9mcyIHVYll+L/UZHzUF Ji+hdTr07Z02rtd8u6oGw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:9DYa66hNuYU=:OWsyimi6GZ8OvAVjWTJSeD UQjrbnqdojG68JtQrAeORfQ98xyWnZ9WzFi96xEQQJN/tRtHlfdZbG7J0bxxbcg9g2A+goWKD v0o6HDQrhF9iKP9i1q4OOkXBFwgQ6TONjTCtbyC5+ODUWmmmulbBvmxDk6G23/gkb3DU7rP6v 3Wmh+7DtAUHHPt/fCDR9lJw2jSLH5goW5kTF/nJn172ogtl0420hHqbRrcP2CGlFeVvWK4nYa 4WpPY45FmwpHJg9R7JYsGzKmVcvMwp8sc0KjWluBU7mbKqRQmhD894DvdyXz6Kz2y1O/Np05W rfUVBzfuXFdXqggLGb4PuCdWl3m8yMFypUoyDx0AW8wfE+aFzug2b/CsabsuDi0YJFCkxQhb9 AgfOgGY4m8txtwvfK8vJ+HasWbAs/B1Y3S7O4HwfbrroR77fWg4bRY14S4THT+btgYAuuqLzh EJ2z3sERmpY6/pNZ77FLJofXd1EOgK9DFotoZ25f6o/9d/mO4bz5ATvUeTEVl/64L9aavCCyf nXwIYn4gDuGKseBQR+oGMMNIAH40VPVOZjHwvQ6Cx8h6Cup+jurSJRe5ukDW8ZBSmP5JJtaQ3 DxwW62cxcE7J8oYmdehyZHQpRnIk/+M12ViqkOTO0M92pVzdtMOqm8vO60DQdEcteuxrsWc/2 BoHFDew5so0wSTysnE6I/CSkuX38vLbyLCe7INCg5ExT2mjEBCVrh7/SC0s0zpoWJdjWdYhV6 cu1Nog47uHp95kRV6PoGT+fz1CG4tnclQElPW187j64Th7jlSc4sCOXepPPr4c8l9RIbimcC3 Rl62vesjFm40fqz6mLpknRvTrzkhGKci4pNHHr45iZxX3/tK7mCLMpdmLAREUCEWj29bYVxwQ +fTMR3xbM+cXP6iliOdQZ4jadhRRtM+j3tgFcl/3qodZ+N2SzjEQITBykfhWNj1BhsPb5UsXZ gksv/D9fdet/kZR+HmhzlGzc5URpMDtYu3pV0dTtw95N6d+v0I5X7
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/PiKlZqgle5RWIFVbPlhTfj4_qbI>
Subject: Re: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 13:09:34 -0000

On 24.06.2019 14:51, Heather Flanagan wrote:
>
>
>> On Jun 7, 2019, at 3:00 AM, Julian Reschke <julian.reschke@gmx.de> wrot=
e:
>>
>> Hi there,
>>
>> I just noticed
>> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.
>>
>> This seems to contradict the style guide
>> (<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3=
>)
>> and also doesn't seem to make any sense to me.
>>
>> What was the reason for this change?
>>
>> Best regards, Julian
>>
>
> Sorry for the delay!
>
> The subseries collections don=E2=80=99t have DOIs; only individual RFCs =
do. If the reference is to a subseries set, then no DOI should be included=
.
>
> -Heather

I understand that the *subseries* doesn't have a DOI.

But let's consider
<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>:

>    For an STD or BCP that contains two or more RFCs:
>
>    [STDXXX]  Last name, First initial., Ed. (if applicable), "RFC
>    Title", Stream, Sub-series number, RFC number, RFC DOI, Date of
>    publication.
>
>             Last name, First initial., Ed. (if applicable)
>             and First initial. Last name, Ed. (if applicable),
>             "RFC Title", Stream, Sub-series number, RFC number, RFC DOI,
>             Date of publication.
>
>             <https://www.rfc-editor.org/info/std#>

I assume this was meant to display as:

>    For an STD or BCP that contains two or more RFCs:
>
>    [STDXXX]  Last name, First initial., Ed. (if applicable), "RFC
>              Title", Stream, Sub-series number, RFC number, RFC DOI, Dat=
e of
>              publication.
>
>              Last name, First initial., Ed. (if applicable)
>              and First initial. Last name, Ed. (if applicable),
>              "RFC Title", Stream, Sub-series number, RFC number, RFC DOI=
,
>              Date of publication.
>
>              <https://www.rfc-editor.org/info/std#>

So where this says "RFC DOI" it refers to the DOI of the RFC that is
part of the subseries, so this should stay, right?

Best regards, Julian


From nobody Mon Jun 24 06:13:08 2019
Return-Path: <rse@rfc-editor.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 851F6120289 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 5pJo7UQ0nkCS for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:13:05 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2680A120155 for <xml2rfc-dev@ietf.org>; Mon, 24 Jun 2019 06:13:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A2DDE1C1346; Mon, 24 Jun 2019 06:13:03 -0700 (PDT)
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 iVl05eGj9dK5; Mon, 24 Jun 2019 06:13:03 -0700 (PDT)
Received: from [10.119.9.50] (unknown [209.135.211.167]) by c8a.amsl.com (Postfix) with ESMTPSA id 20DA51C1343; Mon, 24 Jun 2019 06:13:03 -0700 (PDT)
From: Heather Flanagan <rse@rfc-editor.org>
Message-Id: <64D00A00-89F3-4219-8CDD-5823FD39B792@rfc-editor.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CB992FF7-3C85-45DD-B7E9-11BDCB6C0368"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 24 Jun 2019 09:13:02 -0400
In-Reply-To: <d9f46a41-16f8-d10b-9769-611bc75d6d54@gmx.de>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
To: Julian Reschke <julian.reschke@gmx.de>
References: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de> <6E04A36E-E9A6-495D-8237-196320BB7E26@rfc-editor.org> <d9f46a41-16f8-d10b-9769-611bc75d6d54@gmx.de>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/LzxBfAjh3-ziyqqZv0wLHoGSQpg>
Subject: Re: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 13:13:06 -0000

--Apple-Mail=_CB992FF7-3C85-45DD-B7E9-11BDCB6C0368
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jun 24, 2019, at 9:09 AM, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>=20
> On 24.06.2019 14:51, Heather Flanagan wrote:
>>=20
>>=20
>>> On Jun 7, 2019, at 3:00 AM, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>>>=20
>>> Hi there,
>>>=20
>>> I just noticed
>>> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.
>>>=20
>>> This seems to contradict the style guide
>>> =
(<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>)
>>> and also doesn't seem to make any sense to me.
>>>=20
>>> What was the reason for this change?
>>>=20
>>> Best regards, Julian
>>>=20
>>=20
>> Sorry for the delay!
>>=20
>> The subseries collections don=E2=80=99t have DOIs; only individual =
RFCs do. If the reference is to a subseries set, then no DOI should be =
included.
>>=20
>> -Heather
>=20
> I understand that the *subseries* doesn't have a DOI.
>=20
> But let's consider
> <https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3 =
<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>>:
>=20
>>   For an STD or BCP that contains two or more RFCs:
>>=20
>>   [STDXXX]  Last name, First initial., Ed. (if applicable), "RFC
>>   Title", Stream, Sub-series number, RFC number, RFC DOI, Date of
>>   publication.
>>=20
>>            Last name, First initial., Ed. (if applicable)
>>            and First initial. Last name, Ed. (if applicable),
>>            "RFC Title", Stream, Sub-series number, RFC number, RFC =
DOI,
>>            Date of publication.
>>=20
>>            <https://www.rfc-editor.org/info/std# =
<https://www.rfc-editor.org/info/std#>>
>=20
> I assume this was meant to display as:
>=20
>>   For an STD or BCP that contains two or more RFCs:
>>=20
>>   [STDXXX]  Last name, First initial., Ed. (if applicable), "RFC
>>             Title", Stream, Sub-series number, RFC number, RFC DOI, =
Date of
>>             publication.
>>=20
>>             Last name, First initial., Ed. (if applicable)
>>             and First initial. Last name, Ed. (if applicable),
>>             "RFC Title", Stream, Sub-series number, RFC number, RFC =
DOI,
>>             Date of publication.
>>=20
>>             <https://www.rfc-editor.org/info/std# =
<https://www.rfc-editor.org/info/std#>>
>=20
> So where this says "RFC DOI" it refers to the DOI of the RFC that is
> part of the subseries, so this should stay, right?
>=20
>=20

I think that is more a mistake in the style guide more than the tool.

-Heather


--Apple-Mail=_CB992FF7-3C85-45DD-B7E9-11BDCB6C0368
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jun 24, 2019, at 9:09 AM, Julian Reschke &lt;<a =
href=3D"mailto:julian.reschke@gmx.de" =
class=3D"">julian.reschke@gmx.de</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">On 24.06.2019 14:51, Heather =
Flanagan wrote:</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On Jun 7, 2019, at 3:00 =
AM, Julian Reschke &lt;<a href=3D"mailto:julian.reschke@gmx.de" =
class=3D"">julian.reschke@gmx.de</a>&gt; wrote:<br class=3D""><br =
class=3D"">Hi there,<br class=3D""><br class=3D"">I just noticed<br =
class=3D"">&lt;<a =
href=3D"https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130" =
class=3D"">https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130</=
a>&gt;.<br class=3D""><br class=3D"">This seems to contradict the style =
guide<br class=3D"">(&lt;<a =
href=3D"https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.=
6.3" =
class=3D"">https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4=
.8.6.3</a>&gt;)<br class=3D"">and also doesn't seem to make any sense to =
me.<br class=3D""><br class=3D"">What was the reason for this change?<br =
class=3D""><br class=3D"">Best regards, Julian<br class=3D""><br =
class=3D""></blockquote><br class=3D"">Sorry for the delay!<br =
class=3D""><br class=3D"">The subseries collections don=E2=80=99t have =
DOIs; only individual RFCs do. If the reference is to a subseries set, =
then no DOI should be included.<br class=3D""><br class=3D"">-Heather<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I understand that the *subseries* doesn't have a =
DOI.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">But let's =
consider</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">&lt;</span><a =
href=3D"https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.=
6.3" style=3D"font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4=
.8.6.3</a><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">&gt;:</span><br=
 style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D"">&nbsp;&nbsp;For an STD or BCP that contains two or more =
RFCs:<br class=3D""><br class=3D"">&nbsp;&nbsp;[STDXXX] &nbsp;Last name, =
First initial., Ed. (if applicable), "RFC<br =
class=3D"">&nbsp;&nbsp;Title", Stream, Sub-series number, RFC number, =
RFC DOI, Date of<br class=3D"">&nbsp;&nbsp;publication.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;Last name, First initial., Ed. (if applicable)<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;and First initial. Last name, Ed. (if applicable),<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;"RFC Title", Stream, Sub-series number, RFC number, RFC DOI,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;Date of publication.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&lt;<a href=3D"https://www.rfc-editor.org/info/std#" =
class=3D"">https://www.rfc-editor.org/info/std#</a>&gt;<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">I assume this was meant to display as:</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D"">&nbsp;&nbsp;For an STD or BCP that contains two or more =
RFCs:<br class=3D""><br class=3D"">&nbsp;&nbsp;[STDXXX] &nbsp;Last name, =
First initial., Ed. (if applicable), "RFC<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Title", Stream, Sub-series number, RFC number, RFC DOI, Date =
of<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;publication.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Last name, First initial., Ed. (if applicable)<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;and First initial. Last name, Ed. (if applicable),<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;"RFC Title", Stream, Sub-series number, RFC number, RFC DOI,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Date of publication.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&lt;<a href=3D"https://www.rfc-editor.org/info/std#" =
class=3D"">https://www.rfc-editor.org/info/std#</a>&gt;<br =
class=3D""></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">So where this says "RFC DOI" it refers to the DOI of the RFC =
that is</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">part of the =
subseries, so this should stay, right?</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div></blockquote><br =
class=3D""></div><div>I think that is more a mistake in the style guide =
more than the tool.</div><div><br class=3D""></div><div>-Heather</div><br =
class=3D""></body></html>=

--Apple-Mail=_CB992FF7-3C85-45DD-B7E9-11BDCB6C0368--


From nobody Mon Jun 24 06:24:08 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A66F120289 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:24:06 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 rxgEJujC_31l for <xml2rfc-dev@ietfa.amsl.com>; Mon, 24 Jun 2019 06:24:04 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 093C212010C for <xml2rfc-dev@ietf.org>; Mon, 24 Jun 2019 06:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1561382639; bh=FMpqSJPDFMwr/LsXwj0m8Y3zUNsblnJ+b1ciI1tbQ14=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=kim+96EyiIP/OApFZ12+GuhoqOA9Kbn16rwl4OHkkIYvXJJg2xW3cQmU/gteT3F0F RgvCZVoGL3Agbs7jD43XQpgrf5LmP13BUTrSkpCKChjPf/BX+Z1J23Y2ERpAPIkiEk cVArvxdQhcxXRUwYnOV3VFwZyXHjWHN4nXUsmrJk=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LtVLE-1ifv7T0R1w-010wxd; Mon, 24 Jun 2019 15:23:59 +0200
To: Heather Flanagan <rse@rfc-editor.org>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
References: <457b65f3-3950-174b-9e51-aaf7dd0fe827@gmx.de> <6E04A36E-E9A6-495D-8237-196320BB7E26@rfc-editor.org> <d9f46a41-16f8-d10b-9769-611bc75d6d54@gmx.de> <64D00A00-89F3-4219-8CDD-5823FD39B792@rfc-editor.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ae4c4185-34c5-f336-1cdc-b17827c60bf4@gmx.de>
Date: Mon, 24 Jun 2019 15:23:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <64D00A00-89F3-4219-8CDD-5823FD39B792@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:V0q3f5ja4rY1hJcKXssnLEe2VUVKd3WuxnJ8/dLe9bA8W5vMHWs 54Y+7fBBez3iU1jTcZmYPUWBrE7WfTGyADDS5nvlCGrJvGGNW7tFqzHRRQr03cFALg6HBMQ nJ5JXqc8NV4PD4pxgkL8pxoy6cuos4oa7X5nAOQ1GMMM4tWe1ePy5o22gftlE+7qu4Blw1m 0/4SKwIsAjfFUS3NiNBJA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:F3T7l45QCVk=:frF4BGzHgMy/g3buqV1DdP hwN7+M9ax9U+d2/WOr6dhNiBIEqy7ANI6x1/6ekzThnkn4aof2CReeKw3MgVdftCm2Z1F4OtE sovlrTGYJBP6rBsHxZQXtVTh67UR6JZq9+SoO5tCvapdhPzz2eLtiqVYTnjVIF21ueicqkJaD KY4oYn33xxlzatlWBm+FJlxR5MK/j1fQ5MzXtLuJf/sTyWo1aM1ESOd6K/104A03RHt7upX6t Dr5d8FuxO7azMgcb+mZ9JN3PX6dmdiBoVo9KKi1b/dL1q5ovmxDaIyNGYunq5K2kx0jm2pA+T go8ZBy16HA7lxvOf9CZntDLWMzMNFpicsIdB6qOOd6XQLotcscajJkwfNcD95qnZmG3wu+7mS UMRyPHx6DT9lRytBAqEZc+F9sH7po890DN52dsrY8THZ5RYfaLzjipKWOL7bEh6lJGUz3uDDG o/oJXV4o/L31cWSizr9MQ6XP7l4jY2sPuWsA5bdJ4JaB6Qi4/sJPdNEBh25Dtu/gW3FCVGN4J 5mnN2g6kH76IpQKXDW0UmCe3o9bQjQY7lDw01VaIvkhdIPkzhZ8xR1Lr/6JKInU27NoIRtjC7 gLad/lqetkBBUFQmD1g4slRXxFTahJTXoLRYl8wUtafBELnRRFAU5a89DXKp5rjhtDXhFMwXB hQeVF6T3lTGSdfKLpFYCTMbcWZ1GBvaqZuc6CDrryAQDuZ35ZJck2Kg7FEtYpLNjNsMTiJ6az QupOPwPhT2enQ7zMXo0Vy6LKvxvh2MKDLUQCc+gWTzZVyzFQjkQT++zSqggtTYSHiAC+eVn1t QAmVRKFdAT1X/42cFz6x5tGSEr4bYWiRAsQHcmr1D7eEVoYkL3QA0KblArFvQFRJ+w8er9mJl Lk/IMDdcu7WGmS4Nh58o94cZQ+gRNVqxer1YiWU5bJVj+XdWNjaLBt5ugK5NNI5FTKzrC8LVy lwKYZloXAKnn/BAYcZMMKgoS97aZye486w9NZenY4KkbpzMDyS71594qfglXWe5hfYMttEyR1 tKYre8WVNLJ711V+og/36inwKutcwC9wq7dEu7gt2HqGK/e1kIZ8jEGJVy0XoKBf0ZFueBJ6m Ik6qCUn8PejsAjTQ/uXdzy4M0jb6YU5tJBt
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/QVp_ywP42sg2FigD7LbhJFHwFOM>
Subject: Re: [xml2rfc-dev] DOIs in <reference> inside <referencegroup>
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2019 13:24:07 -0000

On 24.06.2019 15:13, Heather Flanagan wrote:
>
>
>> On Jun 24, 2019, at 9:09 AM, Julian Reschke <julian.reschke@gmx.de
>> <mailto:julian.reschke@gmx.de>> wrote:
>>
>> On 24.06.2019 14:51, Heather Flanagan wrote:
>>>
>>>
>>>> On Jun 7, 2019, at 3:00 AM, Julian Reschke <julian.reschke@gmx.de
>>>> <mailto:julian.reschke@gmx.de>> wrote:
>>>>
>>>> Hi there,
>>>>
>>>> I just noticed
>>>> <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3130>.
>>>>
>>>> This seems to contradict the style guide
>>>> (<https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6=
.3>)
>>>> and also doesn't seem to make any sense to me.
>>>>
>>>> What was the reason for this change?
>>>>
>>>> Best regards, Julian
>>>>
>>>
>>> Sorry for the delay!
>>>
>>> The subseries collections don=E2=80=99t have DOIs; only individual RFC=
s do.
>>> If the reference is to a subseries set, then no DOI should be included=
.
>>>
>>> -Heather
>>
>> I understand that the *subseries* doesn't have a DOI.
>>
>> But let's consider
>> <https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.3>=
:
>>
>>> =C2=A0=C2=A0For an STD or BCP that contains two or more RFCs:
>>>
>>> =C2=A0=C2=A0[STDXXX] =C2=A0Last name, First initial., Ed. (if applicab=
le), "RFC
>>> =C2=A0=C2=A0Title", Stream, Sub-series number, RFC number, RFC DOI, Da=
te of
>>> =C2=A0=C2=A0publication.
>>>
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Last=
 name, First initial., Ed. (if applicable)
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0and =
First initial. Last name, Ed. (if applicable),
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0"RFC=
 Title", Stream, Sub-series number, RFC number, RFC DOI,
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Date=
 of publication.
>>>
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<htt=
ps://www.rfc-editor.org/info/std#>
>>
>> I assume this was meant to display as:
>>
>>> =C2=A0=C2=A0For an STD or BCP that contains two or more RFCs:
>>>
>>> =C2=A0=C2=A0[STDXXX] =C2=A0Last name, First initial., Ed. (if applicab=
le), "RFC
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0Title", Stream, Sub-series number, RFC number, RFC DOI,
>>> Date of
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0publication.
>>>
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0Last name, First initial., Ed. (if applicable)
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0and First initial. Last name, Ed. (if applicable),
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0"RFC Title", Stream, Sub-series number, RFC number, RFC DOI,
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0Date of publication.
>>>
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0<https://www.rfc-editor.org/info/std#>
>>
>> So where this says "RFC DOI" it refers to the DOI of the RFC that is
>> part of the subseries, so this should stay, right?
>>
>>
>
> I think that is more a mistake in the style guide more than the tool.

OK, confusion growing... :-)

Please have a look at
<https://greenbytes.de/tech/webdav/referencegroup-test.html#rfc.section.2>=
:

> 2. Test References
>
> [STD68]
>     Crocker, D., Ed. and P. Overell, =E2=80=9CAugmented BNF for Syntax S=
pecifications: ABNF=E2=80=9D, STD 68, RFC 5234, DOI 10.17487/RFC5234, Janu=
ary 2008.
>     <https://www.rfc-editor.org/info/std68>
> [STD69]
>     Hollenbeck, S., =E2=80=9CExtensible Provisioning Protocol (EPP)=E2=
=80=9D, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009.
>     Hollenbeck, S., =E2=80=9CExtensible Provisioning Protocol (EPP) Doma=
in Name Mapping=E2=80=9D, STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2=
009.
>     Hollenbeck, S., =E2=80=9CExtensible Provisioning Protocol (EPP) Host=
 Mapping=E2=80=9D, STD 69, RFC 5732, DOI 10.17487/RFC5732, August 2009.
>     Hollenbeck, S., =E2=80=9CExtensible Provisioning Protocol (EPP) Cont=
act Mapping=E2=80=9D, STD 69, RFC 5733, DOI 10.17487/RFC5733, August 2009.
>     Hollenbeck, S., =E2=80=9CExtensible Provisioning Protocol (EPP) Tran=
sport over TCP=E2=80=9D, STD 69, RFC 5734, DOI 10.17487/RFC5734, August 20=
09.
>     <https://www.rfc-editor.org/info/std69>

Are these formatted as intended or not?


Best regards, Julian


From nobody Thu Jun 27 04:33:51 2019
Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC88A1200B8; Thu, 27 Jun 2019 04:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, SPF_HELO_NONE=0.001, 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 2Ont6DoOY0DK; Thu, 27 Jun 2019 04:33:34 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84C112004A; Thu, 27 Jun 2019 04:33:34 -0700 (PDT)
Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1hgSek-0004w5-76; Thu, 27 Jun 2019 04:33:34 -0700
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
Message-Id: <E1hgSek-0004w5-76@durif.tools.ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 27 Jun 2019 04:33:34 -0700
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/2JpxZoxyst6qDu3GhxneV14Atos>
Subject: [xml2rfc-dev] New xml2rfc release: v2.23.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 11:33:37 -0000

Hi,

This is an automatic notification about a new xml2rfc release, 
v2.23.0, generated when running the mkrelease script.

Release notes:

xml2rfc (2.23.0) ietf; urgency=medium

  This release adds v2v3 support for conversion of v2 code with both text and
  external image sources to v3 <artset> format, and provides improved cache
  handling.  It also contains a long list of bugfixes.  Here is an excerpt
  from the commit log:

  * Fixed an issue where cache clearing did not consider custom cache 
    locations.

  * Added retry on connection error for external includes.  This fixes an
    issue which has appearing more often recently, where the first connection
    to fetch a reference file has failed to provide the right redirect.

  * Added inclusion of metadata.js in the html renderer, for future handling
    of dynamic metadata (updated-by and obsoleted-by information, for
    instance).  Added a default instance of the metadata javascript file to
    the distribution, and added an command-line option to specify an
    alternative version of the javascript metadata script.

  * Added <script> to the list of elements treated as blocks for HTML output
    formatting purposes.

  * Show 'US' as "United States of America" (official name rather than short 
    name according to ISO 3166-1)

  * Changed the default RFC base URL in run.py, and the extension used in 
    html.py.

  * Added code to the v2v3 converter to create an <artset> for legacy 
    artwork with both a 'src' attribute and text content.

  * Changed <reference> rendering when part of a <referencegroup> to not 
    include the DOI.

  * Fixed a crash that could occur during index building with multiple levels
    of <references>.

  * Tweaked the text format <artwork> placeholder (when no text format 
    artwork is present) to look at both 'src' and 'originalSrc' for an URL
    for alternative artwork.

  * Changed the handling of pilcrow links at end of paragraphs and similar 
    to follow immediately after the content, without wrappable space, to avoid 
    the appearence of having double blandk lines when the pilcrow would be 
    wrapped to sit by itself on a line.

  * Added a HTML div to hold artset anchor, fixing an issue where artset
    anchors would not always be present.

  * Refined the preptool warnings regarding artset/artwork anchor handling.

  * Eliminated toc update work when tocInclude is false.

  * Only apply validation of cache entries as references if they are 
    <reference> entries.

  * Refined the reference URL cache handling for URLs with query arguments, 
    to avoid cache collisions.

  * Eliminated an incorrect check for page break after section header at end
    of document.  Fixes issue #409.

  * Handled authors without address elements for v3 text.  Fixes issue #408.

  * Dealt better with <workgroup> without content.

  * Changed the schema to require at least one instance of <artwork> within 
    <artset>.  Fixes issue #405.

  * Added a default rendering (code point number) for code points without 
    unicode code point names.  Fixes issues #401 and #402.

 -- Henrik Levkowetz <henrik@levkowetz.com>  27 Jun 2019 04:31:34 -0700

The preferred way to install xml2rfc is by doing 'pip install xml2rfc',
and 'pip install --upgrade xml2rfc' to upgrade.  If there are system-
installed python modules which pip will not upgrade, you may have to
use 'pip install --upgrade --no-deps xml2rfc' and install dependencies
manually.

The new version is also available through SVN checkout, with
  'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.23.0'

Regards,

	Henrik
	(via the mkrelease script)