Re: [xml2rfc-dev] [Ext] Re: [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0

Julian Reschke <julian.reschke@gmx.de> Wed, 30 October 2019 14:45 UTC

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 E8BE612013A for <xml2rfc-dev@ietfa.amsl.com>; Wed, 30 Oct 2019 07:45:16 -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, 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 UzEF6zQb4N_U for <xml2rfc-dev@ietfa.amsl.com>; Wed, 30 Oct 2019 07:45:12 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 5A2FC120108 for <xml2rfc-dev@ietf.org>; Wed, 30 Oct 2019 07:45:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1572446693; bh=vfptMmffFH2VstBFDFp1kf7f32KZXAHxb6QHGxTYzo8=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=hRGzVg4N9fNpbaU1PRWu9PJPg/0Pi0W5ujhdSFPd31GwNJ9Ww60l314zmpgbJSXzv gwsQtjB9v34Pe7NEXmH2q3ODBX0eFxf5h+b2PXq9HrIZRbqtIrFVfE2f/1fbiYDovS AmHBvfb5R18f8R66nZiRLAPb5mOU7NGPIbdN42X4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M9Wys-1iMXxp0FFs-005dMg; Wed, 30 Oct 2019 15:44:53 +0100
To: Sandy Ginoza <sginoza@amsl.com>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <71bc8d39-d06c-d900-cc8e-04a48218d75f@gmail.com> <0905DADC-E9D5-47A7-B610-F8A62686D2BD@att.com> <07DBAE10-D1FA-45C4-B7A2-321B265CA302@amsl.com> <694c9244-98ae-1e64-39ef-8756d48b36ef@gmx.de> <860c663b-744f-a033-cc50-96088bb1b33c@gmx.de> <04DCBCE3-2C8C-4B03-9081-EF2B7A5C6087@tzi.org> <b096e29c-02a0-e009-621e-c1eca4712226@levkowetz.com> <4321EEBF-92C2-4405-81BD-899C0FCAC762@tzi.org> <5593c2d9-0bb4-93e9-f5d0-babf194340bf@levkowetz.com> <6BF7D165-EA48-44C1-9153-3F011058561F@tzi.org> <7088451e-745b-a31b-88fb-bce9cb48696a@levkowetz.com> <efb58534-8112-2303-1967-536daae9ff51@gmx.de> <34FFD9FB-7D0A-4BEE-9BAD-AFBD7F883CE6@amsl.com> <d53ef90e-5a50-1472-a61e-12c7a417ac44@icann.org> <b19cd7de-6992-a3b5-ea23-929627018cc0@gmx.de> <019a4a58-ca92-0497-1155-303fba341241@gmx.de> <FB3B5D3A-2AFF-4ACE-BD71-D9EE2F9A4908@tzi.org> <4911a729-648a-a6c7-e673-4dd0fc0cadac@levkowetz.com> <E875F5BB-B2CC-4BB0-8202-6EA2C2E1EF79@amsl.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1cfe235b-6c51-053a-2275-cd3167773b27@gmx.de>
Date: Wed, 30 Oct 2019 15:44:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <E875F5BB-B2CC-4BB0-8202-6EA2C2E1EF79@amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:EESUsTvz7fM5OF4/Ofi+RoBQnwH9EXNee9r/35XIexoIO0mwaNM VoddIxzsiT2Hcdsj6pRBp/3GzIxmqUBEtxhCCewdeCz4WZOD2jOElLFfGp3jwSWSOEn3I11 PfgPl4tlWJysl/5ytu8OgS7NU/IvZLpMMaenHzBWu1ud/ppOG1xUhSQt2pFxSs0rybvUzu0 b4v9flxpCa4XlUV4TMV/A==
X-UI-Out-Filterresults: notjunk:1;V03:K0:NIqM1z3Ibco=:sKjDcNPp0F3sITJC5XfHpU esnVA3GgUh6vYgiYq67xzVwTxMCwhmrAnDBHSipg/NIn1IiZgCQZz9OrAB+X0tcv+Y7Ckui/+ a9Xzh4fPL64JtoGxfU/ArVyOMcTIuaFdTWr1FSBobv7oakTJJA2A2ZbIEo9RTiu7l90DMdi/M l4zGWj6aF4DLR6BQPWi9n7C1L8yeleNTiDl10vmGzREGb+U1oZr7clo+y79tziwJtAlJlsMvm CpqJerlZ5l+Cq0u71qm8q3++fy0+onaEnKbsrihFFF5nnylGDyyRU2nqMy8w7EiEwuSiGvGFh VfftkNIjAkPTrcdAxkf870RiCNZze6rfwivYuaZLTCryCeO3jTcMIMhMeEdQNgji6ZoSRjKol IXJ7Cjcm1zHCBixFFs+B4409BbIlX62+4/QB59LJFIhIh2pQrQdVCWMjEU1iDbk2GJZDznCDd D2fJEI5zcehBIE8HwS28ugduR43pZvrljHnZobhM1T4Tb3xMNSzIni7QnhzITVOMnPqWCzdCP jvno4gQLCUP5M9gyc/T0D4Lokwct3dtM4Co6iDL8k1G7PIi55EktHqHc5kWbNEAnrWTcv8HSR 5uBhPKM46BMf8WTbjRS9WA/C/IbOJLi8ZitHdtexkIRns3SOsbgk93Coly//lk3TUYoE7X7XO cSC0VzAwjyoZ5/EziMEcMPl6tih7CROAno3OumLiXPSIVFzELUWRitlw9TJZuhzCdb3JOvLF3 MXPNerpVUsHuqh5tf8iGyuu5JAoH7rOGCIP0s1LGmCnSVtdkKAIrGLzFf59slyqb7CI/aU2OW Arosnei18vWy5UDFLI8CsIrtPgL06wRr+/R0SmwFuQ4WyiqJsWdwWAuCrC4qEO4CgOrgikkvp h5cZA9+bLwOvhPFgwjP3H+TdEEUGtf4K+xyuN5D8dLXi2jaCumez6/iTbgL/y7f9cqugssvAA 6r1HrFo1aZQGg75VXw0LNVLT1OnDmEQ4abbruF2wQMPAipz11NwUsiFQGfHwWEXaLqmO+IaVm vITCeAuftURUPP4TZuAI2anKrbVvequq/ehsc8ZXLiRr6boAEQtJPS6aqs1VncFfCPy085oem j/n8i+uVDyCOJGRV7bwoNJs7JaF5seA8Uh92/O+7MYL1OR0/5GB7ynKxp152f+ng7vHgKFcXT mt4GAghzhiybhS401K6IQkeaLtH/kiya165prLK2TWCmkA/YU/agfIRY8Ufd8Z0YupIfOmRq5 9/DuQoU1H38ku5lWNbgXI7pqgGaw5EdHBRLANDWH3OH40aYsOpy8dfGErEHQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/YFgm4J8R9ePnpQJXj032SkMevbU>
Subject: Re: [xml2rfc-dev] [Ext] Re: [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.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: Wed, 30 Oct 2019 14:45:17 -0000

On 30.10.2019 15:37, Sandy Ginoza wrote:
> ...
> If possible, I’m in favor of allowing <br> generally — it’s not 100%
> clear to me that we won’t ever need <br> in <title> or <name>.  To help

IMHO, we shouldn't modify the vocabulary unless it's either trivial, or
there is a compelling use case. I don't think this is the case here.

> move us along and get <br> allowed in the less contentious areas, I’m ok
> with using the other entities available to us in <title> and revisiting
> this topic as needed.

+1 (if by that you mean using NBSP to bind words together).

> Sidenote: I am concerned that the ability to update the v3 vocabulary in
> the future will be tough and time consuming, especially with the RSE’s
> departure.
> ...

At this point, I'd be very surprised if we had a consolidated,
documented, tested and reviewed V3 vocabulary by the end of the year. So
we should make sure that in the transition period, we'll be able to
continue to work on that.

Best regards, Julian