From nobody Mon Jun 1 05:03:46 2020 Return-Path: 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 6E6FD3A0FC4; Mon, 1 Jun 2020 05:03:37 -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 PsyWJW_QN_jz; Mon, 1 Jun 2020 05:03:35 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFB0A3A0FC3; Mon, 1 Jun 2020 05:03:35 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:51654 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1jfjAE-0003VZ-Dt; Mon, 01 Jun 2020 05:03:35 -0700 To: Carsten Bormann References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org From: Henrik Levkowetz Message-ID: <109c4ce5-82a6-3651-69ae-8f9950484412@levkowetz.com> Date: Mon, 1 Jun 2020 14:03:26 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="H6TTk5CPno71P64K3scjGlnUt7ft9dC27" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, cabo@tzi.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [xml2rfc-dev] SVG broken (Re: New xml2rfc release: v2.45.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 12:03:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --H6TTk5CPno71P64K3scjGlnUt7ft9dC27 Content-Type: multipart/mixed; boundary="So4O8RiV1lPCGHV92pHLb4pqhfTTCJ88Q"; protected-headers="v1" From: Henrik Levkowetz To: Carsten Bormann Cc: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org Message-ID: <109c4ce5-82a6-3651-69ae-8f9950484412@levkowetz.com> Subject: Re: SVG broken (Re: [xml2rfc-dev] New xml2rfc release: v2.45.0) References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> In-Reply-To: --So4O8RiV1lPCGHV92pHLb4pqhfTTCJ88Q Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Carsten, On 2020-05-29 23:29, Carsten Bormann wrote: > On 2020-05-29, at 21:56, Carsten Bormann wrote: >>=20 >> I no longer get SVG through this version that has been =E2=80=9Crepair= ed=E2=80=9D by svgcheck -qra; the SVG processing now seems very picky. (= I haven=E2=80=99t updated since 2.39, so this might have happened earlier= =2E) >=20 > Well, OK, this is now SVG generated by ditaa instead of goat, and ditaa= seems to want to show of its knowledge of SVG some more. So that may no= t be a change in xml2rfc at all. My question is mostly still valid, thou= gh: >=20 >> Is svgcheck still intended to be the tool to be used with xml2rfc to m= ake SVG palatable to it? Is that being updated along with xml2rfc ...? In principle yes, but there has been no change in the acceptable SVG sche= ma, and thus no change in xml2rfc and svgcheck in this regard for a long time= now. Author of svgcheck is Jim Schaad, he may be able to say more about the expected usage of the tool. Henrik --So4O8RiV1lPCGHV92pHLb4pqhfTTCJ88Q-- --H6TTk5CPno71P64K3scjGlnUt7ft9dC27 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl7U7o4ACgkQTptXS4+7 FxoGZA//UWnfBxQNygK3LcEgPdHWNEyPimyrZJfPa5UJSqzpRtmhu6/I3lKeeaUg PkYehVkngGBKv+CP5ypmAjxry/X4frxAgCtqdxZSlMg64jXM9903zDdzTlPAFFxd YAXeem4oIutAnptlwaX2OdYp5SR4jEC4U1gtMgRzZiHJUBdgYmOdF+c00ske7TF2 CcncIzH0Bkg04gy4QrK+08nzB3xIY3CVqXNfiToFdGFGZYYI0hXePByIxuJwMduO AEvnpy6Fllcox6YL1UYBUTdCBLHlhPO5OI2fs0zgi6yFdOmoeyJZ8761zMA0ugkm EAftgizCkWTPwpLu5RRzi1yP0y1SB6gOquCbtojaVl2SQ9/MTbIIBeduXlydPg8J FXLWvUT0R5RyCtBmPriWMRFHmqO4kQlkNOxAxVM0++g4eEq04o/151cbTF1t0lTf vQybjdVsDrJLK9ctcXpyPHD/86+IwPwEcqOQYAYB7ThgyHz/bfwLIcJRXeRVO1Hh L/y7D0g9DU/t6UlKwfo/UkgqLUMc6/uO509XcElzrPzqvGrD+O9yrqdLk/Xw8V7M IHsM/Ze2c/W968AcmDVhRoeT2Di7L0AZ4Mx31lS1bduEv3XhmUiMSN3NJcZVMeJR rJ0K/UMXfn6FdCTPyLP/slgCVWyAZSeTys9QtchxGwQVcdslR30= =GDPO -----END PGP SIGNATURE----- --H6TTk5CPno71P64K3scjGlnUt7ft9dC27-- From nobody Mon Jun 1 07:22:59 2020 Return-Path: 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 7EFEF3A10BA; Mon, 1 Jun 2020 07:22:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 JR0yXMSiLS6W; Mon, 1 Jun 2020 07:22:46 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A33B63A10B9; Mon, 1 Jun 2020 07:22:44 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 49bHSf2P8Lzyqr; Mon, 1 Jun 2020 16:22:42 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <109c4ce5-82a6-3651-69ae-8f9950484412@levkowetz.com> Date: Mon, 1 Jun 2020 16:22:38 +0200 Cc: rfc-markdown@ietf.org, XML2RFC Interest Group , xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 612714158.577495-705881f09acac57eb92d290ee5a656cf Content-Transfer-Encoding: quoted-printable Message-Id: <3A04D45E-33C8-4965-A9AB-FF52909F29F9@tzi.org> References: <93E5295E-CE96-4121-B3F5-C04540D542FD@tzi.org> <109c4ce5-82a6-3651-69ae-8f9950484412@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc-dev] [Rfc-markdown] SVG broken (Re: New xml2rfc release: v2.45.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 14:22:49 -0000 Hi Henrik, >>> Is svgcheck still intended to be the tool to be used with xml2rfc to = make SVG palatable to it? Is that being updated along with xml2rfc ...? >=20 > In principle yes, but there has been no change in the acceptable SVG = schema, > and thus no change in xml2rfc and svgcheck in this regard for a long = time now. Thank you. So my summary of the current situation would be that there are a few = mismatches between the two, each of which could be limitations in either = svgcheck=E2=80=99s repair feature or in xml2rfc. > Author of svgcheck is Jim Schaad, he may be able to say more about the > expected usage of the tool. Right. So when I see some of these mismatches, I would need to consult = RFC 7996 and find out which of the two has a bug/limitation before I can = log this as an issue. Since this is on the XML2RFC lists, let me mention it would first of all = help if the error messages were more easy to process, e.g.: y2020-05-29svg.xml(645): Error: Invalid attribute stroke for element = text, at = /rfc/middle/section[2]/section[2]/artset[2]/artwork[1]/*/*[2]/*[7] y2020-05-29svg.xml(666): Error: Invalid attribute stroke for element = path, at = /rfc/middle/section[2]/section[2]/artset[3]/artwork[1]/*/*[2]/*[4] These do not lead me to what might the problem (in RFC 7996, stroke is = actually allowed both for text and path). It seems that these messages are about the attribute value instead, = which I can look up in the source line given; it would be more useful if = the attribute value were given, plus maybe some indication of what is = =E2=80=9Cinvalid=E2=80=9D about it. For instance, xml2rfc rightly does not seem to accept stroke=3D=E2=80=9Cno= ne=E2=80=9D, which is let through by svgcheck. Also, I had to replace some stroke=3D=E2=80=9C#000000=E2=80=9D by = stroke=3D=E2=80=9Cblack=E2=80=9D, which RFC7996 tells me should not have = been necessary, but I can=E2=80=99t see what the problem really was from = the above. Here are the fixes my code is currently applying: XPath.each(d.root, "//*[@shape-rendering]") { |x| = x.attributes["shape-rendering"] =3D nil } XPath.each(d.root, "//*[@text-rendering]") { |x| = x.attributes["text-rendering"] =3D nil } These should be allowed on the svg element, but apparently aren=E2=80=99t;= again, the error message does not tell me what=E2=80=99s going on: y2020-05-29svg.xml(606): Error: Invalid attribute shape-rendering for = element svg, at /rfc/middle/section[2]/section[2]/artset[1]/artwork[1]/* XPath.each(d.root, "//*[@stroke]") { |x| x.attributes["stroke"] =3D = svg_munch_color(x.attributes["stroke"], false) } XPath.each(d.root, "//*[@fill]") { |x| x.attributes["fill"] =3D = svg_munch_color(x.attributes["fill"], true) } svg_munch_color tries to map everything to =E2=80=9Cblack=E2=80=9D or = =E2=80=9Cwhite=E2=80=9D; RFC 7996 actually allows other values. This = code also gets rid of =E2=80=9Cnone=E2=80=9D-valued attributes = completely for stroke (but not for fill!), which seems to be an = oversight in svgcheck. Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Jun 2 08:09:06 2020 Return-Path: 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 624843A08E1; Tue, 2 Jun 2020 08:09:04 -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=unavailable 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 62VC9Gujg0S9; Tue, 2 Jun 2020 08:09:02 -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 60C303A08D4; Tue, 2 Jun 2020 08:09:02 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1jg8XD-0003Er-EO; Tue, 02 Jun 2020 08:08:59 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Tue, 02 Jun 2020 08:08:59 -0700 X-SA-Exim-Connect-IP: 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: Subject: [xml2rfc-dev] New xml2rfc release: v2.45.2 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 15:09:04 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.45.2, generated when running the mkrelease script. Release notes: xml2rfc (2.45.2) ietf; urgency=medium * Fixed the HTML styling of
    lists, which wasn't really compact. -- Henrik Levkowetz 02 Jun 2020 15:07:09 +0000 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.45.2' Regards, Henrik (via the mkrelease script) From nobody Fri Jun 5 04:14:28 2020 Return-Path: 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 50D323A1482 for ; Fri, 5 Jun 2020 04:14:27 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 isJ24-zcl49y for ; Fri, 5 Jun 2020 04:14:25 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABD13A147D for ; Fri, 5 Jun 2020 04:14:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591355663; bh=aJwAGbYWUg35Xb45CukdDdGFqIRQ2RmUOaNON7glbKU=; h=X-UI-Sender-Class:To:From:Subject:Date; b=E6w/wSPeoQ+IPnGmvKkRU59Vz1SyDIfhOaVnYXH99b45WjZIpI2rjiXepLZnYkKTO tr/ROUxRHmN9+uw37TE8olKPtFptw6TB9BIwKWxSWADcnGBOApI5DnaBfKnMqqwEkp xK56xyn6n61JyKBedfRusgvw9ARa7Mi3nU4QUqtY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.152.96]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N1Obh-1iwrHY2XIR-012nHV for ; Fri, 05 Jun 2020 13:14:23 +0200 To: xml2rfc-dev@ietf.org From: Julian Reschke Message-ID: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> Date: Fri, 5 Jun 2020 13:14:21 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 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:B2i8An7/5wNgPOfNBvwbhFw19zmyZZlPKff3gMD0kIkmg3lI70u YP0JGUHTn5xXN7fDzJd2ifu+C97/Goa7zD2r8oGymmxfKpm7uuHkH6ZTRBnxMfT+Fh2cAbo EINIDthMD+kIyfQOv+wEv0b30I3kRzDGRqgw0TbgcWwIMFmWd7TrsdeNc243sJ1HLVVOvMp GIVdwbhQ9N8L/YhvDTMfA== X-UI-Out-Filterresults: notjunk:1;V03:K0:UqIbmIMVI5U=:wFbYuR58d8BbLNsTGvHdL4 /Pi/80IM64yvZ24zLD1yS7TYXQX1BBZrcoMjNNF9LAuw+n6JFrai9j1DNeo3ZZ9LlBlmgKU8j FuJDs9PDFfpRRfXNr+GGxpDBWj2kU/p63MouycgSdE8Nt8Cn+/sdChwycnYICp9lL3Ulb26HM ZxWhpH+ELPGxHEoNW8x86vAoWB2C8uvtjLh40uw02FmzXyD9OC1AfuKOD9X4tJfaHkz0b1AeQ Aaf+puO07a45d23fI9FIBEdKNypLHuZmDIeNeGbm1x0MyrVILzik+N5ye/pFRkeV9Od1tTO0r 7v6NuTFZLIQk418dO184LkU1BwrY8Wkvt8bQZvzSm3lCqYv/YsPO9VEsJ/ihunMAtUGAsOxSy OrXqTI3xBiBMzHdaRpkRMHHRr0HXzq7Ok/Fb3DsrVXRblA9W8mgA9FwFQhkAMAdmuBfLEoqUj yaQ6uv1j4eg4TBdV6eKhPlWgn1jfrDCOBCoFHyuwB5D2ZTUBsJ0l3IpCELfgj6gvDW0vkNC+f 5X2eyQVmu/j5HzSwh2HuEr5Tr1/KsnOlRW3WIbb7ZsUg3NzF8E1Ya//qccvqAGuYHorbEw8mS nQ6yozNb1F3+ynrTGD2I18ZUShKnHxq9N2zrzeb8eAuJ7xJE/B6wAxeuf8aF89INNFWXTbjF2 /yD3UMv1/iC1ZS7ey6FwsNgKzpVzvFSF+vMh63SpOUhnulwYP0i2WNuPWVtU+BgYRBT7aatlT T6UcYGmtBXJpo6cG9DGlwJVUvkovoFEnAPFtEQVVIYnQcHhRrzgbgtkjYu4gfEMz50xAOYrqC YvVHNMBN/QUteLnX8b/LPk0L3dd/QJ/geB1l82wJCY6Ogu49829kb+BuyJbg2+zOQ4ircGUsh s6e2mNp7sVhM/bBkPVC4URGhaE5H8Lb1bJonyXUunC3w87KPWAxHYJW6vjCVssa9H0fB6TwCi tweGHN9p0/sM5fd6UkimT1+0wFHDZdVKmAB8J1BNj2t8VcfJyXwOOWAZwsFgPJm6FYZSRFoV5 RwJynm3EyFLu6vaRTNqilBOhWC759cBJStxiZqfEhTpmiFBcm5g5hDSp4wMP4shOTlJ07Px8P 6w7Z5NtLiYjJiSe8dyNDH12LVkY1+qxiwF2h7iJgzTyoDxGKGU1Vx9qjEcQ72pnT6Rj4AiMN7 Be/2AqIgg8jjts7hrqf+cD4/1sUp8ZumJgHyzMRGpROwLrc8DaFyXQvDhCFNB/AoR52GuPmCH 0nWgNApZfXo752Cea Archived-At: Subject: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 11:14:27 -0000 Hi there, I'd like to remind people over here that RFC 7991 (the V3 vocab spec) is under active development, see: https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis You can find an HTML version here: . Plain text diffs compared to the latest published draft are over here: . It would be nice to get some feedback about the issues we've closed far, and also to collect more feedback in new issues. Best regards, Julian PS: there's no similar activity (yet) on the other v3 specs, but it would be good to progress them as well. From nobody Fri Jun 5 05:41:35 2020 Return-Path: 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 C1EB93A0B08 for ; Fri, 5 Jun 2020 05:41:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 TCTQnn0A9yOO for ; Fri, 5 Jun 2020 05:41:29 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 819863A0B07 for ; Fri, 5 Jun 2020 05:41:29 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 49dj1y5NzzzyYN; Fri, 5 Jun 2020 14:41:26 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> Date: Fri, 5 Jun 2020 14:41:26 +0200 Cc: xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 613053686.29732-8a829f307bf1c58ccf1b71f3225a358a Content-Transfer-Encoding: quoted-printable Message-Id: <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 12:41:33 -0000 Hi Julian, what is the decision process (who are the WG chairs)? On 2020-06-05, at 13:14, Julian Reschke wrote: >=20 > Plain text diffs compared to the latest published draft are over here: > = . To enable starting to work on this, a diff from RFC 7991 itself would be = useful. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Jun 5 06:07:22 2020 Return-Path: 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 622103A0803 for ; Fri, 5 Jun 2020 06:07:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 KY_FGC-m_ayN for ; Fri, 5 Jun 2020 06:07:19 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 689A23A0801 for ; Fri, 5 Jun 2020 06:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591362428; bh=1QP5J/kKxoR+ZKc0Pv5JQDPwW8G+HDlmOYWt0197EsU=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=fmLyYSGOt4CyIDJuXqfO8I9KiL6X7Zv/mOVgo83Usg+OworKoeMkNQ4qHdY+qrzdP eoZiXuho8pimxUgd29rJChmBdDGdKZZCMRX8hqZW1DOb1Wu8FTWr9QX0898lbfWtzW eNdstUBn/RDxnQ6Tirc3QN3b6gFANZh9Z6XH5w4o= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.152.96]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mel7v-1j9Vnt1naH-00amSl; Fri, 05 Jun 2020 15:07:08 +0200 To: Carsten Bormann Cc: xml2rfc-dev@ietf.org References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> From: Julian Reschke Message-ID: <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> Date: Fri, 5 Jun 2020 15:07:06 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:7uwWrVPdrRN/J8bqVWD43eGTt+66OlrCqADXzzUuCiKAlX3FZzp 21G7l1nEpH5c9cruFRwplx8FdaTnTeIlI6sXyDBZpPWLAO78INmo8fIdVLaXFKAkdnHyw5u eydo22EoWgVbWKK1NCzM4yqfKeBQ4CfRHjs0QoAgxGs/rTMwd1zfxGBbpK/ybKYnVJtrxKZ g853fRY0LPCNvyGM7t2Jg== X-UI-Out-Filterresults: notjunk:1;V03:K0:+bUsqoJZoOU=:MEQQC3/p51v9BzVCWEosjO 9euvCADspLtAwof6GYaCbDsjyitiHtDktwdt64f/aFji1pFIXQq0u3VswJpnQrWEoUnj37lbM y2ojok2OdAFcCEU1IgQmD32McMvGKpZgRiLSbmTc9fthP3Y7xAL1WHsEDDAY3tAYC8qL98TSU f+Cj9HmXhMWGcnVgk+wNzFDyA8NdfwZ9dbeJoUBlTD3AsLXnZLNx7rVfbZLPtyfb+09Cj0+sq sBDsIHZOVuFbWmmZdikYjS2gLxNejK7bSYjpV+IKgUSRhGzmuWAiLF39fk0tYaKTgCBe3oQ9A cTSzKZKGzrQDP8uoIsIWBCSUsTxzUuVMXfJxTubsKh5kFqnku1R5GB2tiAzJEZ7nyqR6RtQqt cnLNnGqKEOXN1gcLGQ5ePfFvb7PDJN5brTg4gMxEMzA6UgqOOm6LLyP2P7yr+Rc7N+i0pdzPR skqeClOr3JmjuFtwQTJYqKoY976pDowxyMyE/oVKuVBp8x/aPHweaD2cMhedH0NIHi8qORBYO wJ5iY8Vj0uYcL+ITSZUXvEr5bI+1pM+CwxwRb7DOGrjXs25imqm1o0vPd3fN2GaqUz46unIYx NSGgJh3nZrxmOUk8R8e4oWLu7IAsx+hXUnhb3fobnvLgxLVH6E+DSbtFTC3HJBkQEV3Se5ldE mtsS+kP7IWkU0/AUs2nbxKIZHBdlo0fwIAK3i2F7nghTVZpO+VPqnGWsJw99SC+VqIqVN8C0n 6ScoE4xGeTOlLYx2HsaKPR1a5t2yiNP5MtjVQVU1tPvJMy7TA8FHv0a+SALmKI6DAJzMqLoPx KBxV+k6+8Wj09V5TR+AOXIL9xmQXiJFrzYOPcLSu/634zV0+nI7qEhKK2nhxg06WVO3aYS2Uq V0m2pNRw3MYMHRWN/CsCYvcszkrTghziiK/M0h7qUNWGY5jwUEjQnsZFH5JfYsljMRaDhaivv Q5utx4IFq1ox5uw6nQAdxHBucTcL9jFLs66SdEWR5tOxxaHh02A383LIhnW9fmdzsKm30kCdb D6tAmSfpXvOyu9FYZmWSioo3i0PElPCMl6Zhta+mxkAtY3aPANnh+VBqKGb8PCwWrqdi0QkmC pnFM9daxBnzDYgi6DPnQIJHxCn87QwY0TxoZ4y/EmgZDJVZ0G43sfwW+vuY5pMnc2wFRdtqpl AiEmTbOGxvmpbRY1/hxfTAn+BPOSnLh9oleKpUumtwoUyD89OBP7OVkpbSMJy1bkzAkiCBJJc cndBV7wYBd5Ju/Eq1 Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 13:07:21 -0000 On 05.06.2020 14:41, Carsten Bormann wrote: > Hi Julian, > > what is the decision process (who are the WG chairs)? There is no WG, just interested people. All changes since 2020 have been applied by John Levine (who is the document's official author since he started as TRSE). That said, I agree that more structure would be good here. For now, I'd be happy if more people would be paying attention and provide feedback. > On 2020-06-05, at 13:14, Julian Reschke wrote: >> >> Plain text diffs compared to the latest published draft are over here: >> . > > To enable starting to work on this, a diff from RFC 7991 itself would be= useful. Right now, we have , and you can also check previous changes in: https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-00.txt https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-01.txt https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-02.txt https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-03.txt That said, if you want a diff between "latest" and 7991, I can generate that as well. Best regards, Julian From nobody Fri Jun 5 06:17:21 2020 Return-Path: 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 E81333A0A8C for ; Fri, 5 Jun 2020 06:17:12 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 I5JM2WS2EaPG for ; Fri, 5 Jun 2020 06:17:11 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D6273A09F6 for ; Fri, 5 Jun 2020 06:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591363020; bh=twaEYd+fCrvnjqqqHewbCNa2XgDmfzkHBxWkOkDnx5U=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=lBlIVNqwui+sAMpXgBT/zLIuuNYfoKjI3WRau0QpGXt9cR8tN0qXQoKPNa09QDS0W 3qSGfvzzhDkXx0g1uEL/K9cMML0sU08h0bTOPRG/rryihYqWIu30TqNkPooukG1/7y vrnzI45VHcPlCBS2C9COdQGTpunjd3UnFrgekzbg= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.152.96]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mzhj9-1imMJB2P69-00vhOL; Fri, 05 Jun 2020 15:17:00 +0200 From: Julian Reschke To: Carsten Bormann Cc: xml2rfc-dev@ietf.org References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> Message-ID: Date: Fri, 5 Jun 2020 15:16:59 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@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:9oKzpzNt/3Conj1eB/QWtg0J2glYKJwS+82mDsv2xs0/jOWtlpF 8McUr955000kJeJ8P1QXdL4sd/GRFCOYiM1r0ZGE5DkFsDiYwhfB8+tM94/xyMEnChK/hCV JyvmdzslHTCTN2yA94nmxdBTc0gMQEa+XPxTvPTV+QOYnt+xe4ag1m7BQI/DUtnm++yw+Hc uVgpGHnFOwiFrDbL4Gu+A== X-UI-Out-Filterresults: notjunk:1;V03:K0:159oPMn+ISA=:qZh4r39qkJK9Y9TJUxKJ1t yrAt80Af+wc35OyFH+MedBSyIx9BwvkxFKGeicDlZEDJs3UrTtUJU559hmAr988qQ3eqgTHw1 07v3vMeqLqOGe0T9o0jKEwCA329K7p2XJuLEkhtmDbAQBvduiUVYy4R148sXKPKlthfSSFrIb jZuOJ/PO9kez46JQmqKLovuYJvAzx7GJoyZ5K9y42wsN6bKe82ksk4DEe5QArp/4wTa/0K17v 2HPI1TCa21EpAwh1j0FjvAx2paWgK8Fw2h/Qj+QjhIN1RbEhqMCvwOB2Fpo+eb1103YRevjN+ UVfSXql0r3zuyQVc9go+VRFs2bJpjetva2FYr6fqqZlzTrNjdKzOPO1P+qloFaidiPF2G/3am ELqTiyrHey1pe6sjwE+vSTX+rwAS9qL3a+i7k9Xq8WAuDKhRMBLO+4QtLaC0x6L7XvKOfiFH8 NChSW7pGPMdqMRcG8ma7gm0HUdiu4GJxXtrT1SWDmoj1s0BVeXMEpOILb6ot5YJbWqdPEur80 UCH8jSJE8/rMegSrw5I0EEqzHUVnPWVvKvLZrGZOsR5uroovgneO0HfYxuIw+mJ5JLslqrZzJ VcFJI0sCdsKfxDRvthx2Ye+/rQxMU208zySGNGpGgm+T2kWysVzxoUwrOAHo60mylnfzv9Bvb HgF4ES7n/v30yQedV8HeXZr6eDbqBJjJ+Ni2SR208pk7yAP9mHet9R4mjdsvu7HcaFxSjtGsH 5tDVybqqkJ4V9FEhsc/Sl4PSGLOHR6BbhHJa4bKWXnqdFZdEhviU6LU8//Q1aQItopGiYpq3U SZPjQ0453C4LSpQWkaT9hWihbV7sqMOMahGH2FmErRQ497c3YNGOApN44kECfXl0tv1qbpNo5 3tB0eZw+QH0YRqszmngG58EqiM+4MvcRNdbV2OglGHbaQftQ0BNsjq9hNA0CGDCrLKKGxDDDX 8StnTVHClXD+jeWzhLgcK6dAYKTEq2k7wSNBUTRFc+/P4twiOiwgjBorFyPwAUj3hLuYdv09y t80HraunP2lRWuVcA0kcuxM38Bo7J7K3nBmOeSQi2To1uZ42fgcVutKOT2cUrmS+qA315EleX jXI6MbP0AyR6fivs2+AmNC4Dt0SNz6mdSrI3OzbYVDYzWmjrNqO2IrJHzpnBMHjRcMAyQUewD I4w0KiN8q4ULOaArG29/ZrrXZfy6xu42Ztu72Fyh+HYzBKmdaLDgu+QyW7wL5sZCWmRuEgsmp Bh6wEdZbXZETGDbMw Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 13:17:19 -0000 On 05.06.2020 15:07, Julian Reschke wrote: > ... > That said, if you want a diff between "latest" and 7991, I can gen= erate > that as well. > ... Here you go: (linked from ). Best regards, Julian From nobody Fri Jun 5 06:24:06 2020 Return-Path: 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 1DB8F3A0854 for ; Fri, 5 Jun 2020 06:24:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 4EF-rfOa_bNX for ; Fri, 5 Jun 2020 06:24:01 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9401E3A08BE for ; Fri, 5 Jun 2020 06:23:29 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 49djyS0Z5KzyPg; Fri, 5 Jun 2020 15:23:28 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> Date: Fri, 5 Jun 2020 15:23:27 +0200 Cc: xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 613056207.601346-102f41c2b6675ddfe1bbd47640700a58 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 13:24:05 -0000 On 2020-06-05, at 15:07, Julian Reschke wrote: >=20 > On 05.06.2020 14:41, Carsten Bormann wrote: >> Hi Julian, >>=20 >> what is the decision process (who are the WG chairs)? >=20 > There is no WG, just interested people. All changes since 2020 have = been > applied by John Levine (who is the document's official author since he > started as TRSE). OK, that works for me (while we wait for the below to happen). > That said, I agree that more structure would be good here. >=20 > For now, I'd be happy if more people would be paying attention and > provide feedback. Will try to. Just as a random data point, my biggest problem with V3 at the moment is = that I only can use a subset of human names in acknowledgements or other = running text (I want to use Vigen=C3=A8re ciphers! :-); doing some more = work here would be appreciated. (The other work that is sorely needed is embracing standard typography = for English; I=E2=80=99m not holding my breath here.) >> On 2020-06-05, at 13:14, Julian Reschke = wrote: >>>=20 >>> Plain text diffs compared to the latest published draft are over = here: >>> = . >>=20 >> To enable starting to work on this, a diff from RFC 7991 itself would = be useful. >=20 > Right now, we have > = , > and you can also check previous changes in: >=20 > https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-00.txt > https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-01.txt > https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-02.txt > https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-03.txt >=20 > That said, if you want a diff between "latest" and 7991, I can = generate > that as well. Actually, what I=E2=80=99d *really* want is that, with the section = numbering noise removed. (I just looked at the diff you linked, and it is drowned in that kind o = fnoise.) [I said *what* I want, not that I have any idea how to get it.] Thank you for keeping up this work! Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Jun 5 06:35:54 2020 Return-Path: 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 BA24E3A0834 for ; Fri, 5 Jun 2020 06:35:52 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 VGSbHTnv5Ww0 for ; Fri, 5 Jun 2020 06:35:51 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E0A83A0850 for ; Fri, 5 Jun 2020 06:35:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591363964; bh=IhR5Z8kStavWtQQUwI4UzS4wq9Iq3me+9uCdw4Knb58=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=JkTHnagy28zDlc22JyGEKmf4Cd10Lg0QR9EPHRfw7rQa7sHWp7biAGyIm+6pAJmgj HBHRWOGlhXmVbvafRL0fCEDQcmCs1CJrJOpy2CB9kEhS9ipGzkt5TwNHtJgwEcHL/T 81Pdv4AOVZNYCThjhiFf57ofX7U5Ftgu/nO0aB78= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.152.96]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N0FxV-1imv6p1pjj-00xLZV; Fri, 05 Jun 2020 15:32:44 +0200 To: Carsten Bormann Cc: xml2rfc-dev@ietf.org References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> From: Julian Reschke Message-ID: <6233f397-e633-a885-fefc-d3a03ba1823d@gmx.de> Date: Fri, 5 Jun 2020 15:32:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:2mdlTH9OeC8mqRdpCWlwxfdQaiyXkAUzJI75Tzjyjro9zGvS4xy 3MgItx7tka0r1vPCTPujUwNpR+FqL0FEplCcU1JMtaMqfIOFFy8o2CtD00E80V3GWiwSEKl 43D2TOBiFzwKDc5cHHXGjLqEyxY7Yrl8pdg2KZnp+6DBUkLtd786cybU8gfb7EE275zT2Zv bwgDohbap4HYSa+aO7QHA== X-UI-Out-Filterresults: notjunk:1;V03:K0:Ej1xBcs4hFc=:cbK2e0YwFw/UuOGaTkpzTW 0uLD/uQRmVi5Tuam/fZKXnOFoF1HHzWsjVC6oK0MMf48xVrY+y7J+cAhNAtlV9nXjDjyK4knU HMAlE8Uvv3+T6WvS6SpILBOYfhey9Yq2kGMsk9laOXYfV2mm18R0VPubRnAhC4aebjVPwgnpM yz+s0DYgfycKzYDFX4kvDQfo982GLLxYpp3ywFqn+5xB/iahTR/2SOxbKIrCLehNKScuToL+t U2ZdtEb7YUzcKqWPpevY7InME6dhX55Y9NGolbuJtvkg2oOAVNqkZcIifvHbVFWt3h5y+JJUR 4QqUVuzCUDx1JCoxOLgZsog6EqbMiyoU3jY7yK3aYpRgYoRjzpnvfqJgKkagJU8RuhOSFKINp woS+AQfllei/+vwjZcY8BjwRr3XDbahzQRLyBQ+koGvSQLroJfgh8hXFAlKI3G67JoFYbo4xr 1DwDFFzZHdI4T22cggwDqoU1nfCr0cevbdp8URJN20Ht+VPvplf007cIeDvfGjSIoYmAwoRJ9 N2/zI3vKOUmEXZFYRJDLEuy2Zai7Cmxa6x2TnpUD995e+0e6YvigWWUgwV93+jhJ1DXU4ckma WUGhxfn5ZMSQ7KLUyV8/3UyjtV/DyyBuS5WhhXo0vI7OmG/S8tcl69flawNVtd2pxkfdbuIec nGSAvSfASPTeNfZE+KRWDHF2Uaut2mBOqEjyhDQWdyC7k0p3mk/iHGZfneffrNFBGYDb+TTPg Yo8RMtcl28OUHC/NDyxTnnksaxoMVnrNR+hmagzVOZhWM3GRvW/lG5qd1YDlerLIeBNC3mK3M 96FG1OQryB5N1gB8ggkibcg3JZP341Io54odmgHsYeKUtBd4MHyaAT036DA928oLXt+OV7ubi 39/bFzUMmwl9vgbGZhWsNe0IUNOxcFFfNQItRHnt3D7YDm3Fs1aQmySB9LnsHXjLBN772FyE1 iL+fjH7RHKQG16x8iC0RK1GL32xfF3JCurDdHgZc078GopCJ4nAm+8qFeXTbJMThr4LPI3NLY BXHx4SFdb2jLVDgOBwmd8yIoHn+qgUpNjt7LUIorwfu0oRNXwhcJFMm5Szcm/ytCawUonQxMo FyT/Nwz9qufIbW5/GxDxTdeXY0tDsSKAHxsE/G0BQbfc1BuFeOlolgIzRPh0lLF06AWxBO+ze R69ig6s14Rd9Kw5Vhj9WeAkdoTrKr5gbmhn5jSwBP0zKJzCERecaMC9dnMrrjzrEckhUqg83Z fiI3HPmSK0vQN29eo Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 13:35:53 -0000 On 05.06.2020 15:23, Carsten Bormann wrote: > ... > Will try to. > > Just as a random data point, my biggest problem with V3 at the moment is= that I only can use a subset of human names in acknowledgements or other = running text (I want to use Vigen=C3=A8re ciphers! :-); doing some more wo= rk here would be appreciated. > ... I agree that xml2rfc's approach to disallow non-ASCII except in very limited cases is problematic. It would be good open a ticket about that, even if the actual change in xml2rfc causing this (the introduction of ) is still not part of RFC 7991, and thus (pedantically speaking) not really an issue in rfc7991bis. > (The other work that is sorely needed is embracing standard typography f= or English; I=E2=80=99m not holding my breath here.) Hyphens and quotes? RFC 7991 really is agnostic about that; this would be input for the revision of the style guide (which needs to happen as well, and in coordination with 7991bis). > ... >> Right now, we have >> , >> and you can also check previous changes in: >> >> https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-00.txt >> https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-01.txt >> https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-02.txt >> https://tools.ietf.org/rfcdiff?url2=3Ddraft-iab-rfc7991bis-03.txt >> >> That said, if you want a diff between "latest" and 7991, I can generate >> that as well. > > Actually, what I=E2=80=99d *really* want is that, with the section numbe= ring noise removed. > (I just looked at the diff you linked, and it is drowned in that kind o = fnoise.) > [I said *what* I want, not that I have any idea how to get it.] > ... In that case, looking at the Changes section might give you a easier-to-process summary. Best regards, Julian From nobody Fri Jun 5 08:11:38 2020 Return-Path: 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 E31C73A079A for ; Fri, 5 Jun 2020 08:11:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com 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 RYbHPf7_Mr6H for ; Fri, 5 Jun 2020 08:11:30 -0700 (PDT) Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 379BB3A078A for ; Fri, 5 Jun 2020 08:11:29 -0700 (PDT) Received: from [172.16.10.110] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 7955A10B69; Fri, 5 Jun 2020 11:11:28 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1591369888; bh=VlswCgi+OwTrm8vREOGmiOHZr1dHy/DXXFEQ53ISURY=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=rQFv0mfDEb4Wjg4iJ6xpDzguS3wppln3/Lkamj7J7MbfnpDwMpRntwJZ6baTDVLg0 Lvu8H4BudQEzq/aps/U5Jl4nwjWhr4YZc2tM7JumHNV3NRszZARSm+/LfQ7G+4yJC0 83okfwHcvJdz2L8WQqQvOOiX5JLmbPIT+JUt63ofm9o/o4ex474ckARb9pkLMj11yw pUURaW6gqWJC35b/K5W4PlMynPOfU8NyZBuwIWBaz5oMCSaN/EW4Pcn1t7Zi699+nn 0V4j3rrO/IOn4EDawtwFFghSn/MI4lrPGozJvniZ1NgbtECl8FnBL5I8aOk+aJFDMe ddFB82hO0F6kA== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Tom Pusateri In-Reply-To: <6233f397-e633-a885-fefc-d3a03ba1823d@gmx.de> Date: Fri, 5 Jun 2020 11:11:27 -0400 Cc: Carsten Bormann , xml2rfc-dev@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <62DBE093-BE05-4BAA-A400-C939072F1E33@bangj.com> References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> <6233f397-e633-a885-fefc-d3a03ba1823d@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 15:11:36 -0000 > On Jun 5, 2020, at 9:32 AM, Julian Reschke = wrote: >=20 > On 05.06.2020 15:23, Carsten Bormann wrote: >> ... >> Will try to. >>=20 >> Just as a random data point, my biggest problem with V3 at the moment = is that I only can use a subset of human names in acknowledgements or = other running text (I want to use Vigen=C3=A8re ciphers! :-); doing some = more work here would be appreciated. >> ... >=20 > I agree that xml2rfc's approach to disallow non-ASCII except in very > limited cases is problematic. It seems like we all agree on this but it never changes. xml2rfc should not be doing any non-ascii checking anywhere. v3 documents should be UTF-8. Tom= From nobody Fri Jun 5 08:58:49 2020 Return-Path: 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 1DE693A07AF; Fri, 5 Jun 2020 08:58:48 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 AYCP03wdD_V9; Fri, 5 Jun 2020 08:58:47 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8446D3A0755; Fri, 5 Jun 2020 08:58:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1591372719; bh=tkOGG9MTRSubPZ9sEaraHUGp2pHwxCfxinWq0j3qpwc=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=BeII+PjELu3HQaVppESu7HaiLi+3V+tLcuv0mVcnxST7GzTn04JwqEo0+Z3UREvQI /TA1DpEIWRDxDLTBljigf+mJgC2am/6Z9t6PO5DjAd0bkjEIC8HdK3vR57gYyOIN9j wbi/hvu88GKbsaDiduoCkQoODwEcsEysZ4cJZ8Zc= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.124] ([84.171.152.96]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MiJZE-1j4LUH2JM6-00fOva; Fri, 05 Jun 2020 17:58:39 +0200 To: Tom Pusateri Cc: xml2rfc-dev@ietf.org References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> <6233f397-e633-a885-fefc-d3a03ba1823d@gmx.de> <62DBE093-BE05-4BAA-A400-C939072F1E33@bangj.com> From: Julian Reschke Message-ID: <2058e96c-ca75-a1a0-3bc9-19a9939d06bb@gmx.de> Date: Fri, 5 Jun 2020 17:58:38 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: <62DBE093-BE05-4BAA-A400-C939072F1E33@bangj.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:exKv+1bBc61YAGjcVyAl5K8iGSQLuKcJQqRRkVfUY/wc2NiMLql A9WjhqJZn2kOVoNdPfDYDF+On+zkhhbMk7MWzcrJZVE+5budVG9ZH9n51lMON2TdnrBoWJO WzbcnGACmx/px79XzrYcElc2UdYqNiszNlDWfFJLOSReBwZJn4Zc82EFmstI2pEE0cZ4bym EP1adoZq0F8dAmpD/vXzQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:Hd/DNFo812I=:w2qdrzDSBPpO+85fCJzbzG KTaB4gi8pqBmtL/wxEsE5d9qpgquf1uBUb2EjS6ZjoJ2jXx4+Q5OtIz9TZLqYyPuXY66dJCyO Udll45yAUqlnTASQIh7m7VqkBORw8FRYATEiYipwp5wzhsJP3RDTmFK5ooeDawHQwdajqpGjp cxKqXqUmh3HRYR6cRjE48c5VpBlOquVZzGLwERjsqgiNQr1V1zci3sHcIMmUSk1TXZ4qlCFVd 9Sby0CKDW0vdPxnxVFHTsd5Wl9UEMhKnF/OIy7nbZ6Yok+tiulNCSHFimXd6xvDKJSYkpghbC cyESrkCT9aDZ7+9MlqEpQlXyGEOD9O+UN99StoXsrqHFCi2Hv2KkpQIcwtjH6yHNxZZJtuhcH v4OV9084paXpEiNAQxXDnloFRuo9Qgan91P/wzWxl6ffnL2kyhbQOXyLP6Y8n7ZnKTYH2AbhA 1v8WLc5yeB1p29pL+fDD6GOXcMQfzAV8RSmFKUXdLXMEFJVb8AQxt3oYgFYABdxIGEHzY+dXw OFv4ng4+Ac1Tz7Eo4pod/2k9xEY2efaHsezim8w2F2zOg2rtUoFrsjkISKjfIUQgx8QBEQGE5 1MUG8Na68+pwc1AUq9SYcnnc+x45QZgLkOVKCaElS8+A8eY4M6t3KCrTIDaH+FW4tMD0j7EFn PlfeWMRc6s5+5QdzBLFiwFbNkE0/rQFl9H0a1XAEq7kEUe4CkiPVYPf2CF1YTQjvCZcPi4NGd 7UEFnDdBcc1oiG9yTGhFWxeYkfsr0AkUOV+GVGTAAsEy2NwwetxrNkN21xveplwgjZ2Q6vv53 R7wTDJT/Izy+eJQy9NIIF0q92RmVcs/adp9BDzwXVTpu9+lODOI9ZUfdl9ZAw0vk/zOT9WnCz A0hjeoekxTky/lJ67gHdrEgwmFKrOjXHRYJsXRoJTlU8Gh5FUwCoRbqlvEdvXKmYn9zyYpH4E YpjFbLjkVNAfShrN4Bvk/ZyZOOfYTg1tOq0CJKAxkePcRkTNKdKrtnIwOUrJO2u+UFmp8ZJJt F6TAdnqI2FKCTeQbiFuEG8KPHm5oFXe/aUzF6poylxiTIh3G3+xShMr/74VuA/il2X95vfRdn UVPXLzygPj0jQ8GxhJ1/4hmRsYhd+1qmqOJyZMa/FSJcKm9bsy3yZdKRlPePHKRH+rycZqaTj zsOHdlQhTQLGCdH/+BD9e9zSdbwz16KpoZqsZN+22KF/aUeEiUnjojUSjmSo5u2sssyi4hyu0 jk22rK5Kx+FNVcpgP Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 15:58:48 -0000 On 05.06.2020 17:11, Tom Pusateri wrote: > > >> On Jun 5, 2020, at 9:32 AM, Julian Reschke wrot= e: >> >> On 05.06.2020 15:23, Carsten Bormann wrote: >>> ... >>> Will try to. >>> >>> Just as a random data point, my biggest problem with V3 at the moment = is that I only can use a subset of human names in acknowledgements or othe= r running text (I want to use Vigen=C3=A8re ciphers! :-); doing some more = work here would be appreciated. >>> ... >> >> I agree that xml2rfc's approach to disallow non-ASCII except in very >> limited cases is problematic. > > > It seems like we all agree on this but it never changes. > > xml2rfc should not be doing any non-ascii checking anywhere. > > v3 documents should be UTF-8. All I can say is that my recollection of the discussions was that we did not want to enforce anything about non-ASCII characters in grammar or implementation. was first discussed as feature to make it easier to talk about non-ASCII characters (automatically inserting long names, etc), with which I agree. Disallowing non-ASCII outside (and example artwork/sourcecode) IMHO goes too far. Best regards, Julian From nobody Fri Jun 5 09:38:09 2020 Return-Path: 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 D6EF43A08E0 for ; Fri, 5 Jun 2020 09:38:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 MgXGA8eCPxcu for ; Fri, 5 Jun 2020 09:38:04 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805F23A08E8 for ; Fri, 5 Jun 2020 09:38:04 -0700 (PDT) Received: from [172.16.42.112] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 49dpGy4KS2zySL; Fri, 5 Jun 2020 18:38:02 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) From: Carsten Bormann In-Reply-To: <62DBE093-BE05-4BAA-A400-C939072F1E33@bangj.com> Date: Fri, 5 Jun 2020 18:38:02 +0200 Cc: Julian Reschke , xml2rfc-dev@ietf.org X-Mao-Original-Outgoing-Id: 613067882.1602449-fd0df529f015900998ca44ecc9a1fa41 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8fd7f1ba-96a7-e3fa-29a6-32fe47b5cad5@gmx.de> <1DF69700-3713-40B8-9A70-818F69483733@tzi.org> <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> <6233f397-e633-a885-fefc-d3a03ba1823d@gmx.de> <62DBE093-BE05-4BAA-A400-C939072F1E33@bangj.com> To: Tom Pusateri X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 16:38:08 -0000 On 2020-06-05, at 17:11, Tom Pusateri wrote: >=20 > v3 documents should be UTF-8. Yes. And there may still be a *style guide* entry to limit gratuitously = going overboard on this, and requiring the document to be readable based = on Latin reading skills only. RFC 20 is not relevant in any case. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Jun 5 13:34:55 2020 Return-Path: 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 A66973A0D0E for ; Fri, 5 Jun 2020 13:34:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.851 X-Spam-Level: X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=NwNRADHb; dkim=pass (1536-bit key) header.d=taugh.com header.b=MKbtvEAb 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 cnCT9t1wDmS8 for ; Fri, 5 Jun 2020 13:34:52 -0700 (PDT) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F410B3A0D04 for ; Fri, 5 Jun 2020 13:34:51 -0700 (PDT) Received: (qmail 83976 invoked from network); 5 Jun 2020 20:34:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14805.5edaac69.k2006; bh=1OAicKec7noHpOtpWHCsH9QxPfsCrZMuZ7Xzpgasdpw=; b=NwNRADHb2lit/R3ECzlEUUH7VNiI1jyD/crqSL/ls0cVumwLeuF5ZV1ghdU6/NoouWEOPHZF4SXE02AD0JfDfkCp2sdYX/y313DcXYiop1Cn/lCtO9SaIsd6Gn8kkR96iGH9PkeCjsB67TFNIa+9jcHkLMX3eNlbfc1ZlrJcZjgxZdwzyHAeACLWKd2oSkudSHoUjSo9wt/EAcNTi3h2t8W2dU2fPj1nE3H3UR6ptx8TCEJDzv3BIi+wKohXFyip DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14805.5edaac69.k2006; bh=1OAicKec7noHpOtpWHCsH9QxPfsCrZMuZ7Xzpgasdpw=; b=MKbtvEAbZG2KYQWiVNsQlMA17Cz5e+bJVr+fVuaUNOaALXppVXr3qum+6Rt2x0CdyXmrFRVNoJzFfp5ZjkSwn/9GhKCzAdr25+lzCdkblnBZmGN6z9LxCdc7ymCFLTyL5XWwrCk7FB5vi+puhZKuybja5b9kjyHK95pWSTjJ435Yq/U5n9lGgTONdyaOdBt8bT9HtsvTp5RKXef3GYGDUnOwdAM3+k2vCGV8jdfgegx5dtphTlAwvXLrPIcmAac5 Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 05 Jun 2020 20:34:49 -0000 Received: by ary.qy (Postfix, from userid 501) id 5EF1C1A34E7B; Fri, 5 Jun 2020 16:34:49 -0400 (EDT) Date: 5 Jun 2020 16:34:49 -0400 Message-Id: <20200605203449.5EF1C1A34E7B@ary.qy> From: "John Levine" To: xml2rfc-dev@ietf.org Cc: julian.reschke@gmx.de In-Reply-To: <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> Organization: Taughannock Networks X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: Subject: Re: [xml2rfc-dev] progressing RFC 7991 (and friends) 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 20:34:54 -0000 In article <640cdf3e-391f-7e9e-df9c-c093c0f2d2c6@gmx.de> you write: >On 05.06.2020 14:41, Carsten Bormann wrote: >> Hi Julian, >> >> what is the decision process (who are the WG chairs)? > >There is no WG, just interested people. All changes since 2020 have been >applied by John Levine (who is the document's official author since he >started as TRSE). > >That said, I agree that more structure would be good here. At this point, we are still trying to catch up with the differences between what's in 7991 and what's actually implemented in xml2rfc and in published XML RFCs. Once that's under control then we can address change management both going forward and retrospectively. From nobody Mon Jun 8 07:59:42 2020 Return-Path: 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 14C1D3A0879; Mon, 8 Jun 2020 07:59:40 -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=unavailable 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 3ZIbp-ZMOhC2; Mon, 8 Jun 2020 07:59:39 -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 78BFE3A0C57; Mon, 8 Jun 2020 07:54:27 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1jiJAR-0006h7-Ap; Mon, 08 Jun 2020 07:54:27 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Mon, 08 Jun 2020 07:54:27 -0700 X-SA-Exim-Connect-IP: 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: Subject: [xml2rfc-dev] New xml2rfc release: v2.45.3 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2020 14:59:40 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.45.3, generated when running the mkrelease script. Release notes: xml2rfc (2.45.3) ietf; urgency=medium * Fixed an issue with rendering empty
    elements. -- Henrik Levkowetz 08 Jun 2020 07:51:35 -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.45.3' Regards, Henrik (via the mkrelease script) From nobody Tue Jun 23 10:30:45 2020 Return-Path: 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 5463E3A08F8; Tue, 23 Jun 2020 10:30:29 -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 yxtofrp7WeIC; Tue, 23 Jun 2020 10:30:27 -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 613983A0881; Tue, 23 Jun 2020 10:30:27 -0700 (PDT) Received: from henrik by durif.tools.ietf.org with local (Exim 4.80) (envelope-from ) id 1jnmkd-0004Be-5l; Tue, 23 Jun 2020 10:30:27 -0700 To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org Message-Id: From: Henrik Levkowetz Date: Tue, 23 Jun 2020 10:30:27 -0700 X-SA-Exim-Connect-IP: 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: Subject: [xml2rfc-dev] New xml2rfc release: v2.46.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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2020 17:30:41 -0000 Hi, This is an automatic notification about a new xml2rfc release, v2.46.0, generated when running the mkrelease script. Release notes: xml2rfc (2.46.0) ietf; urgency=medium * Added
    and entries in additional places, as a workaround for WeasyPrint's eagerness to break between
    and
    . Fixes issue #529. * Tweaked the rendering of inside table cells in text mode to not use double quotes to distinguish the content from surrounding text when the only cell content is the element. * Modified the text rendering of table cells. and now implies no special rendering (earlier, they caused a change in table border on transition) while now always renders with distinct borders compared with . Also added 'light', and 'minimal' table renderings, with different table border settings when compared to the previous rendering, which now is available as 'full'. The 'light' rendering is closer to the v2 formatter table rendering, but does not permit table cells with colspan or rowspan different from 1 to be properly distinguished. The changes in rendering fixes issue #527. * Added a --table-borders option with possible values 'full', 'light', 'minimal', to control the table rendering of the text renderer. The current default value is 'full', but 'light' is closer to the v2 text renderer's output. * Added a new internal join/indent setting to the Joiner nametuple to control outdenting. Used the outdenting setting to enable outdenting for artwork wider than 69 characters in the v3 text renderer. Fixes issue #518. * Added missing support for @indent for
      in the HTML renderer, and tweaked the same for
        . Fixes issue #528. * Corrected is_htmlblock() to not count
        ,
        , and
      1. as block elements as they cannot be wrapped in
        . * Updated and refined the div-wrapping used to introduce additional IDs to deal better with anchors on
        ,
        , and
      2. . Fixes issue #530. * Made the CSS setting of background colour on and more selective in order not to interfere with background colour in tables, for instance. * Removed CSS that made URLs in references not break across lines -- the drawbacks turn out to be more of a bother than the original reason not to let these wrap. * Did some HTML cleanup to make the w3.org validator happy. * Fixed a few places in the HTML renderer where an empty tag could cause an exception. * Added test cases for empty and double email addresses, and added support for multiple email addresses within an author's address block. Fixes issue #522. -- Henrik Levkowetz 23 Jun 2020 17:15:23 +0000 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.46.0' Regards, Henrik (via the mkrelease script)