From nobody Sun Aug  1 18:49:46 2021
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0283A0A26 for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 18:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level: 
X-Spam-Status: No, score=-4.4 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, RCVD_IN_DNSWL_MED=-2.3, 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=iecc.com header.b=T5hhw/wH; dkim=pass (2048-bit key) header.d=taugh.com header.b=LTB7zegZ
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 bp_IlzbvVssL for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 18:49:38 -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 52BE53A0A25 for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 18:49:37 -0700 (PDT)
Received: (qmail 77311 invoked from network); 2 Aug 2021 01:49:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type; s=12dfb.61074f2f.k2108; bh=EDbaNrRb1B3vKirKMFPllmXBhoAnlkWCXJz/HNdIad4=; b=T5hhw/wHFsUVbD6ydx1mnUHQc5XUgNYAZctkvtKgkL8VaXbAmp+Mw+0Ww7aAGPltITUOtMTeWaCZr1GYh9qjvVbrT34FlY7XUpxGZbpL29V3wmNH2zNwi2E5y5gXI6c3W0sZCBhamT65e90zUnSIZiAytp8H9onA423lhZ2xTeT2ANMDwwk7rLMHJRwcPMbDSEr5IO05IW7Yyk/sVWy2NA/UCM0BOMmU1AxX4ZEgknIMM0dlg4scZyHxH10Y00H0ft3oiulqhw2JlY7kSzYBBaPaC8fMFQ6LLX33TB1ya6jCVNk8tXKVMbi9TnulD2438cLs9AcJtF7UcgMqfBcN7w==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type; s=12dfb.61074f2f.k2108; bh=EDbaNrRb1B3vKirKMFPllmXBhoAnlkWCXJz/HNdIad4=; b=LTB7zegZiUyPW3/2EAGmkmtACjzb9O7a9Inl7Jdy7Qo/WrXHMuOwM/SOdeAl1f3CaUYDrj+DxDCDIaR36SkFsYhwFlsB2G31IUW32nVkhLTxAWKLi3zrYV7FtuFUkGDQ8wFu47FuI/gxV3OSEvB+fzw7OssUHm9V1+kI7oPEg3XnwhfVL4iKZ1V8ulmPQVBIneZPEnapqpCTb30lTghnH7AS+lJcriLUkFIaOTDtYfJ4QLhR6L/plyv2bGvylIcPAAiPr9/t88XCmfRAXjITOaxyCtNymh4mGwpvlhUceuZ5P05UoxeReyjR4pyqUa5OR4hFy+uir9w27PwAc1/rlg==
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 ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Aug 2021 01:49:35 -0000
Received: by ary.qy (Postfix, from userid 501) id DBE1B2573D9C; Sun,  1 Aug 2021 21:49:34 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id B24E42573D7E for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 21:49:34 -0400 (EDT)
Date: 1 Aug 2021 21:49:34 -0400
Message-ID: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AKBW3j5Ac8GCfyCrNU5Bk6VDVAs>
Subject: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 01:49:44 -0000

When I run rfc8799.xml or rfc9001.xml through the current version of 
xmlrfc, it says:

Error: Found no element to match the <xref> target attribute 'section-a.1'

When I look at the XML, the target is there and this presumably worked 
when the RFCs were published.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Sun Aug  1 21:11:10 2021
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F653A00D8 for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 21:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-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=itaoyama.onmicrosoft.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 xQZXRGf_CgIV for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 21:11:03 -0700 (PDT)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-eopbgr1400129.outbound.protection.outlook.com [40.107.140.129]) (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 B02833A00C8 for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 21:11:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RvpzHSkPi8cUGmP6icgYtEnb6M/X3NCuNYhhIlC1PROYdbS9Avu1J7ciJifzlKPMWytOHyWpUxp3WfLORBZRsbvnQmiUCg5AFNS2CHgAyzGQqw3dw2vABAvSo4gMu+/pclKv5eQYZqtUWnWN/citXqzvCC8srcq9KR69jIQeQfbEWGSCpVZn4VUueI7ypQ1tU6ctN3c9WvGsWRMI6WAEElL6I/Z6+OhcNv3+vD1UJLU5yL49QsoW5SjIH8AMG8J8JTgByhsCFwNGgzNI0RWK58MQUPzd14NaNV8RSAykWa3U+w76DWVbAQDkB03vyDEiaLcs9eyhA23yjXGiO/x5xQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5BbCMbmWNwNtnAu/Mn9XFEsyrJhV6Ll91qjQ8FSqqq8=; b=cizYYAaI3UOMb9cy7o8oyHpCzfd8DQ2ok0Rt/cJ1scjg+e2PiEo9xmVFy+z0wLiGOuLajC4w83uKa27MbRm0F3ATlNYrwpttLG0kVzzrz5GdtPC74MsC9joVEFqEC2icHkgKwgjUxz+N0xTdlJmqVtc8rr/RXOvR6aIqp0NMs27Mp0NL6JkaGHBhC0MKXTOrPWc4xI90KAOSIvxzofy1GAOcF0vZJ3mUWzKGMw8vLKBEOfbmGKPtdPk1ypi71PTSrLwBoKzEBwESLrOY8qvhajAIIEpxp3IO0jv5p2nDJq63dq5BoFsZbEEhVLpQJfeuGdLqJxzIFhdqHPl4p4rA+w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5BbCMbmWNwNtnAu/Mn9XFEsyrJhV6Ll91qjQ8FSqqq8=; b=K3zJ3xLVXEzR5xmBPULihJJCu/eP/CRi21qjbo0qyL/LM2vfQzle7LMKDfu8PwVdKQ4YkogqhSFUtXGdscjG26aQvx/KhE8KanLRjTNfY5IIVwmYyIu26Jaden+GFRlXrxaRSGIpEN6Y3yGYcNSrS4lQ4pkhu3QntR0D5nv38Cs=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp;
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7) by TYAPR01MB5721.jpnprd01.prod.outlook.com (2603:1096:404:805b::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.23; Mon, 2 Aug 2021 04:11:00 +0000
Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::11f6:52bc:8bf7:d82b]) by TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::11f6:52bc:8bf7:d82b%6]) with mapi id 15.20.4373.026; Mon, 2 Aug 2021 04:11:00 +0000
To: John R Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com>
From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
Date: Mon, 2 Aug 2021 13:10:58 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
In-Reply-To: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: TY1PR01CA0206.jpnprd01.prod.outlook.com (2603:1096:403::36) To TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [100.70.19.14] (133.2.0.94) by TY1PR01CA0206.jpnprd01.prod.outlook.com (2603:1096:403::36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4373.18 via Frontend Transport; Mon, 2 Aug 2021 04:11:00 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 2559a27f-83fb-4211-1d2a-08d9556b8970
X-MS-TrafficTypeDiagnostic: TYAPR01MB5721:
X-Microsoft-Antispam-PRVS: <TYAPR01MB5721F1CF759DD0F0EE1B291FCAEF9@TYAPR01MB5721.jpnprd01.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 95jC0DpxhnI6eLaUnildxgmYQfSm15M6K2ODUoQ8JC0kEgNQeCHkLEJptZdnqC00RDkxTtftX5p1QWKSDgafSfSAEWQVSYGHTmqaP72sdExdTKsln987RZ1Ag1Omi2ViEcFo2xJttV3xO5yb6mhYqBeld3uGHHjb7Kts4hOPH2q1xFjWLzY/H9luVivyH8xYhtIzun3G9Xv9/AdNjUjgNvOQ4HhKwSGjr2V9m3kBEB3hvx4qE0IsP0+YbWRSKDxfCZUnbMXUKWZlV1RqbVCjyFWZkPC0ChfZNgx5BAK5merd/1K2eMmty6pzZM36N8Z7K2vdEjsa2khZieTwf7a5HMoDBk8Qzg92tyxRXFkT8JUXPuVCIPgL3x2ZEX5I+nTTTQBI3kp9cCR8HTQI+4DjQNILdDw8WrIZQUqGI3xTsIJi6BCNHwG9nQxQtI8JSrc6rhWjUFcYEsHGS00EKx5l7SQTJV+PAo3nmBAK2PN0SM1VjqqsyJrFrRzglgH/VntInELVKf4nDRBXBDm4HZdU0HYWh62OINjhAG0or+ekGAQxT/M+KPb1cAwhtREhhumxXOH/j7WWSfxnLcYkCZ67eVKedRWjevVFdBNnVrIrQNxBzqu2JwdIU14KyBq6MG2jSrkexeyQMZjFCjIVor8U3dg8E45kOnIvsHAV9iV8ieU5AOagLnZEuXGTxeMYaOrQAdiWomckEfTgAWV8GaQnuKyVuqShcP6mkuUaYnHTosnaqXKrDUvlLhOQ5MfHsHPxaA8dt/SDBdXk4L4igeAdtJjUWr08ZJW/SQcwhn9Kx18mpE89TOofFgEdL3qym7peRPGUIy57B5ctKwgErRTUb4txxoGwhr0foMoMs0WT9OzwH23xEFyatpikQEaV5D2O
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:TYAPR01MB5689.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(376002)(366004)(39840400004)(346002)(136003)(316002)(6706004)(2906002)(786003)(6486002)(36916002)(52116002)(4744005)(31696002)(5660300002)(86362001)(26005)(16576012)(186003)(8936002)(53546011)(8676002)(478600001)(38350700002)(38100700002)(66946007)(31686004)(2616005)(956004)(66476007)(966005)(66556008)(78286007)(43740500002)(45980500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?UnRsMldFWWlLUTdveUNBdFVnNzk1R2l0Q0xPSWpGc0l6S285LzRsdEdzRjdl?= =?utf-8?B?UU5Oai9ZTzFWbGtTeUtLRis1dnZyYzg0WjZGb1ZJVHhpMk9NMmpLZ0NGMVY3?= =?utf-8?B?bXJwZFFzbW13ajBSMmgyTTJ0NDdYd3Bxc0U4VUhxdmtoRmQvQVI3bmZya0pY?= =?utf-8?B?Q04xVmY3TzY1QUZnb0Q0cDlxUDhBckhGOXFqMzVBQWNobktlVHFjVU90MGZn?= =?utf-8?B?VDk5MFZaZ0d3NFpTckV3RlYrSG1sa2k5QTMwc2RyTUl1L3lkSmRjbldaMHpv?= =?utf-8?B?S2hKK1hYRW0wdVNBRHZ2TjdJM3p2MlJHT3gvWk8wcjZDS0w3RVVkM3J6K0tG?= =?utf-8?B?OVl3emtGMTEvSjhxNDN2a1R1cXN2dWp2MThyWGM3dHBmVzJiM0libE1aQW91?= =?utf-8?B?ODZ2V1ZJVlhtVXo1dnBaNGNVS3c4bjJEc1lPcVVWelVSSnZJRTgzN1NtUUk1?= =?utf-8?B?cHdmWWpxNEQvUXJrck1mWXlLY2p5cHdvQlNUbndwZXl3d3p4MFdZYnRuQjlP?= =?utf-8?B?Q1dFVTM5RTR4YkIwakFSempQSGpBa2dCeEJmRkJ4Zzh3aTFLUGFLa3NEcGZk?= =?utf-8?B?UTJEM0Q4aDExY3Q1M2dwSWpPQmh2ck1WcVcyQlQzUDZ3eHhyWnM2bndHWVpX?= =?utf-8?B?WWdKbHhlV1QwNFpXemI5N0hTUjlNcjhydzlKbmpFZy9qYUNrVGNaMFRXd0tl?= =?utf-8?B?dHhtcDQ4dVR1c0hWVkFyQkU1ODVYUUVVT0FVNWxvUThRWFdkd1JIbnNCR1Fm?= =?utf-8?B?V0l3U0lLdnZYWWl1blMxdElMbnJiTFo5YkJ5Wmg0alBOVTZFWXZXczdTRE11?= =?utf-8?B?U0NHTktCb1g4dmRRTkV4KzFETk5jblRQQVl1UjVWY1h3ZERvTFU3aGJ3VEVw?= =?utf-8?B?dDJJbG9lYUVpQlNMUGtmbk9rVmpIOUwyLzZRcmdvRUlSNGh5c1hMZmM2YVhu?= =?utf-8?B?R2Z0K29XbmdTR0dDVndSbDdQL20yQVpTd3NFRktrS0ZpblVWNFlLOTZQMzkr?= =?utf-8?B?NFlXTS9vQXpEU2VBdktmM0E4K2d0SnR0RDNkdkdVWkF0U29GVnNaU2d2b0pT?= =?utf-8?B?dllvaXBSN1hDZGtoN3c0cXN6TmQxT1lTQ3M1N1pkSUdUeHBDc1VYTGxlNE5k?= =?utf-8?B?ZGZMNWxIR1lsZS9uL0hmZUlLYS95Z2FKQTlmUnN4ZEswNVFaVXJrVDlKQlIx?= =?utf-8?B?SStoUDhKNXpNL1Zwa21pWkpmakRWZ05OcVNGUTJsNDVWdDZ5SDhQZzV5U1A1?= =?utf-8?B?SVgwVGZIN2EvYW1zbWRoak1mUXJRZjVSaFUydG0wemhONnFSMGFBZFJncXlC?= =?utf-8?B?S1JoM0sraFM4M3g0WVFuZHNra2doUDlITTFEVlF5UkkybHlid1IwL2JVRDdy?= =?utf-8?B?aHFSS0NmOFFwOCs3NFRZaHdLaktLWVdOOW9LcWVTSnBmYmFCU0hpZWZDOXgy?= =?utf-8?B?VnQwVGpWaXozNkhTZXpTZy9yK25lS01Odk1LM2xHKzJiYVR0ZG96TUpXenJO?= =?utf-8?B?UlYrRkFHMEN2VFV0UEFxcEJXZHNTTVJQRzBaWlkxWFJFeUxRWlRnVzllTHNW?= =?utf-8?B?WmlHaFlJYnFWYTgyL1p2T3hRRHBERm5rRDYxbzBoQVpZNVJuTnMycFVOclMz?= =?utf-8?B?Njk3aVpHbndXOStjREZJQ0Y1QU1ldGJrcU4ySzJMMS9iUm5HSHJPaXhNSy9Z?= =?utf-8?B?bnA4VGNWK0FTRmZFRDl6cW5ybWhVbjlVV1RIYmxpQzhyR2NHQURQeXk4VFBt?= =?utf-8?Q?EjgxB0UF52QJHVNEV8lKHH5XtsHrYvofkq/u8JT?=
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: 2559a27f-83fb-4211-1d2a-08d9556b8970
X-MS-Exchange-CrossTenant-AuthSource: TYAPR01MB5689.jpnprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Aug 2021 04:11:00.6737 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: wQ3sK1QI6oMgV+HKaKImmjG+PfpqOe6PkQPexJjvnbnw9JUdIrvoi55c0ZKc7QCUZzfvsdpUm2xQQzT9t2liuA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB5721
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/BXqbHAV308DkA0TTAWE1krMQdSE>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 04:11:10 -0000

On 2021-08-02 10:49, John R Levine wrote:
> When I run rfc8799.xml or rfc9001.xml through the current version of 
> xmlrfc, it says:
> 
> Error: Found no element to match the <xref> target attribute 'section-a.1'
> 
> When I look at the XML, the target is there and this presumably worked 
> when the RFCs were published.

I think it would be a good idea to add the above two documents to a test 
suite to avoid regressions. And use some kind of continuous integration 
testing (if that's already done, that's great).

Regards,   Martin.

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
> 


From nobody Sun Aug  1 22:10:28 2021
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5171D3A0919 for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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 (2048-bit key) header.d=gmail.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 37pJxo5BmUFC for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:10:19 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 999833A0918 for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 22:10:19 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id k4-20020a17090a5144b02901731c776526so29800898pjm.4 for <xml2rfc@ietf.org>; Sun, 01 Aug 2021 22:10:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Ox1ZuBNe3+SuVNijCiTalg3PzrxSVjSGxx6zLZrKxTc=; b=AaoLCswedyM9zKI0YhP9/ORvE/jIR1BQhut6DySk2rIqgm9vylOJXtL44tMu123bH9 xjGKv84J2FeLTkd63dUnF+0rMVkWZ2pKPdeUhRiW5JB9fmEAWNYQd0oWDmR55JixSyL3 XdVhPP2gJeiACmUkKMx+htOkH1rs4iZBxcHAeYuVxulvWH85bZG97D7ToquKKHueX1Pk lFN8kLGNmhMyWuEW9naFS2tZNEcZaZxJJ15v62fmdI/9nL7f7B016s9yFPqsuAJBVeWp J7DDQJ+eg0zNOVy9VXYJcD49gCxs2YjRRAYZ5bdF81MdpjMbtJCrp9annfGg9CPYqvAR XdXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Ox1ZuBNe3+SuVNijCiTalg3PzrxSVjSGxx6zLZrKxTc=; b=anDtucv9nzR9NLuBRhwjnz4HE/zwYj9aL8ITTPItX7VUvVASN8pX9LL1e/mlDYe2iq IYRQC6PVSoDHTq2y7nBfdEZI5pr92uxP0J4VYPqLpHtO5Tkz6LoKrw29Nk88tsWGaum4 W+OD6YK4LClNCNIMzWkWGeFyp3pldOzBUfVhbZ3eWrVwVkuWJAqbrkPPXSRC99uNY91N TdngQ6A/B0q017OlZjLtbt+iHIBP/hjcqyxUSZ4gswrrf1YdKUuhPSLOC1i7yH1knfdB I1IZg4XkpcpbPntOz9lkYPZ1Mw7Y8ZmSXSAgSc4TSc/3CYFSuqu44FCCVzbLrxhTdcLX /rxA==
X-Gm-Message-State: AOAM532cCK+8a5hqL5aPa3qaQkrwO1ICkZK59orU2BSz0TvAha5LN9W1 QPtjo7amW/arbFyPoGlZJjiwtOCJJlZTCw==
X-Google-Smtp-Source: ABdhPJyx5nMyJn3p8blsv3aKMcj5IgxlEOpbpKsChWKwKH8To+CLSnuE4/kBRFQTaVojpx2yAgPUJw==
X-Received: by 2002:a63:496:: with SMTP id 144mr1734875pge.353.1627881017836;  Sun, 01 Aug 2021 22:10:17 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id b3sm10157881pfi.179.2021.08.01.22.10.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 01 Aug 2021 22:10:17 -0700 (PDT)
To: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, John R Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com>
Date: Mon, 2 Aug 2021 17:10:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1sCfm01NnR1eFlkHcA27pMCJIPU>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 05:10:26 -0000

=46rom a brief experiment, the xml2rfc convertor at https://xml2rfc.tools=
=2Eietf.org/experimental.html simply can't deal with the xml files at htt=
ps://www.rfc-editor.org/info/rfcXXXX, right back to RFC8650.

The specific element causing the problem appears to be pn=3D"xxx" which i=
s like anchor only different. The published XML is littered with pn's.

Regards
   Brian

On 02-Aug-21 16:10, Martin J. D=C3=BCrst wrote:
> On 2021-08-02 10:49, John R Levine wrote:
>> When I run rfc8799.xml or rfc9001.xml through the current version of=20
>> xmlrfc, it says:
>>
>> Error: Found no element to match the <xref> target attribute 'section-=
a.1'
>>
>> When I look at the XML, the target is there and this presumably worked=20

>> when the RFCs were published.
>=20
> I think it would be a good idea to add the above two documents to a tes=
t=20
> suite to avoid regressions. And use some kind of continuous integration=20

> testing (if that's already done, that's great).
>=20
> Regards, =C2=A0 Martin.
>=20
>> Regards,
>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>> Please consider the environment before reading this e-mail. https://jl=
=2Ely
>>
>=20
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>=20


From nobody Sun Aug  1 22:34:24 2021
Return-Path: <krathnayake@ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01CBC3A0A1C for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-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 Ie8PV_M7RXqj for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:34:16 -0700 (PDT)
Received: from [192.168.1.198] (unknown [124.197.12.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 7619C3A0A1A for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 22:34:16 -0700 (PDT)
Message-ID: <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org>
Date: Mon, 2 Aug 2021 17:34:14 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.0
Content-Language: en-US
To: xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com>
From: Kesara Rathnayake <krathnayake@ietf.org>
In-Reply-To: <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/TlnE0SXWXiidN1vhZZbmY5lqAcM>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 05:34:22 -0000

This seems to be introduced with 
https://trac.ietf.org/trac/xml2rfc/ticket/581 by restricting section IDs 
to be in `appendix-A.1` format without a backward compatibility.

  --Kesara


On 2/08/21 5:10 pm, Brian E Carpenter wrote:
>  From a brief experiment, the xml2rfc convertor at https://xml2rfc.tools.ietf.org/experimental.html simply can't deal with the xml files at https://www.rfc-editor.org/info/rfcXXXX, right back to RFC8650.
> 
> The specific element causing the problem appears to be pn="xxx" which is like anchor only different. The published XML is littered with pn's.
> 
> Regards
>     Brian
> 
> On 02-Aug-21 16:10, Martin J. Dürst wrote:
>> On 2021-08-02 10:49, John R Levine wrote:
>>> When I run rfc8799.xml or rfc9001.xml through the current version of
>>> xmlrfc, it says:
>>>
>>> Error: Found no element to match the <xref> target attribute 'section-a.1'
>>>
>>> When I look at the XML, the target is there and this presumably worked
> 
>>> when the RFCs were published.
>>
>> I think it would be a good idea to add the above two documents to a test
>> suite to avoid regressions. And use some kind of continuous integration
> 
>> testing (if that's already done, that's great).
>>
>> Regards,   Martin.
>>
>>> Regards,
>>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>>> Please consider the environment before reading this e-mail. https://jl.ly
>>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
> 

-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF LLC
krathnayake@ietf.org


From nobody Sun Aug  1 22:39:21 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932313A0A60 for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:39:19 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 JNRD6_EXBaLi for <xml2rfc@ietfa.amsl.com>; Sun,  1 Aug 2021 22:39:15 -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 7F1643A0A62 for <xml2rfc@ietf.org>; Sun,  1 Aug 2021 22:39:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627882752; bh=k/Q/gMWDTM0W/Q3z0pCN2zjm5VtMdx4BSIinDSUfrQ4=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=BWvGzuCAxYxUq+Kt/GQ0BJhM8NAnzpxcx3khNsU40Dxj5kLF/wDR5bEnyEPmgsznO t/6LUt6pIz86cWUSdO+I814wa/j2wK3Z1TmnWed7zxQMleNg/2UBySPkLY1GdXoxkM 4xGxZiEEZZWZm28OhpMzuFAsCDyqX+Ob52hHh45I=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N1fn0-1nCCTY0r8a-0120QY for <xml2rfc@ietf.org>; Mon, 02 Aug 2021 07:39:12 +0200
To: xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de>
Date: Mon, 2 Aug 2021 07:39:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:1rkSK75frImuWkZTYB7S0QpnljaJOb9AmRENKrNuwP1eIl8DL3d PSeEKM/XVZQFEbrYsSbATBgHLZMHoXM+ca2CoIruBMkWtHbZ1BHp01gf0MSUJbpVKVd0xv5 EyQPzO4OEytooAXagBxrB7Uk/jOrINT+VZeokSGNfigaUyfU/9BTsZMQ1C7tu7bZL+mYmre O5nohC6PBWexz5n+g4sWw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:sfRbYYBx4uA=:/tYuN+qpEpywpmnKwbXgYz oqiEJEoqNIcjQ4lMm+uQEk/ejLS5sw9RUk/s50X/jJuCAaG/AQGiYt8+leFoVedJHAlucdnh+ mBVssI0uaER5qi10Mic0UFUAPjl3carmLRkvTtKfCdk6m8AEhOHsA+G6fejBznQxTnXpGmiJL H+Tn94U9J8Nyrzq1efQCN76cYp732LIHe04kVvBFC/DU+osTjIrJxxaSOGkl4IM1pr8hC9Zh1 HmmaYA8fTPkxMxcCGXLwzogD5El1POeGqjYtO0EwgMEtYgzTuaUEZQQUcLSyS7D2oGB5jlyjF OkQE0MkqstcA2FRvWJjWpTyMrZSB7Fm0d/2DWPfTQ1ZBJPUMOFtXmB8plTDbV7aNDFW4hd5Dw OlU1hWDKxHJjiDjC7b82MiWsiU+HOUgAC6V0tvRGlOrGIHq0jzFWqma34vtQnz+vxhjWAMoir LbYRoBEG8GrEhMZtM3Bh+or3f4VO7WYtujxwrJkfM5bmwRL8CiRBPdcP3nZPcJkKuozo3Kcoa WymIP8SpHjY+rcJ0mHnFhjYrzWndhQtNXJvx4CIGdJcDh3Zhd1/tqmNauNXcU1eFm6dIFjTfC Ohfm1P2wb9ZfedR0h38PduSoqlIosdpQNoMzMxgTcrvXWe0nXHSCfJthUlym1HnvS/p3Iwqjm d9qLo6d7f6WM4JMEGm1A2c1wCy1XDy+YmvVIZGIjy30v0kgci2jwtaEss1h2E02SH3BUZ4cyS 4pimWitP6042kR8dFnIaQ3rBii8wdgW8cgjJ+YHxFs13qMPj/VdTUGAEYJw/OOxUoliuDLZte JLCF4r44ohHoT+QGyFnWRbWTQ5AMNmmxEQZeRxY5m0Prn5hIE9spJlYoIT1PcAR5ui4ZZ5sez MOIJXPX6fuxYpXZSHXhs7GCMC9dwBKsEpyhAJWr3Ase1B+3myI7jaC32/0GNDjHOX9OeK5vcV 0clzUUe0h9ID+c1AX36+nJNAgdKGD8gkYMpJFIzN97DpnW9azdByqIHQQfXmhsM8f/ycpbLlA Z52lZqGh1vbcAlehYy6JFX1TXgiduxSta6fkeXa4h1XsWyAtdqfvQSUAfvlmfcLF7b0Qjvv4d E8IlX/fNY2D3tvwQk2zNJAAgqn9BHRhsrp7ctdrv8uiOHE8ZPrzID1j2w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ygBzILsu7Q1t4kumsvw1FX8X6qE>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 05:39:20 -0000

Am 02.08.2021 um 07:34 schrieb Kesara Rathnayake:
> This seems to be introduced with
> https://trac.ietf.org/trac/xml2rfc/ticket/581 by restricting section IDs
> to be in `appendix-A.1` format without a backward compatibility.
>
>  =C2=A0--Kesara

AFAIU, this is because of the inlined Table Of Contents in the prepped
version...

Best regards, Julian


From nobody Mon Aug  2 01:08:49 2021
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0E53A1292 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 01:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.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 uaZImjySDF_s for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 01:08:43 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 D67273A12D2 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 01:08:37 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id b6so9398844lff.10 for <xml2rfc@ietf.org>; Mon, 02 Aug 2021 01:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S15nSbE/uY31V+aSkxNK1+i33S/XQWUbkINeNlFSfsE=; b=IHvXR5VyqM+IugJ79STNiiAvTy7u9CjO1Vk/R/6sDbeAzcHAKTHobSzfgZ1d2irOV/ 1NiONyDHDYyH6QSGMLhlvy/nmmUwu0Fb2Uu2gX3nHRWS8AWxK/4fQXBVzskn/m7rNzmg Bsyj8jI7+BVeJBghpopBIU47OXHpW0SW7CROFBgc8k54sX9siWui21kRTxk479vEoHH4 pDxtuNeC4O/rrp77b7IqiTYs4vql0pKe9MTKOyp2kZXBhRhrQ3Mai4JJeXO668BWjN/C SJUtUklK+ZLX25SIGFMMz4T1exxuFetUe3deUS/ZWSRz6M8H6A2C5g2LQcTytIIpcEE/ aCiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S15nSbE/uY31V+aSkxNK1+i33S/XQWUbkINeNlFSfsE=; b=AeuVMsk+I9mXwKqVz7eKeSfHGvfozBc6krnDRCbjG2LRP7UQzCD0M9KGMeFtjYy2WY pvN8HTO7NFtkgkl2/HSnE3rc1abbb3RCg31DvGiHHJVeudqLl1wDWWaHZDrbjD30vE73 74iBAQOOTrbLgyWJUUt6Ae2+ZY6sISfj+/CAYKz0PjIaZBH/A5b1Tv9pOgpFtG3w4o1H N1DsfwyHY7WGsXUnpCbLAnCMH7R+SnwQO5588wu/gwzP6TIemiHUKPWnknuTHEGMMdTW GbU+kQV4UIb6KzrJ9+lh5fQEhTdxrs/CVHAXLDi1IB27GjXS5ppwvOhoMh8Rv+aXDJ8a d9ww==
X-Gm-Message-State: AOAM533FSlMj02/lpGdcif3BFL5iyD6TSJ5jzrpyeq2sgMplhhDk3HBC towLNq6kxMOTWL/+T9utFeaY5gDWeJ6dnsRIxKA=
X-Google-Smtp-Source: ABdhPJxVnLp5dYbhX/esOLtzyjz9sOLvT4Z3ueKmnbirQ0ufNSJV7HxEsPxwwoTjW6TrGqD/gGupsiA2SmkF1j+pilk=
X-Received: by 2002:a19:8c07:: with SMTP id o7mr11592041lfd.637.1627891710722;  Mon, 02 Aug 2021 01:08:30 -0700 (PDT)
MIME-Version: 1.0
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de>
In-Reply-To: <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 2 Aug 2021 20:08:19 +1200
Message-ID: <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc <xml2rfc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000026861605c88f136b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/AQt_K-R0ws7E8xQEoUOGC_4OczA>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 08:08:48 -0000

--00000000000026861605c88f136b
Content-Type: text/plain; charset="UTF-8"

I think that's a red herring. The processor is not recognizing pn="xxx",
that's all.

Regards,
    Brian Carpenter
    (via tiny screen & keyboard)

On Mon, 2 Aug 2021, 17:39 Julian Reschke, <julian.reschke@gmx.de> wrote:

> Am 02.08.2021 um 07:34 schrieb Kesara Rathnayake:
> > This seems to be introduced with
> > https://trac.ietf.org/trac/xml2rfc/ticket/581 by restricting section IDs
> > to be in `appendix-A.1` format without a backward compatibility.
> >
> >   --Kesara
>
> AFAIU, this is because of the inlined Table Of Contents in the prepped
> version...
>
> Best regards, Julian
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>

--00000000000026861605c88f136b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I think that&#39;s a red herring. The processor is not re=
cognizing pn=3D&quot;xxx&quot;, that&#39;s all.<br><br><div data-smartmail=
=3D"gmail_signature">Regards,<br>=C2=A0=C2=A0=C2=A0 Brian Carpenter<br>=C2=
=A0=C2=A0=C2=A0 (via tiny screen &amp; keyboard)</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 2 Aug 2021, =
17:39 Julian Reschke, &lt;<a href=3D"mailto:julian.reschke@gmx.de">julian.r=
eschke@gmx.de</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 02.=
08.2021 um 07:34 schrieb Kesara Rathnayake:<br>
&gt; This seems to be introduced with<br>
&gt; <a href=3D"https://trac.ietf.org/trac/xml2rfc/ticket/581" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://trac.ietf.org/trac/xml2rfc/tick=
et/581</a> by restricting section IDs<br>
&gt; to be in `appendix-A.1` format without a backward compatibility.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0--Kesara<br>
<br>
AFAIU, this is because of the inlined Table Of Contents in the prepped<br>
version...<br>
<br>
Best regards, Julian<br>
<br>
_______________________________________________<br>
xml2rfc mailing list<br>
<a href=3D"mailto:xml2rfc@ietf.org" target=3D"_blank" rel=3D"noreferrer">xm=
l2rfc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xml2rfc" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/xml2rf=
c</a><br>
</blockquote></div>

--00000000000026861605c88f136b--


From nobody Mon Aug  2 02:25:25 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8FC3A155B for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 02:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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 GKb0AGv-Ozbh for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 02:25:19 -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 E27493A1558 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 02:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627896313; bh=RY0SBm4NCWxWMFL/TgtDtfDaePenDJ55pa3h8+t5m4M=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=iOzGPuiVUjh0EvYpyty3WrA/6gE+vag583PEwRBB1RDaEg/AZxGRWMnyujmo6UTxA /ExvzVBeu3m27AcOEjX1nsQzhOmba15gL5PZ27jmPTCmxrJCTlDA2mCComzsaQOZQ9 yxqwpS4p7pGW5tSQfRiUs0uvp7CG4KxsZYfpv/P4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1McpNo-1mizvu3qiY-00ZvjN; Mon, 02 Aug 2021 11:25:13 +0200
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: xml2rfc <xml2rfc@ietf.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
Date: Mon, 2 Aug 2021 11:25:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:Vd4JGcEKl2EGXmnyzist1OODJAHdI2OrTtxea5CiafiChr7Ba/J lIZ2YSWiT0sxYWaJR4vptGW+g1S3etIXjKMbbbeNbP+FkGOXYEANFiJAE0BEtk8eh60AHWB BgCAQ8/7gQX9bIIVpStmKKGx2aJ2NRtMmy0nE2lxK135ovNavvDThPc6rvH7ICJmL7DOzuJ pUqOSW81W4yOYF76cGLsw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:mruVBQ6xZvA=:VfG1Gx7zemvefa5slpVM6L NhZZDxz5lhw0sz9xjn/ZLJWIqlxzw1xOAjBIhGU49qAppO/QP7I420pjh+nAudSlwB02DCClX Wa50lKTpozUYufdkD8c3loAzPZ63hX6QgzC1paARX0XVBvP/n5ywssLaDzS9w1vuQOhBu4WCo 7Z+pcUlxPDeh3oCA8vs0vjiK+YzQWWEl+QtN2Fhw2PoiX3AmHRSpBcBpXwNoOR34MV07sXhw7 dLz/+GGhhMDTTl5EVgsM9HEgTPpVuWEz9mS0tu2apOgeWVu2LfquUPXRGIIDr1bn5GvZIC0/R sCKd3l1MydyUn/41avPi7B/pCHg4gHk3Xyqt74lQn4MXtPdgKkFgbJ8rU7p+/JXzKGfpjF3Pj G2d5JNjykCRU6bCR67zdgNv9oHwqRNfcxd2hv8bbxyS8vA2goOpmasWk3v6SNcHfQEtnWL7vw fuHBjAfqs+sV7pMBarNEVWm2YC7eNDYn7tF9+xApkgNZwosnRokPkDfP2Qes7PtyEECToFWRc dakuPWQt32+LuBw7T56sP8PicqheC0j/zOpWSukh12wvrdYqRrZNJMr+MUQjoH4UEEJG0lEHo xQIsZKYRPJhR7X7dxw2JqHXuAqr2QZayzIX+IgvPnUynqc75R9i3ViwuaEhYLisX5hoNspCGl v0O814wfoA3SxTFDR2QhqH/wlG5g0kIK/WfUExLJHmfYN/5ggdfu7dWAQd3VuIEXwoZZ/cRy5 JVKCSd6Pxdk+GFidqUpNDKyjuPluLdK/uGV0BD1Mo5xI4Z3A9BGn3v6c037tkaVId3oNoI1vT z2E0jeqsPbF4/PJxqrFNv/AqkzSPHcfzVmvK3Jy+J+EZtpFDknQV+NNYiE3w+42WBMEiWrXPk xOHVPQlnIRIBekDI14gIcuPKpVvRCXoZ7zOGGM4QQBCiNh2ux59frrgsvNV7wpPc8ypZBAkrK aO4kSyv69I3ygz1WxWdWuUkzk9FSzKzC2RnyvPkJsqRTEWlndRouY86Buxzubx4C3+rNPmRYp 65UHTjWbU4/vEyXE5vSmcDYYvNgTIY+efRchLdFmZ505wzJbvV6+P3jx0fMUrDznjvB72nRVv Gbc991QBopM7WlkSbdFtDjLGDdC57zYZeLMNwTfVLGc2VClXU1UxozjHw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/cFQ1DqhdFKdutmCUqUhSHZVHVCg>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 09:25:24 -0000

Am 02.08.2021 um 10:08 schrieb Brian Carpenter:
> I think that's a red herring. The processor is not recognizing pn=3D"xxx=
",
> that's all.

Nope.

The issue is that the document uses xref/target to point to sections
indentified by their "pn" attribute, and that one's value is different
under the new version of xml2rfc (and gets replaced).

We wouldn't have this issue if the ToC wasn't inlined in the first
place. So a bad implementation decision now causes breakage in
"canonical XML".

This could be worked around by xml2rfc rewriting the inlined ToC as
well... (but that would be a workaround on top of a bad implementation
choice which leaked into the user-visible grammar).

Best regards, Julian


From nobody Mon Aug  2 05:04:04 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE463A1A81 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 05:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 85xW9r1g9g6g for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 05:03:56 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B10D63A1A7A for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 05:03:56 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Gdc9P3LXCz2xJ5; Mon,  2 Aug 2021 14:03:53 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
Date: Mon, 2 Aug 2021 14:03:52 +0200
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, xml2rfc <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 649598631.553569-67abe4eca030b61bf3e26ad793114bac
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B968E22-B4BC-47AF-9A4C-53015726CD2F@tzi.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com> <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Jipcr3X9xkmIGAMyFe4jn7sSmq4>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 12:04:03 -0000

On 2021-08-02, at 11:25, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> The issue is that the document uses xref/target to point to sections
> indentified by their "pn" attribute, and that one's value is different
> under the new version of xml2rfc (and gets replaced).

So you need to unprep the xml before any further processing.

I=E2=80=99m not sure we have been told why there is a need to process =
the xml again; if there is authoring involved unprepping is already the =
right way to get rid of all that noise, so I don=E2=80=99t see how that =
is a big problem.

xml2rfc =E2=80=94unprep rfc8799.xml
=E2=80=A6 edit rfc8799.plain.xml
xml2rfc rfc8799.plain.xml

If this is just for generating renderings, of course xml2rfc should not =
second-guess the previous output of the preptool.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Aug  2 05:13:58 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDF73A1AC9 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 05:13:56 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 WZfBdGAPxS0C for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 05:13:52 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 8AA053A1AC8 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 05:13:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627906416; bh=OMP9dTXnYNbVnXw0mknD4G/QZbUYRWIOzcw+A41R1dM=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=A5qyuB40Gl0Esar+A3weo0kZbsHIlgx3Y0mGM8mvGebbAmt1MZoQRjER7WE2K+O9x WH72F8xsIk8aHts/H7v8ujTDJ5ep/oU9/8eAhhnyxru0w1uZLSQJpxtYIU8nuxAUeX ZYxJXJILcF8sIs5eEIUYcUcL12jAXodOrMRNiHck=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MkHQX-1muHpR0Qsj-00khtL; Mon, 02 Aug 2021 14:13:36 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, xml2rfc <xml2rfc@ietf.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com> <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de> <9B968E22-B4BC-47AF-9A4C-53015726CD2F@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ea1a79db-8538-2f56-dc6c-ec1ab2fd2832@gmx.de>
Date: Mon, 2 Aug 2021 14:13:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <9B968E22-B4BC-47AF-9A4C-53015726CD2F@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:pY5eMXpGzxUwjJJLQkbNHA40M9+FU0EB0pGX/pp0qsxTVKOcRne hbwBDjk6ZQrSEPIbov+tQ7Da4LEiYiOattfZC2zV2dnUoJUUZ9wTY0/y/sKWWZQ2/z5PDEK uoSicSTXF3PU2EeZsdlSop29qJs5P/1P28Qg+PcBf4up+/MgDCnUCltBCI8QDgC6yZyMbiW fbeHSyosOvVDZVp+RyKwg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:jxICtTA00UE=:Zj5gOR/wb/P0mDLr3gFsQ3 ASnWfX8NZ8avpM11zudgbdL9i+dO2s6QE0JPuOjEsGps6rGbDCL1Jrd5Pkwf9esGakSESZfhX 6aKLN8f5uMkST4b5UYY/ibMtd7xRpFDi8lSx55h2+RNrwR2Wd1o3IpGNiRIPx9F2qM7hPgLua 4sQngmAhZAxeMNPtTJTipGE8ec05fPAR/7URCVpdIGFCG1TTvfFqwTsb21zrBr9Sa3gkDr3YU gJHLseHGopjJHknaVOLo3ZDCZu8Zfl2f2+AmX+5/zVPlbYgXwcJeBmw5dQ2ULvRJHKOTPsUsa AVuhVhSy4fASGDLFuyiFR2Nn/v4tyRYJVmhsHNp3h3tlvaFDmQ0fqM+6pLpU4BNIGmnT0GFrh BXCcJNSX8gt1q7h7t4MasktujcKQwHgZTxQ8JW8uuMqUU47ss0ETF0uzvIrfk/HSPHnlIrP5c uJkzOElGJ8i9vOBF1CPRe+bW7MBwi1xz6C/L1QW0VwE54zKV+dSPpwRj2XWd/wxanRDtnw78v RyQl4U+MUVaNvMNQXmOfNDJky3s3B09WGevJNt4AcS707KffDMv9zXRKjmSJRleD08VY32lU7 37O3SYYOmcFcLZUhE0xYi8F8AYRzWdDfibNHA91m8qxNoy6BDd9b9ftPKwKknLTdGoSZR7ZVR z5y2LrMQuPzgVdhxItRHL0ydqHcHzKapgCcCfsjI1nI4emCWY4IwV7umbljPCg17yUA7DfBQ6 zntnE6wTJHwy082ph1GIMytQ1YsLFnsH5XL6v0pARXLVdl2tmIXhQgUxIMeTrtsi+w/5T2sut voJVS5jJmVhhh//5/DSGDBvPYqah773F6AKhN4ikWo1T+4QSKjxU32g0JNaYJ7BSqKfbHe5q1 9XZlx2tYkHroAvs+CIFK1koMBPZoBa0PIKl38zHhrlMOQEb/tiWOgmZKxjSDMMwRFfH5cac+o CRXE0UzavZLjdZB6+zLhwGlamaWkiYyLvCrbfORQX6ZNlJcvVHlLDdmdN/daYAtZ4WzhElI3M L7REMUg01jU0/w73Ge6f0BV5N8qtlKD4/xdOPdv7Xg0DuZ+o01nGo7Tczb9P6FG50SJ0YTnSG wH9xsmIGC/ztEHZNx/jygCMe1pDdDuqufjCUZzXIJkQTpcPOvi/1suN3g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/kSoLYKr9shHvPxTc8j2M-0W_KBw>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 12:13:57 -0000

Am 02.08.2021 um 14:03 schrieb Carsten Bormann:
> On 2021-08-02, at 11:25, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> The issue is that the document uses xref/target to point to sections
>> indentified by their "pn" attribute, and that one's value is different
>> under the new version of xml2rfc (and gets replaced).
>
> So you need to unprep the xml before any further processing.

That's possible, but I still don't get why we include the ToC.

> I=E2=80=99m not sure we have been told why there is a need to process th=
e xml again; if there is authoring involved unprepping is already the righ=
t way to get rid of all that noise, so I don=E2=80=99t see how that is a b=
ig problem.

If we need to "unprep" the published XML before doing anything with it
(like generating new HTML), the whole concept of sealing certain
auto-generated information in the published XML becomes somewhat weird.

> xml2rfc =E2=80=94unprep rfc8799.xml
> =E2=80=A6 edit rfc8799.plain.xml
> xml2rfc rfc8799.plain.xml
>
> If this is just for generating renderings, of course xml2rfc should not =
second-guess the previous output of the preptool.

Which for this specific change means that the "old" documents keep their
old anchors for appendices, making them inconsistent with newer ones,
and making it impossible to compute the proper anchor without additional
information (such as reading the actual XML).

Best regards, Julian


From nobody Mon Aug  2 07:48:10 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB7163A0743 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 07:48:08 -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 MOvo3_HgxZne for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 07:48:04 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30CD43A0745 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 07:48:04 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Gdgpk6p7cz2xKW; Mon,  2 Aug 2021 16:47:58 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ea1a79db-8538-2f56-dc6c-ec1ab2fd2832@gmx.de>
Date: Mon, 2 Aug 2021 16:47:56 +0200
Cc: Brian Carpenter <brian.e.carpenter@gmail.com>, xml2rfc <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 649608476.3976409-406a1ada1b344985c48ae8f67eb2f667
Content-Transfer-Encoding: quoted-printable
Message-Id: <F17E5E5A-06AA-4B9F-B5C5-57FA3B49D510@tzi.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com> <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de> <9B968E22-B4BC-47AF-9A4C-53015726CD2F@tzi.org> <ea1a79db-8538-2f56-dc6c-ec1ab2fd2832@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/0ILN4Yy6QzDgRzZMVc1HC_FJwLQ>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 14:48:09 -0000

On 2021-08-02, at 14:13, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Which for this specific change means that the "old" documents keep =
their
> old anchors for appendices, making them inconsistent with newer ones,
> and making it impossible to compute the proper anchor without =
additional
> information (such as reading the actual XML).

Yes, which might mean that this specific change maybe wasn=E2=80=99t so =
practical.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Aug  2 08:25:56 2021
Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B433A09AD for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 08:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level: 
X-Spam-Status: No, score=-4.4 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, RCVD_IN_DNSWL_MED=-2.3, 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=iecc.com header.b=mQdcseqq; dkim=pass (2048-bit key) header.d=taugh.com header.b=WWtjr/3X
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 qzOqgIKVIHZg for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 08:25:47 -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 70FB13A09B5 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 08:25:47 -0700 (PDT)
Received: (qmail 50440 invoked from network); 2 Aug 2021 15:25:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=c506.61080e79.k2108; bh=EZJq0VrQrzxvWnbSrVnsme7C1LVdcliFsFcMBNldzK4=; b=mQdcseqqEsfHmmvz7VIxAuo0JVVz57B/NjX4GnAc/TRrDpP64MG+DJOcIEji6llJaJRQEwDUXBNBQkVskLbf1ih219f2wf7p63sYAvED3r3+koU1RifQBs2kyinKCp6ngJVVkppTURTs0hX1WjTTLLXjuPCOFYud3AkTDJn9yLoLlLHxdhtGuNpAUHDkrvPtia0sGlU1nqjbnGlg+7ce8sFqzQs5av/s9YbORxBp4BQApO0diy2OreAS60rlDlk1JyIwdSrKpikcbWicNzpreaAqP3D9MhyTWGP051m7ONCqsXU/dU+qKHGW9yqjnwv/cQDaY5wJz3G4ZWGqhr9Jbw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=c506.61080e79.k2108; bh=EZJq0VrQrzxvWnbSrVnsme7C1LVdcliFsFcMBNldzK4=; b=WWtjr/3XyQpC2k/NsbVMI9V87P0wS2o0sr46lkqsbJyIzZFH6BAwnP8p4BgpfwR7/H1ho2d8eBe8N8nFP76rNlMf12rp6hP8UP43GeYAA2pOxsPzHnDti3bPPzusJpMhUeJU5U6XF5EpbCGYyrQW2NdbUhWqT7/iqzfAJtd3dYD2w2Dvqnw8TakQluP9GLkLR2qQXLUhVu7ewKBbsbN64jjXxu0jSCsiyAXIw3t71ibufiG1Sq3J7smpLstmcDl38JE5qXgBIj5vywFURBsvhQO7abylLBqboZ2xBG49R7Sv0zgTO0fHugYwjTGxPW6qtVXXdoC6ybnV5lwlK8ngGw==
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 ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Aug 2021 15:25:45 -0000
Received: by ary.qy (Postfix, from userid 501) id 95DBB25769E9; Mon,  2 Aug 2021 11:25:44 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 6F64825769CB; Mon,  2 Aug 2021 11:25:44 -0400 (EDT)
Date: 2 Aug 2021 11:25:44 -0400
Message-ID: <98df983-bf39-6521-dffe-86e44015db7f@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?Martin_J=2E_D=C3=BCrst?=" <duerst@it.aoyama.ac.jp>, xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1601401194-1627917944=:60450"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/2iRK2NGnfswPpLHeo0Dl2daF22o>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 15:25:54 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1601401194-1627917944=:60450
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Mon, 2 Aug 2021, Martin J. Dürst wrote:
>> When I run rfc8799.xml or rfc9001.xml through the current version of 
>> xmlrfc, it says:
>> 
>> Error: Found no element to match the <xref> target attribute 'section-a.1'
>> 
>> When I look at the XML, the target is there and this presumably worked when 
>> the RFCs were published.
>
> I think it would be a good idea to add the above two documents to a test 
> suite to avoid regressions. And use some kind of continuous integration 
> testing (if that's already done, that's great).

Not just those two, all of them.  I've run the entire set of published 
RFCs through xml2rfc.  It takes maybe half an hour.  We definitely should 
do that before releasing each new version.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
--0-1601401194-1627917944=:60450--


From nobody Mon Aug  2 09:42:43 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01FC43A0D38 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 09:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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 V6RFh6Io_w-F for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 09:42:20 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 A28403A0D34 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 09:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627922536; bh=Hnp11pvtje9wiBaOZtwFjAfq1kUG6IcpmRiHoW2qkb8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=TFgGnWOx16dzz8Su9NSAy2jmcjjD2BHwhKjUCBvcgngnML06bqpi8f+oOYDChE6xl 4mJk6jHBl4tF9jtNEn1nMO9wuDjnoMhShCycW6nVz+6vBVLuhfRPosM/ukboNddm9m DjSkyyXjzj0jnAMPMhaCRxEHABj9Njc3YH8zgXOg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.1.70] ([212.205.152.82]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MuDbx-1n0mvd0PID-00uZiM for <xml2rfc@ietf.org>; Mon, 02 Aug 2021 18:42:16 +0200
To: xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
Date: Mon, 2 Aug 2021 18:42:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <98df983-bf39-6521-dffe-86e44015db7f@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:nnOuf2JqbdgXprRiuaYUjBFeykSSCz2wQwPGtQ5OqY0FZGgt8nE iFEbkFG0qT1xpg0TAQ2//Zz5TFaiqXHE3eFR+BfLkhwLYfoSUaOzeV6bkhXIbWUjNJPqDuw FXh3ShEskl3Zlku9jet7qjESu96X+BAUTxy0v+j3jHVnxYncGXIch7m1cTuXNLl3aM7STCa kZkEYU32sCnL9+nWyxm3Q==
X-UI-Out-Filterresults: notjunk:1;V03:K0:CYIcfZi+AWo=:MVf8GFm7UXi0NrxkeE4/om SVfH1HCPCL5u1i437fOZnhiuQSCNdh1szeKpGwU/oGFD9spGb3MpF4H4Q1BOBYo/H+MUXF5DU Rnr5nEXAY3s8nA8THVT6+a2xnHidExQBbnsuGvBrecebctrz3prK5yhAbMFczAcQ9JUMANq39 3EKpvU1+Z1FKeDwh3a3l3Zd+GSmCSUdM74Ffbw9Om5axQh/uYgnbcwS1qnTrzfPmvTdF/FwvA ud7UB6d3QAzM54s1Qr1edQpiG4KlUMNVChsVPjrSThVbmX5ks+l8tw7M/f8gdGD1kaHgX5VsD RyLS+jnB/6otcBJw+HcOQOgX5zznUDO96qQdXOz8as1ZwWXMTQBN1og0g20k/aSgmB2q/y+gH ft4w+c3RzJOLwCooNYLbCW0TCCq6cxh69fedEy98KqI2cwcgpjiaL38uRMab7nRj5EABfxQJm X8HAqhWsRNHQ4S7UT4zRxP8FlJ3qSICtQo8RGVquimozd0GGa+epDx3N3g9tpFvcU9IQMjw7w S7pI37ASRjxcoPagKRx4TzZyH6MNkmKfBtJfe1jh+3yBmu9f3PA0+QtcoL5ogg/RLPuo44TiM 8VO1MQwrqu09tXJ6sgFCW9+Ovnn0hc66VMmpAtbBdgE2avRSoh14lwOJ+/CGG6mkI0wWNK6hC OB2C04AyQus2GB8xLCjMs2ZQhAsGPLhpKgWupNNT2ZkXdMGppswoolM0OrKcBcQud4gC97Kbr THRCcGlF8q5VJqXHQGOA+o0XDPEL3E/TdtMYJvsrxdQZGg6BH8ceCl1DYdLUZLPs/7yfStjRA aXt/NwZrT7A6J63C5/RHbUPQr+KuzdnwC+JDNgyJpLWP7whCHEitPPdwcV/X1a+ep6XUbst/J 4abHTt0VDHmLTiQLaa9G5c0eXjRcFuHk6AIsMRA/SacQhKRRd8fi3XLTTJ/3V89za/U1Z51dH gBlFCZXK58RwofCwqVOM61d2ZJhs9/6uJnpbXiZ+Rd+6+GxeNQJsS4xe7N6C/XC1udM2mtqCJ El27EF6L6OXLzOV9hT3upRPDTKshAgK0ulMV1LTqQ0whXbG0TGF0By3q2JPOP7Yoacj2rBPDU f3DNbZGx9mrdslm0Zkl8Xs0z63CEYgtLfdc704+y85FdmtyQo6hPOvVOA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/tXRCifvNQUQ2xvg8nSjvVnZaUAI>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 16:42:26 -0000

Am 02.08.2021 um 17:25 schrieb John R Levine:
> On Mon, 2 Aug 2021, Martin J. D=C3=BCrst wrote:
>>> When I run rfc8799.xml or rfc9001.xml through the current version of
>>> xmlrfc, it says:
>>>
>>> Error: Found no element to match the <xref> target attribute
>>> 'section-a.1'
>>>
>>> When I look at the XML, the target is there and this presumably
>>> worked when the RFCs were published.
>>
>> I think it would be a good idea to add the above two documents to a
>> test suite to avoid regressions. And use some kind of continuous
>> integration testing (if that's already done, that's great).
>
> Not just those two, all of them.=C2=A0 I've run the entire set of publis=
hed
> RFCs through xml2rfc.=C2=A0 It takes maybe half an hour.=C2=A0 We defini=
tely
> should do that before releasing each new version.

So if anything breaks with published canonical XML, we can't make that
change?

Best regards, Julian


From nobody Mon Aug  2 09:58:41 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9CD33A0E60 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 09:58:38 -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 kbTL2FOFgAP7 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 09:58:34 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 352913A0E5F for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 09:58:34 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GdkjK4xXDz2xKK; Mon,  2 Aug 2021 18:58:28 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
Date: Mon, 2 Aug 2021 18:58:22 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 649616301.944831-f8e47cca92cc6a0f6ac19cc09c6d29c3
Content-Transfer-Encoding: quoted-printable
Message-Id: <F36D2C8E-E5B5-45C7-BA32-A553E2B4C727@tzi.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Zyv-LudhhTSv1iQa553-Y5SP3Wg>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 16:58:39 -0000

On 2021-08-02, at 18:42, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> So if anything breaks with published canonical XML, we can't make that
> change?

I=E2=80=99d say, if a function of xml2rfc breaks that we need to run-on =
published v3 RFCs (8650+), we should make a better change.

Re-rendering is certainly one such function.
What else?

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Aug  2 12:57:20 2021
Return-Path: <johnl@iecc.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2123A19F3 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 12:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.707
X-Spam-Level: 
X-Spam-Status: No, score=-3.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, PP_MIME_FAKE_ASCII_TEXT=0.292, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=MdAXytMr; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=lOScLtr9
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 JtAr6IquaQ9n for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 12:57:04 -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 8F69D3A1A3B for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 12:57:01 -0700 (PDT)
Received: (qmail 21261 invoked by uid 100); 2 Aug 2021 19:57:00 -0000
Date: 2 Aug 2021 19:57:00 -0000
Message-ID: <se9imc$j1e$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: xml2rfc@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=5306.61084e0c.k2108; i=news@user.iecc.com; bh=KxPgCTexNYxGGayLkyeG+0WI4oXhpZc26z6d98JgOQY=; b=MdAXytMrbl9/Zi0zgneUt2V0IuOykl41A7GELER7CqZGmYaKOeNYmTpM1dmRfnUZGwxr6KoRkHFhuEM55tkxAKpOVedNq6ReLOqmwgsq8LH2VELhzStVR2cAYAvChs2feBWFet7Cx3EInn7oiv4r8kfARIzLSzdmutTF31VAntCHEydqwNvjuQoBZ63z46vjzgtW4jcjatNttucs6nc9qT76tDOHfPTrprqUzoX9cg702RHY3q3yQdXqSudwAOVcmxNgZgUBrKzhDHL5jKCr687bU4dztdwBs4uESPFs+1b/TOm0R6mMJ4RcSNtz32G2AjX9tTddLzh0o5fh6kYn7A==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=5306.61084e0c.k2108; olt=news@user.iecc.com; bh=KxPgCTexNYxGGayLkyeG+0WI4oXhpZc26z6d98JgOQY=; b=lOScLtr9wk3Kdm09zuwBXekLoDocjt+g8dwpuLlVlb/Tdn4nNNuGh/Xk2BQLSCeyrSmn5efWSKTajvBFVMu1BFdW9EWP8Btnh+g4bE4hD1IoqVZEgxzJqSaZZIfPbA0262DziDwqDslhb6lSlTR0o0IvvkMyiinShwTjK+9w5IesLMSrU+WQt30pqptcQafr80FxJ4Kfs9E6L6WATjqXenvOP75E8GwwOkhLKkzoqSy6BYutRkcntQGMtHujIoskTZjD/5jkrJS/DcJ9s8yAITqTyQ2/v1q0WnfXGLG1N6WeIMalfRFCvmvvU5AM+4Lha7ktMvvmOPOnRpU4Qt9HqA==
Organization: Taughannock Networks
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
In-Reply-To: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/94vl1hEk2iwfqgop1kax6XpKqaM>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 19:57:19 -0000

According to Julian Reschke  <julian.reschke@gmx.de>:
>> Not just those two, all of them.  I've run the entire set of published
>> RFCs through xml2rfc.  It takes maybe half an hour.  We definitely
>> should do that before releasing each new version.
>
>So if anything breaks with published canonical XML, we can't make that
>change?

Maybe, maybe not, but we can at least make the change knowing what the consequences will be.

This gets back to the unresolved issue of whether we're going to update the XML in published
RFCs once we agree on what v3.1 is.

R's,
John
-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Mon Aug  2 13:58:01 2021
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CE23A1C35 for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 13:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 (2048-bit key) header.d=gmail.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 lthcbnqvy3bS for <xml2rfc@ietfa.amsl.com>; Mon,  2 Aug 2021 13:57:54 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 540DA3A1C24 for <xml2rfc@ietf.org>; Mon,  2 Aug 2021 13:57:54 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id j3so6019842plx.4 for <xml2rfc@ietf.org>; Mon, 02 Aug 2021 13:57:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=dLeUe89dqdx3pR39RazUa4ShNvtf4/vurnL2CX1vl6c=; b=UlcOInM7jRAZqSG6xmsNjM70JPAL+Hoq0tdZ5E4wkz1mpFaDMnupYprku+EyB3r3tp Sf70Hb3KPAffhu/pOpHYNu0R+/fIyV7kYSCpmWWyFEMXGm+T2mj02waC0lVoVDQLwQff /wTBpAhh2fi13epi2KjxSYkdGCpKmIMRgL0gIpLxSlJcuo9OR0INlkGy/zT2hOfd64kO QLUdV+gEuisUmKyJw0o63pHdrJlfa/p9Lh1sEDcGD60TztKfw6LNFgBZbkPcd06s1IAW iIBCj6e51SpNUzoB0r0jpETqL3P/EcR7Zz+haZFdcCMV1+9A8U/W2m56eBS/QQf516OE cwzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dLeUe89dqdx3pR39RazUa4ShNvtf4/vurnL2CX1vl6c=; b=bCvrSEzjRRr0LrnsDbGQ4RMHFtOjolHFmEnTr0GxN69lPnJkXvDyW0TM97lnXomvbC CucP36cdV+bbhwyyV5DQCTrxp69045wO5wU8D9r2vUY34o3IhkqZu6VBybGpCEV+eMCo I4x+OYqCaFktC7wfB/Uqeibej4DEYBjhnCUsFMRYNhwUMaTSebOAFFWGswfjnwRkcC+l huDYB1AXn1nPAyOMhn+xnkmNMKhJSzG68/x+iQsMp/jL2pIJdUTSiHLwUMu9U75YXizp CWThK1+sLJhJ/u3rkS2pZvexCDKwiEL03YKmtV7lhfgKXLYKAOwiONtvS2Ga+09HG06C DrlQ==
X-Gm-Message-State: AOAM530qyNh5+NxLfZkEXBsAbbNsRG1Pwx6GB3dxtpU0d+5/WSFOFJ9q xA98MGg9ycHWTFTq8n9qPIOv+xt21aLbKA==
X-Google-Smtp-Source: ABdhPJyP97fysJQ5aaPCy+ROYNHxhUotFXkv3cvymbU7Lo8kDM0ctodknGvIlbdLI0i8QtGWGbaZpQ==
X-Received: by 2002:aa7:8298:0:b029:338:340:a085 with SMTP id s24-20020aa782980000b02903380340a085mr18574013pfm.46.1627937873259;  Mon, 02 Aug 2021 13:57:53 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 198sm10426400pfu.32.2021.08.02.13.57.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Aug 2021 13:57:52 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc <xml2rfc@ietf.org>
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <5cd2807f-397c-b098-f91f-a8e84a6b4510@gmail.com> <94576ea4-d3ab-2aa3-c43b-8771b1f9e043@ietf.org> <e28ed04b-8d51-089b-3ea5-aae139d371be@gmx.de> <CANMZLAa=TYEhv+-6ZHJBmeGDHee__knTgEu7E8eZjV_UitMhsQ@mail.gmail.com> <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7323703b-d9a3-2043-87d1-9fe58d56dfc6@gmail.com>
Date: Tue, 3 Aug 2021 08:57:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <431c2076-46b8-c71f-86ea-4186dffeff7e@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/0rOd4TBuqYOERUXKMSNoG4Ie57o>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 20:57:59 -0000

On 02-Aug-21 21:25, Julian Reschke wrote:
> Am 02.08.2021 um 10:08 schrieb Brian Carpenter:
>> I think that's a red herring. The processor is not recognizing pn="xxx",
>> that's all.
> 
> Nope.
> 
> The issue is that the document uses xref/target to point to sections
> indentified by their "pn" attribute, and that one's value is different
> under the new version of xml2rfc (and gets replaced).

I'm sorry, I absolutely cannot parse that sentence. All I was saying is
that https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc-dev.cgi seems to
have trouble with "pn".

   Brian


From nobody Tue Aug  3 00:05:42 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1CA03A16C2 for <xml2rfc@ietfa.amsl.com>; Tue,  3 Aug 2021 00:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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 786ZLMAuWhps for <xml2rfc@ietfa.amsl.com>; Tue,  3 Aug 2021 00:05:34 -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 466D23A16C0 for <xml2rfc@ietf.org>; Tue,  3 Aug 2021 00:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1627974330; bh=rLZwbxgvHqEvV5u/hacFjRBI2zAzS92GGaENQbxqOOU=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=RjIA1C79J+EBkcwEXd0SUey+z7K7bmPr4cWVHELzzJSDm2nVIj4Ouh2hZmMthznL9 G8QfPqW1mNioxvRc9IaddonVoFFF5YDOsxmnTmzkTg2i3WXgeyjgasosyfJMa5P01m MQnBuJUQUcTqZpBW6XMgdjee3UKQOhpV/630xlx4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.4.172] ([212.205.152.82]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1Mkpav-1msMEf0yul-00mGY3 for <xml2rfc@ietf.org>; Tue, 03 Aug 2021 09:05:30 +0200
To: xml2rfc@ietf.org
References: <69176971-843c-5e59-b45b-18398bd41d38@taugh.com> <61145c89-4c93-13ab-6430-e87afcf17efe@it.aoyama.ac.jp> <98df983-bf39-6521-dffe-86e44015db7f@taugh.com> <72e2f889-a012-c990-ac25-809e2dbaaa39@gmx.de> <se9imc$j1e$1@gal.iecc.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ae33c49d-6503-fdae-c6f1-ca0cadc7c177@gmx.de>
Date: Tue, 3 Aug 2021 09:05:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <se9imc$j1e$1@gal.iecc.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:v9hIxoiRnYhc7MSe6gTigSJYT+J+PyJRhVwblwgHxv7n2xIs+mg wZzHcRAlG6i1G0elb2PwsQi5lSARXtOMfSvgnoRZ81b31HO3Q8fdVaX1Jp1Rqb44WgT7GB9 yY7sFMPNH5cAO12g/8qNqWl7wb2vwidt4TSeJK8jq38VvEvPtu9QDmPqtSz7/KPl2L1lix9 0Nx+1s8uhoqO+XoK9IpAQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:1iocRX0Xllo=:2wOMJmdVZgDolePoMbEEhE mtQnvV79DtgBhwv4vfwwad8VBXIP6a9gJxoT1vWYX6Auyn5Qa2UaThrjoolknRpp4t+RADOMe JXEDetWWfHvWBqGz9qpHCwWy9e7nOuT3Fi4SB5VgkOxFJAt1pkqfgXCQABOHHvlDZtXVa6jH5 svi2h2VwS8zsJSZX++icRG327f0A9clETeqyX8BqCDljaTV6usVx5az5CRkXDIW5bxR5Y0/3v YXQG0LTkT0hTo5IvCbJtkl8MsuYyFgyPs8L8/Ok0KiifBzDKRTi/VYdeBbrMDMsyYVzdhE9ui eiWLPUAo4yh07HMUmBiNe0O0kkZAX7ZGwbgQ/tqGHDDUk0AoLexfctivRTw8KTu82Uy4SXTyQ TmGARVIbxlA1jfz5EWrgM/cars6G+nXdrBdhHX5i4NIkcGAZBO3rACc9bpelaTOtOKhtdn1L5 3dc+QOBwH+nVMRXTGwdoyMVMy5wiyJt6tqHpVOAvanQsPRJiHaD87o+C3HanaNDScDRVjxJS8 8yMUOLohTET0ub8GU/FrD8IAPL0ZSzGgyMiIkmBaWN0hWxHSonEZ/LJyXc1Zyocq4cvy1pQ7g MrzJ+wCXfYwvTf7EafuZfEIxJ0n9MFoQH+XwWE37aW5LdJVgGvKSw13KvXOqjimehm0eVVRho gs7lkCbLeY3029VgJ0IGLhHjkOjtLje5DeTQUpHvGZuvlCcpWGo7UcI/69odnz/kW7xSuzNyN M7EITwW7v4ZHleyeb8G7h3qEcwEdwjofc5icyXS2nCPjXq02O54UioE14IxUpPjE2+iaolK4c 3E7NIo8DjLcKOc690O3Mw7ekYkjDu0IUeyhPC80m7lD3Bvlfw1vHCI9qoI3qqSVq6Ck6jh3IN xxp3Kkw2DymQWdpfEjh3sk/X/0xmaYCLX1lXnJxBvhf5j1FADeSV+ShRLS4BZYJnUf1LDc3La zcSApToqxjDehckK9zzkyBMp1kXsLHZ2VqZ+t6BpQQPXKIndl8j9LBTm15EL9/qBt1zEtEPs2 U7G7Fcvc9IPdWgv3Ymxp3a85JegGNmt9MjDSfN6OOJLWWVM49AdYTWp0WL9KbCwuQwep9aIOd fK7ERbKCmoUNu/JDRu0BJ2Z7RvcyjMvBwEX5Qeu9IMbPlnPuXO8kZv0wQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XoaLcT_rukUR4phugZeM87DegpE>
Subject: Re: [xml2rfc] Current xml2rfc produces errors on published RFCs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Aug 2021 07:05:41 -0000

Am 02.08.2021 um 21:57 schrieb John Levine:
> According to Julian Reschke  <julian.reschke@gmx.de>:
>>> Not just those two, all of them.=C2=A0 I've run the entire set of publ=
ished
>>> RFCs through xml2rfc.=C2=A0 It takes maybe half an hour.=C2=A0 We defi=
nitely
>>> should do that before releasing each new version.
>>
>> So if anything breaks with published canonical XML, we can't make that
>> change?
>
> Maybe, maybe not, but we can at least make the change knowing what the c=
onsequences will be.

+1

> This gets back to the unresolved issue of whether we're going to update =
the XML in published
> RFCs once we agree on what v3.1 is.

True. And I continue to believe that we should do that.

Best regards, Julian


From nobody Mon Aug  9 03:53:48 2021
Return-Path: <glyn.normington.work@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0813A0838 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Aug 2021 03:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 (2048-bit key) header.d=gmail.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 HNcsg2NLgR3N for <xml2rfc@ietfa.amsl.com>; Mon,  9 Aug 2021 03:53:45 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 03CF73A0835 for <xml2rfc@ietf.org>; Mon,  9 Aug 2021 03:53:44 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id mq2-20020a17090b3802b0290178911d298bso6504708pjb.1 for <xml2rfc@ietf.org>; Mon, 09 Aug 2021 03:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=QluGuM/FSMbg0K41M2pHJ9kpwFTndrGWCovwcKHeTCU=; b=pgEL7A8hZw08oM/amFJ8dL2bC+nVXwVUuZAU98lhESlEtHH6Lv6i37h0GXWNLG6C/x mIfUfQuGB/3FptV0V+V4rX1FxO5++5+59tpd2Yd2kRC4mdPHP5S16mBzgxvy3NWrXsJc lLAgljYlUe9W5nureAi6uf3WWI7xW+xWCEIGfxnZicBM0IbhDaePGH/YmTcJddnx7/DU yakYQJ4XadrVOyiTLM9ME5oxuJFzCZ3tmY44BZET8VtvC2+DCwC9s8t/QY6vkIuUmMDz FWaM2bDNCXbtoUfH7HOaPWOPd3yUfdovm0b/LaOtkUGyo10aN6KlZS5B/vksOwRK3yAa BCJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QluGuM/FSMbg0K41M2pHJ9kpwFTndrGWCovwcKHeTCU=; b=uN/cgWCZR0K+y23WsitNT24bXFo4R6USnKMWVtJZS7Bj1OfR/2r+O0CGvUBDaFbXlG X3Mh+xUzHMCT/ff+AW4z35IjV/CPeLIx2vG1TsVJLQoQE/inx+uMuJbU1vHE9ywLRFeZ MwnRHgTu42ru954xxWT0Ia0Cnr5QbBlEz03ahwTKi/sFQAgMjFaLmnMrKIbwdrGF2hKj TXhrdkLQ8rqrGdZHIl07VLFGn1HOLJnh8pZj6W3vC4UA/oPaWzov5uZ7pIS9dNAgbfXs orwvzwY4nAgsuXTAWhGLjLclyxK1BRqRuCxlTDQGSQT+gOnDSeir7W3egHP4OxIpXy/4 mt+g==
X-Gm-Message-State: AOAM532N9CHJ6X9QqjL6u7DpzOVZYjErQr8zDwPjmrXJ33brfoC/rjVY 7e/nQXGnFss/C8Lv8yMxe3aqTBhaLEAUH/r4oh3Cv+sE5Lk=
X-Google-Smtp-Source: ABdhPJyvgYLSRtoxE0V8I0XBwVgoRgpTnn8s+9o9NVUqDijtZvFhCwalWJS3qktW3iQQUtahwg4lp2EAM7waTWKAZ44=
X-Received: by 2002:a17:90a:b948:: with SMTP id f8mr35440683pjw.3.1628506422656;  Mon, 09 Aug 2021 03:53:42 -0700 (PDT)
MIME-Version: 1.0
From: Glyn Normington <glyn.normington.work@gmail.com>
Date: Mon, 9 Aug 2021 11:53:32 +0100
Message-ID: <CANH0GbJSrezhUqK2DkrPx_7ttptLp1BZZbjeFA0VctLBzD7YWw@mail.gmail.com>
To: xml2rfc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d6429f05c91e3256"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/30tTnMMcJHCIH8t8-s_NVLZYrFg>
Subject: [xml2rfc] Double quotes added to text output when <br/> inside <td>
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Aug 2021 10:53:47 -0000

--000000000000d6429f05c91e3256
Content-Type: text/plain; charset="UTF-8"

When I use <br/> to add a linebreak inside a <td>, xml2rfc seems to add
double quotes round some items. For example, the following table:

<table align="center">
<name>Filter expression operator precedence</name>
<thead>
<tr>
<th align="center">Precedence</th>
<th align="center">Operator type</th>
<th align="center">Syntax</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">5</td>
<td align="center">Grouping</td>
<td align="center">
<tt>(...)</tt></td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">Logical NOT</td>
<td align="center">
<tt>!</tt></td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">Relations</td>
<td align="center">
<tt>==</tt><br/><tt>&lt;</tt></td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">Logical AND</td>
<td align="center">
<tt>&amp;&amp;</tt></td>
</tr>
<tr>
<td align="center">1</td>
<td align="center">Logical OR</td>
<td align="center">
<tt>||</tt></td>
</tr>
</tbody>
</table>

is rendered in text output as:

                  +============+===============+========+
                  | Precedence | Operator type | Syntax |
                  +============+===============+========+
                  |     5      |    Grouping   | (...)  |
                  +------------+---------------+--------+
                  |     4      |  Logical NOT  |   !    |
                  +------------+---------------+--------+
                  |     3      |   Relations   |  "=="  |
                  |            |               |  "<"   |
                  +------------+---------------+--------+
                  |     2      |  Logical AND  |   &&   |
                  +------------+---------------+--------+
                  |     1      |   Logical OR  |   ||   |
                  +------------+---------------+--------+

                    Table 5: Filter expression operator
                                 precedence

Why are these extra quotes added and is there a way to avoid this behaviour?

Regards,
Glyn

--000000000000d6429f05c91e3256
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">When I use &lt;br/&gt; to add a linebreak inside a &lt;td&=
gt;, xml2rfc seems to add double quotes round some items. For example, the =
following table:<br><br>&lt;table align=3D&quot;center&quot;&gt;<br>&lt;nam=
e&gt;Filter expression operator precedence&lt;/name&gt;<br>&lt;thead&gt;<br=
>&lt;tr&gt;<br>&lt;th align=3D&quot;center&quot;&gt;Precedence&lt;/th&gt;<b=
r>&lt;th align=3D&quot;center&quot;&gt;Operator type&lt;/th&gt;<br>&lt;th a=
lign=3D&quot;center&quot;&gt;Syntax&lt;/th&gt;<br>&lt;/tr&gt;<br>&lt;/thead=
&gt;<br>&lt;tbody&gt;<br>&lt;tr&gt;<br>&lt;td align=3D&quot;center&quot;&gt=
;5&lt;/td&gt;<br>&lt;td align=3D&quot;center&quot;&gt;Grouping&lt;/td&gt;<b=
r>&lt;td align=3D&quot;center&quot;&gt;<br>&lt;tt&gt;(...)&lt;/tt&gt;&lt;/t=
d&gt;<br>&lt;/tr&gt;<br>&lt;tr&gt;<br>&lt;td align=3D&quot;center&quot;&gt;=
4&lt;/td&gt;<br>&lt;td align=3D&quot;center&quot;&gt;Logical NOT&lt;/td&gt;=
<br>&lt;td align=3D&quot;center&quot;&gt;<br>&lt;tt&gt;!&lt;/tt&gt;&lt;/td&=
gt;<br>&lt;/tr&gt;<br>&lt;tr&gt;<br>&lt;td align=3D&quot;center&quot;&gt;3&=
lt;/td&gt;<br>&lt;td align=3D&quot;center&quot;&gt;Relations&lt;/td&gt;<br>=
&lt;td align=3D&quot;center&quot;&gt;<br>&lt;tt&gt;=3D=3D&lt;/tt&gt;&lt;br/=
&gt;&lt;tt&gt;&amp;lt;&lt;/tt&gt;&lt;/td&gt;<br>&lt;/tr&gt;<br>&lt;tr&gt;<b=
r>&lt;td align=3D&quot;center&quot;&gt;2&lt;/td&gt;<br>&lt;td align=3D&quot=
;center&quot;&gt;Logical AND&lt;/td&gt;<br>&lt;td align=3D&quot;center&quot=
;&gt;<br>&lt;tt&gt;&amp;amp;&amp;amp;&lt;/tt&gt;&lt;/td&gt;<br>&lt;/tr&gt;<=
br>&lt;tr&gt;<br>&lt;td align=3D&quot;center&quot;&gt;1&lt;/td&gt;<br>&lt;t=
d align=3D&quot;center&quot;&gt;Logical OR&lt;/td&gt;<br>&lt;td align=3D&qu=
ot;center&quot;&gt;<br>&lt;tt&gt;||&lt;/tt&gt;&lt;/td&gt;<br>&lt;/tr&gt;<br=
>&lt;/tbody&gt;<br>&lt;/table&gt;<br><br>is rendered in text output as:<br>=
<br><span style=3D"font-family:monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D+<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Precedence | =
Operator type | Syntax |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D+<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 5 =C2=A0 =C2=
=A0 =C2=A0| =C2=A0 =C2=A0Grouping =C2=A0 | (...) =C2=A0|<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +------------+------------=
---+--------+<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 | =C2=A0 =C2=A0 4 =C2=A0 =C2=A0 =C2=A0| =C2=A0Logical NOT =C2=A0| =
=C2=A0 ! =C2=A0 =C2=A0|<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 +------------+---------------+--------+<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 3 =C2=A0 =C2=
=A0 =C2=A0| =C2=A0 Relations =C2=A0 | =C2=A0&quot;=3D=3D&quot; =C2=A0|<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 | =C2=A0&quot;&lt;&quot; =C2=A0 |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +------------+---------------+--------+<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=
=A0 2 =C2=A0 =C2=A0 =C2=A0| =C2=A0Logical AND =C2=A0| =C2=A0 &amp;&amp; =C2=
=A0 |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--=
----------+---------------+--------+<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 1 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =
Logical OR =C2=A0| =C2=A0 || =C2=A0 |<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +------------+---------------+--------+<br><br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Tabl=
e 5: Filter expression operator<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0precedence</span><br><div><br></div><div>Why are these extra quotes a=
dded and is there a way to avoid this behaviour?</div><div><br></div><div>R=
egards,</div><div>Glyn<br></div></div>

--000000000000d6429f05c91e3256--


From nobody Mon Aug  9 07:51:57 2021
Return-Path: <rjsparks@nostrum.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A97423A1655 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Aug 2021 07:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 mem1CNnQ1Jv6 for <xml2rfc@ietfa.amsl.com>; Mon,  9 Aug 2021 07:51:51 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 286583A164C for <xml2rfc@ietf.org>; Mon,  9 Aug 2021 07:51:51 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 179EpgZO025494 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 9 Aug 2021 09:51:44 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1628520704; bh=aZcpMqzYD+uEYP1p7v9vYhJ0wqEOsmz9M/FTM2ofXy8=; h=Subject:To:References:From:Date:In-Reply-To; b=hCFXCrjlPzvW9/jdMkQ+jw0WPRd5/OOUrlH4nSh5leRfEu5V1Ez7W6mVQXJoL5Q96 3CvbFdNwFm60b9NM5J9uWITA5q4lRcJ4svhdUFM1mLhEWcklXd2DcYdL3IZGuE4pc8 /iJPoGNNleWB8vo2DeRFne4gw/MNiVzD5fQ1+dSQ=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
To: Glyn Normington <glyn.normington.work@gmail.com>, xml2rfc@ietf.org
References: <CANH0GbJSrezhUqK2DkrPx_7ttptLp1BZZbjeFA0VctLBzD7YWw@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <bf23f4cf-46d2-2acb-bc77-bf74bea94304@nostrum.com>
Date: Mon, 9 Aug 2021 09:51:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CANH0GbJSrezhUqK2DkrPx_7ttptLp1BZZbjeFA0VctLBzD7YWw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------E6D7AE2082CDBCCF34E961F9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/0ap0-mCLVFAhCqzj7EqCv8lpA6s>
Subject: Re: [xml2rfc] Double quotes added to text output when <br/> inside <td>
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Aug 2021 14:51:56 -0000

This is a multi-part message in MIME format.
--------------E6D7AE2082CDBCCF34E961F9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Glyn -

see https://trac.ietf.org/trac/xml2rfc/ticket/600

The quoting behavior will be removed in an upcoming release.

RjS

On 8/9/21 5:53 AM, Glyn Normington wrote:
> When I use <br/> to add a linebreak inside a <td>, xml2rfc seems to 
> add double quotes round some items. For example, the following table:
>
> <table align="center">
> <name>Filter expression operator precedence</name>
> <thead>
> <tr>
> <th align="center">Precedence</th>
> <th align="center">Operator type</th>
> <th align="center">Syntax</th>
> </tr>
> </thead>
> <tbody>
> <tr>
> <td align="center">5</td>
> <td align="center">Grouping</td>
> <td align="center">
> <tt>(...)</tt></td>
> </tr>
> <tr>
> <td align="center">4</td>
> <td align="center">Logical NOT</td>
> <td align="center">
> <tt>!</tt></td>
> </tr>
> <tr>
> <td align="center">3</td>
> <td align="center">Relations</td>
> <td align="center">
> <tt>==</tt><br/><tt>&lt;</tt></td>
> </tr>
> <tr>
> <td align="center">2</td>
> <td align="center">Logical AND</td>
> <td align="center">
> <tt>&amp;&amp;</tt></td>
> </tr>
> <tr>
> <td align="center">1</td>
> <td align="center">Logical OR</td>
> <td align="center">
> <tt>||</tt></td>
> </tr>
> </tbody>
> </table>
>
> is rendered in text output as:
>
> +============+===============+========+
>                   | Precedence | Operator type | Syntax |
>                   +============+===============+========+
>                   |     5      |    Grouping   | (...)  |
>                   +------------+---------------+--------+
>                   |     4      |  Logical NOT  |   !    |
>                   +------------+---------------+--------+
>                   |     3      |   Relations   |  "=="  |
>                   |            |               |  "<"   |
>                   +------------+---------------+--------+
>                   |     2      |  Logical AND  |   &&   |
>                   +------------+---------------+--------+
>                   |     1      |   Logical OR  |   ||   |
>                   +------------+---------------+--------+
>
>                     Table 5: Filter expression operator
>                                  precedence
>
> Why are these extra quotes added and is there a way to avoid this 
> behaviour?
>
> Regards,
> Glyn
>
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc

--------------E6D7AE2082CDBCCF34E961F9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Glyn -</p>
    <p>see <a class="moz-txt-link-freetext" href="https://trac.ietf.org/trac/xml2rfc/ticket/600">https://trac.ietf.org/trac/xml2rfc/ticket/600</a></p>
    <p>The quoting behavior will be removed in an upcoming release.</p>
    <p>RjS<br>
    </p>
    <div class="moz-cite-prefix">On 8/9/21 5:53 AM, Glyn Normington
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANH0GbJSrezhUqK2DkrPx_7ttptLp1BZZbjeFA0VctLBzD7YWw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">When I use &lt;br/&gt; to add a linebreak inside a
        &lt;td&gt;, xml2rfc seems to add double quotes round some items.
        For example, the following table:<br>
        <br>
        &lt;table align="center"&gt;<br>
        &lt;name&gt;Filter expression operator precedence&lt;/name&gt;<br>
        &lt;thead&gt;<br>
        &lt;tr&gt;<br>
        &lt;th align="center"&gt;Precedence&lt;/th&gt;<br>
        &lt;th align="center"&gt;Operator type&lt;/th&gt;<br>
        &lt;th align="center"&gt;Syntax&lt;/th&gt;<br>
        &lt;/tr&gt;<br>
        &lt;/thead&gt;<br>
        &lt;tbody&gt;<br>
        &lt;tr&gt;<br>
        &lt;td align="center"&gt;5&lt;/td&gt;<br>
        &lt;td align="center"&gt;Grouping&lt;/td&gt;<br>
        &lt;td align="center"&gt;<br>
        &lt;tt&gt;(...)&lt;/tt&gt;&lt;/td&gt;<br>
        &lt;/tr&gt;<br>
        &lt;tr&gt;<br>
        &lt;td align="center"&gt;4&lt;/td&gt;<br>
        &lt;td align="center"&gt;Logical NOT&lt;/td&gt;<br>
        &lt;td align="center"&gt;<br>
        &lt;tt&gt;!&lt;/tt&gt;&lt;/td&gt;<br>
        &lt;/tr&gt;<br>
        &lt;tr&gt;<br>
        &lt;td align="center"&gt;3&lt;/td&gt;<br>
        &lt;td align="center"&gt;Relations&lt;/td&gt;<br>
        &lt;td align="center"&gt;<br>
&lt;tt&gt;==&lt;/tt&gt;&lt;br/&gt;&lt;tt&gt;&amp;lt;&lt;/tt&gt;&lt;/td&gt;<br>
        &lt;/tr&gt;<br>
        &lt;tr&gt;<br>
        &lt;td align="center"&gt;2&lt;/td&gt;<br>
        &lt;td align="center"&gt;Logical AND&lt;/td&gt;<br>
        &lt;td align="center"&gt;<br>
        &lt;tt&gt;&amp;amp;&amp;amp;&lt;/tt&gt;&lt;/td&gt;<br>
        &lt;/tr&gt;<br>
        &lt;tr&gt;<br>
        &lt;td align="center"&gt;1&lt;/td&gt;<br>
        &lt;td align="center"&gt;Logical OR&lt;/td&gt;<br>
        &lt;td align="center"&gt;<br>
        &lt;tt&gt;||&lt;/tt&gt;&lt;/td&gt;<br>
        &lt;/tr&gt;<br>
        &lt;/tbody&gt;<br>
        &lt;/table&gt;<br>
        <br>
        is rendered in text output as:<br>
        <br>
        <span style="font-family:monospace">                 
          +============+===============+========+<br>
                            | Precedence | Operator type | Syntax |<br>
                            +============+===============+========+<br>
                            |     5      |    Grouping   | (...)  |<br>
                            +------------+---------------+--------+<br>
                            |     4      |  Logical NOT  |   !    |<br>
                            +------------+---------------+--------+<br>
                            |     3      |   Relations   |  "=="  |<br>
                            |            |               |  "&lt;"   |<br>
                            +------------+---------------+--------+<br>
                            |     2      |  Logical AND  |   &amp;&amp;
            |<br>
                            +------------+---------------+--------+<br>
                            |     1      |   Logical OR  |   ||   |<br>
                            +------------+---------------+--------+<br>
          <br>
                              Table 5: Filter expression operator<br>
                                           precedence</span><br>
        <div><br>
        </div>
        <div>Why are these extra quotes added and is there a way to
          avoid this behaviour?</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Glyn<br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
xml2rfc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:xml2rfc@ietf.org">xml2rfc@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/xml2rfc">https://www.ietf.org/mailman/listinfo/xml2rfc</a>
</pre>
    </blockquote>
  </body>
</html>

--------------E6D7AE2082CDBCCF34E961F9--


From nobody Tue Aug 17 02:08:11 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70B93A18CA; Tue, 17 Aug 2021 02:08:05 -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 RdrgD9xiz2Jn; Tue, 17 Aug 2021 02:08:00 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D34F33A18C2; Tue, 17 Aug 2021 02:07:59 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GplYS5c7Vz2xMm; Tue, 17 Aug 2021 11:07:56 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <YRt1V+K7uafeqOnw@shrubbery.net>
Date: Tue, 17 Aug 2021 11:07:56 +0200
Cc: ietf@ietf.org, xml2rfc <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 650884075.908211-e030c7aceec3267ec2e7bf84ff0281ed
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org>
References: <YRt1V+K7uafeqOnw@shrubbery.net>
To: heasley <heas@shrubbery.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Y_-CuG2_vt-xlI94WCeYGreAZnw>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2021 09:08:06 -0000

Hi,

> On 2021-08-17, at 10:37, heasley <heas@shrubbery.net> wrote:
>=20
> I appologize if there is a better forum for this question, I didnt =
find one.
> Cluebat welcome.

The answer to this question isn=E2=80=99t quite as clear-cut as it =
could; we don=E2=80=99t have an =E2=80=9Crfcxml-authors=E2=80=9D list, =
but typically these questions come up on the xml2rfc mailing list (or =
rfc-interest, or tools-discuss=E2=80=A6).

> Is it possible to insert a line break in the contents of a list?
>=20
> <ol>
> <li>
>  bunch of hooey
>  <line break>
>  more hoo-ah
> </li>
>=20
> Everything that I have tried results in errors from xml2rfc.

First of all, I=E2=80=99m assuming you are using xml2rfc with --v3 flags =
(<ol/<li is new syntax for v3).  Even though there is older =
documentation that is supposedly more authoritative, the RFCXMLv3 we =
actually use is described in =
https://xml2rfc.tools.ietf.org/xml2rfc-doc.html =20

https://xml2rfc.tools.ietf.org/xml2rfc-doc.html#name-br-2
describes the <br element, which can do exactly what you want, and is in =
the content model for <li.
So the example becomes:

> <ol>
> <li>
>  bunch of hooey
>  <br/>
>  more hoo-ah
> </li>

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Aug 18 07:59:42 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E36B3A1D9E; Wed, 18 Aug 2021 07:59:32 -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 mAWh5u6F76uY; Wed, 18 Aug 2021 07:59:26 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E79FE3A1D9A; Wed, 18 Aug 2021 07:59:24 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GqWJV1n1mz2xQc; Wed, 18 Aug 2021 16:59:22 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de>
Date: Wed, 18 Aug 2021 16:59:21 +0200
Cc: ietf@ietf.org, xml2rfc <xml2rfc@ietf.org>, rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 650991561.770273-bc7d38c9bc5896a531e0a60eadb9b0e6
Content-Transfer-Encoding: quoted-printable
Message-Id: <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org>
References: <YRt1V+K7uafeqOnw@shrubbery.net> <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org> <07bd2306-130c-a07e-afe8-684d9f65c04a@gmx.de> <YRxBZs/UF2atvBFY@shrubbery.net> <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/t49wYDl38sxCJfgKfFsrxhtIcUk>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2021 14:59:33 -0000

On 2021-08-18, at 16:43, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Am 18.08.2021 um 01:08 schrieb heasley:
>> ...
>>> Or, if you actually want a list item containing two paragraphs:
>>>=20
>>> <ol>
>>>    <li>
>>>      <t>bunch of hooey</t>
>>>      <t>more hoo-ah</t>
>>>    </li>
>>> </ol>
>>=20
>> That works, but did not work for me originally and after your message =
I found
>> that I could not mix syntax like below.  Maybe using <t> throughout =
the <dl>
>> would work.
>>=20
>> <ol>
>>    <li>
>>      bunch of hooey
>>      <t>more hoo-ah</t>
>>    </li>
>> </ol>
>>=20
>> In all cases, the errors that it produced did not lead me to a =
solution.
>=20
> Raise an issue (-> <https://trac.ietf.org/trac/xml2rfc>).
>=20
> Best regards, Julian

As far as I can see, there is no support for mixed content between =
block-level elements (to which <t belongs) and text/span-level elements =
anywhere in the v3 grammar.

There are a few elements that can have sequences of text/span-level =
elements *or* sequences of block-level elements:

blockquote (but not aside!?)
li
dd (not dt!)
td/th

So while this may be confusing until one reads the grammar, this is at =
least somewhat consistent.

(It doesn=E2=80=99t help that there are elements like <contact that are =
allowed in both block-level and span-level contexts and change their =
semantics based on that context.)

A cleanup is clearly needed, but it would not help with this example.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Aug 18 08:01:34 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 150633A1DA5; Wed, 18 Aug 2021 08:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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 WFl8ApnI2E-h; Wed, 18 Aug 2021 08:01:27 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 88E5D3A1DA4; Wed, 18 Aug 2021 08:01:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1629298874; bh=KLu4hKFHds/cB+zBbxdvx+QmxRKRiC5M7afZ08rzS9Q=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=NqJL9nWwOnLwRmRiMpSc96Yuhk6QepgNOmxgHhM1K3hF1GyWuZnmEw4xfV85xkyz8 L0VqXyT5aKqOT8vwO8o7g9oVqpw+5rbEhGMSbpCQF4Pg/awbZxhhS7kIp1MuadOxVM fnIqT72XIk8JPikdGohCKkmHJdaKc5njJipiZm/8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.156.220]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MF3DM-1mIYuP3yky-00FUQk; Wed, 18 Aug 2021 17:01:14 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: ietf@ietf.org, xml2rfc <xml2rfc@ietf.org>, rfc-interest@rfc-editor.org
References: <YRt1V+K7uafeqOnw@shrubbery.net> <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org> <07bd2306-130c-a07e-afe8-684d9f65c04a@gmx.de> <YRxBZs/UF2atvBFY@shrubbery.net> <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de> <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <07841cef-5c75-2ea0-d0ee-5ef806292921@gmx.de>
Date: Wed, 18 Aug 2021 17:01:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:D93opb3VIyHhzdVPzkZItkHuxBXphVUcUfd+OlkZbVMP6PoVvdq 0XelVmp8GhVkD9dPIRSny+H1JGxwHGiPPKTALet7vGu5ZHQ3z8QmAJvV32sd4YV56YM161i E40FdP8RMf/oFegne5GRCUl6dmvnblB2pQmVy9or03FdU3UOUJ6EFlFXYu6+om8Sqt4EUre iGNHqr5drxNXsqDvjcdXw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:maJ/RsNLD34=:xI7CZKPW8rJfv/ueKx+2pj tvvQ43vJ4cfFiZRUx8qCL2mznG8Y+gZGFtiuZ7D5Nbl0AFz91QaBS5KFdaDYJLRtwJM4nB3Mz 6JmDeNG2/8UufX1fTVvK+2l8aLCGOU6POYlw7EipG9YKRfVPqDCS7wkQic1qtdKTnnjnfuGD+ yZynqKk3mKs3johg6j16laxT481Xp/e3d453tADZna9h/9zCEO6q4DFrWot97k/M9Lwwq09Qs npk7YUp7bKl2ynh8x0Dvcc7nrq2BelDYfMfCx/QRFY21uUfiXmfnjtJYSJPlUDOPBxvqHeaLg w/TLSvqBSpGIv0qTt4dZodNuavGfnYNk7MFTBAd1atcsdQFIwuu/mhMQ8LFV1/suG2m56bNu7 7C9uor3kX/RET5npN9//p8LRiCaQAv9zrIUj/YAAx/QfNXLTxLkYdleub/dIBDU3XVEOwAjwj w/oEgiRWYFc37zK0XYB6VmvMFJiVUZAs71bkGvbumxud32E4r2EquncJWjgZRXlWpdAt6vCTU v57mIUZGL55S24ppkTCzyqbogWAwIL4kGRwf/65G9kMiHGlMkTdqQOZOm1DAumZ1DytPZLkrd /2ndkQbIcvx9n9f3ZaIMv2oa1PKZl2dVpwQY+FM1jzN+WsmIkxpBKQCtC7fNCOfZSBhLWcI5n F++hoJhjkToFPagpytKnTLC3PMaxTBLxye8iLeDcchD60tgSru1S2efPdMmEaqk+RC6/bUlny MB0/BZq5ejZfkuXcpbBrCR4qDXNr8yeYuYTAv7B4ht9UDSd06d90OJOENJvZjZ/7ltKXhJOg6 TlWaowtxVlxfF2yHEFurWEUpB2DXnC+U4DiHzBzHMroQUxPqSGkwneoJvu6AplIxybzo3+PwO mTTQ4AgAR+Mxna+t8meqyrCZEGLXfwXAnhSJye29POG6vC6y7p2Bvj0rITpiwTgmx44DE7gsj Ma3RhSMPYiyxyELY5ySlHAORMdbU5jIoI0SbLiGlRv7Py4iZSWwnjhxvFIEUe0IcOKSw/3xrw 4wFiqY7szypa0toueIAJG0+S4RjvRGQc9VKIKoeK5L0Fze1D4gziXrkByZgCjPIEOHJXWPnbD OlaLms7gp3ISkerIaqsG7je5/oQuV/AjRDm1+XD9VxmS7Jz4TzPG3rULQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/nFrS9limWCCGkYUB0IRxgV94mlU>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2021 15:01:32 -0000

Am 18.08.2021 um 16:59 schrieb Carsten Bormann:
> On 2021-08-18, at 16:43, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>> Am 18.08.2021 um 01:08 schrieb heasley:
>>> ...
>>>> Or, if you actually want a list item containing two paragraphs:
>>>>
>>>> <ol>
>>>>     <li>
>>>>       <t>bunch of hooey</t>
>>>>       <t>more hoo-ah</t>
>>>>     </li>
>>>> </ol>
>>>
>>> That works, but did not work for me originally and after your message =
I found
>>> that I could not mix syntax like below.  Maybe using <t> throughout th=
e <dl>
>>> would work.
>>>
>>> <ol>
>>>     <li>
>>>       bunch of hooey
>>>       <t>more hoo-ah</t>
>>>     </li>
>>> </ol>
>>>
>>> In all cases, the errors that it produced did not lead me to a solutio=
n.
>>
>> Raise an issue (-> <https://trac.ietf.org/trac/xml2rfc>).
>>
>> Best regards, Julian
>
> As far as I can see, there is no support for mixed content between block=
-level elements (to which <t belongs) and text/span-level elements anywher=
e in the v3 grammar.
>
> There are a few elements that can have sequences of text/span-level elem=
ents *or* sequences of block-level elements:
>
> blockquote (but not aside!?)
> li
> dd (not dt!)
> td/th
>
> So while this may be confusing until one reads the grammar, this is at l=
east somewhat consistent.

Absolutely. My suggestion was to raise a ticket for the non-helpful
diagnostics.

> (It doesn=E2=80=99t help that there are elements like <contact that are =
allowed in both block-level and span-level contexts and change their seman=
tics based on that context.)

Indeed. (Guess what?)

> ...

Best regards, Julian


From nobody Wed Aug 18 09:04:01 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132E93A2060; Wed, 18 Aug 2021 09:03:56 -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 Yce9gCU97uZo; Wed, 18 Aug 2021 09:03:50 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310DE3A2054; Wed, 18 Aug 2021 09:03:49 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GqXkl0ndqz2xMq; Wed, 18 Aug 2021 18:03:43 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <07841cef-5c75-2ea0-d0ee-5ef806292921@gmx.de>
Date: Wed, 18 Aug 2021 18:03:42 +0200
Cc: xml2rfc <xml2rfc@ietf.org>, rfc-interest@rfc-editor.org, ietf@ietf.org
X-Mao-Original-Outgoing-Id: 650995422.654915-d19f525af9cda410f61d4f90e165a99b
Content-Transfer-Encoding: quoted-printable
Message-Id: <9760281E-1EAD-40F7-8F78-4C7D416D8CFF@tzi.org>
References: <YRt1V+K7uafeqOnw@shrubbery.net> <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org> <07bd2306-130c-a07e-afe8-684d9f65c04a@gmx.de> <YRxBZs/UF2atvBFY@shrubbery.net> <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de> <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org> <07841cef-5c75-2ea0-d0ee-5ef806292921@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/RBO1Z1nxw2apIBbrfHGhiaUOQnk>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2021 16:03:56 -0000

On 2021-08-18, at 17:01, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
>> So while this may be confusing until one reads the grammar, this is =
at least somewhat consistent.
>=20
> Absolutely. My suggestion was to raise a ticket for the non-helpful
> diagnostics.

foo-broken.xml(623): Error: Element li has extra content: t, at =
/rfc/middle/section[2]/ul/li[1]/t
/.../foo-broken.xml(14): Error: Invalid document before running =
preptool.
Unable to complete processing foo-broken.xml

The line number turns out to be useful to me, as the XML editor is =
showing a validation error on the <t that follows text.

Creating useful error messages out of validation errors is generally =
impossible, as the grammar/schema has been abstracted of the information =
that could be used for a =E2=80=9Cwhy=E2=80=9D/=E2=80=9Cwhat=E2=80=99s =
going on=E2=80=9D part of the error message.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Aug 19 05:14:17 2021
Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA0D93A115C for <xml2rfc@ietfa.amsl.com>; Thu, 19 Aug 2021 05:14:14 -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 s920XQeWW9rz for <xml2rfc@ietfa.amsl.com>; Thu, 19 Aug 2021 05:14:09 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC773A1159 for <xml2rfc@ietf.org>; Thu, 19 Aug 2021 05:14:07 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Gr3bF15hNz2xHs; Thu, 19 Aug 2021 14:14:01 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <cdb764b6-426b-0019-3804-15f480777b2e@gmx.de>
Date: Thu, 19 Aug 2021 14:14:00 +0200
Cc: xml2rfc <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 651068040.6773911-071d8ba304e201650a0a9486cd2fe8ca
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C6AACA1-7FA7-47A8-AD14-95F4784355F7@tzi.org>
References: <YRt1V+K7uafeqOnw@shrubbery.net> <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org> <07bd2306-130c-a07e-afe8-684d9f65c04a@gmx.de> <YRxBZs/UF2atvBFY@shrubbery.net> <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de> <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org> <07841cef-5c75-2ea0-d0ee-5ef806292921@gmx.de> <9760281E-1EAD-40F7-8F78-4C7D416D8CFF@tzi.org> <cdb764b6-426b-0019-3804-15f480777b2e@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/U-PkZMeMqTjTETTIkJaC8K3kvdA>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Aug 2021 12:14:15 -0000

(You didn=E2=80=99t make your enlightened comment available to the =
xml2rfc list, which I=E2=80=99m doing herewith.)

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-08-19, at 09:05, Julian Reschke <julian.reschke@gmx.de> wrote:
>=20
> Am 18.08.2021 um 18:03 schrieb Carsten Bormann:
>> On 2021-08-18, at 17:01, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>>>=20
>>>> So while this may be confusing until one reads the grammar, this is =
at least somewhat consistent.
>>>=20
>>> Absolutely. My suggestion was to raise a ticket for the non-helpful
>>> diagnostics.
>>=20
>> foo-broken.xml(623): Error: Element li has extra content: t, at =
/rfc/middle/section[2]/ul/li[1]/t
>> /.../foo-broken.xml(14): Error: Invalid document before running =
preptool.
>> Unable to complete processing foo-broken.xml
>>=20
>> The line number turns out to be useful to me, as the XML editor is =
showing a validation error on the <t that follows text.
>>=20
>> Creating useful error messages out of validation errors is generally =
impossible, as the grammar/schema has been abstracted of the information =
that could be used for a =E2=80=9Cwhy=E2=80=9D/=E2=80=9Cwhat=E2=80=99s =
going on=E2=80=9D part of the error message.
>=20
> ...but of course that doesn't mean that the tool can't create better
> diagnostics. For instance, it could check certain things *before*
> validating.
>=20
> Best regards, Julian


From nobody Thu Aug 19 05:21:29 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9776E3A11C8 for <xml2rfc@ietfa.amsl.com>; Thu, 19 Aug 2021 05:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-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 VYnwqrInC3XT for <xml2rfc@ietfa.amsl.com>; Thu, 19 Aug 2021 05:21:23 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 3907D3A11C4 for <xml2rfc@ietf.org>; Thu, 19 Aug 2021 05:21:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1629375673; bh=39lqfIPWyy6jCK5uaH7XxmuDS+y3SM1SDBszYVADwe4=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=cFDIjs2J/JUkHd4kVwk0U1Af2dDb5jCLbt9mMpEKUdDYO2rFsqaAtBmWAi/GRKtOi 4ejdvUrWoylRqdsa41WnwdPyCTwa1JX5T8WMhqNUs2W/KA3EMl8B481W7F3yCUnTY/ XHPy1JaRSAf7nZnzRTVfkct3w2BfH5et7OwPi3Q8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.236] ([217.91.35.233]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MwQTF-1n6jKm2prp-00sPIn; Thu, 19 Aug 2021 14:21:13 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: xml2rfc <xml2rfc@ietf.org>
References: <YRt1V+K7uafeqOnw@shrubbery.net> <E2FCB445-FC8A-4133-9796-1D43DFC14650@tzi.org> <07bd2306-130c-a07e-afe8-684d9f65c04a@gmx.de> <YRxBZs/UF2atvBFY@shrubbery.net> <a35f1cf7-a334-13ae-483c-fa743da15f92@gmx.de> <13B5FF5F-5A62-4E06-BE80-C7126CF43D98@tzi.org> <07841cef-5c75-2ea0-d0ee-5ef806292921@gmx.de> <9760281E-1EAD-40F7-8F78-4C7D416D8CFF@tzi.org> <cdb764b6-426b-0019-3804-15f480777b2e@gmx.de> <6C6AACA1-7FA7-47A8-AD14-95F4784355F7@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <eb0545e8-5b6b-a894-c5e9-a36bbac218d7@gmx.de>
Date: Thu, 19 Aug 2021 14:21:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <6C6AACA1-7FA7-47A8-AD14-95F4784355F7@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:CmV9y8yoKXVfOlKfn1CnrLpaS/PqzOAcb0KuHtg0ACmegF4mjES CZUgow5z0mCkyDT33yeuryR4FLq7He0bVJHChelkm8WLr00ejHq+wEVElrNn9N9AXE2BMTi ZBtZ/i50Pm3bSrJlTFYpLGs7zXl3sf1TEyC7/ZJ/73JVQXxVXiNbvicIJhz6PZvs4pjtozO pQbhbiw99E03lEX4Estmw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:c/FqnBoVNp8=:hb+7OeQxxY2tifgFJy9yD9 0YcyOV38XjgRobGb3sRDjjAPVDo697nmCxKSTCvqYRdU8IrUt6xDNVBzX3ZWRwUDj0J4ZWGM6 qwfuZxT1WN7p9SPCHLGhSDpQv0G7X18SzMOZ7JN27A80D6QG1evb+8s0v1JVYv6QuY2inqWAM Uw5oP9qN9pZrygFmJ3KB9uDyo30PuzWEvjuMQt4EP6k5O+L0isbkdQsYDQhxKY0k9jFA64hWm 1TJGVn1XskuqTBLFetKas0TpgaxU7Ws51GUV+9g2YaeJY4U5QEmZnV0b3XjP38oJVxTW15Jac vDOLIKqs7tTAaRnU6Gt4gLws5Nb4C8hA627eWfDusaqSxOE6R8nVge5MXGH1XxQbFPr9jSrqK SQz3SbJYYdUcUmp4ZlHb39m6LzqYwXHTkwBpwUAe/RniZ3sYrTw+BJfBFC4j1gb3AIcMAam3L ZNpHarqshVF6dnY/iEcryPFQZFClrnfFTn7FEmE32S/V1Ez55d6rhNPQHfK4qBfXA5ipXNnN8 707hdB1okOGelySlzWlBD60GOO9UeNFG+F1HNdo5Q7PrNo2Mur7HzxSWTd270OJp3YtXIKyf/ gWC3JyO7Kuu9N+eLFyT2yMgKbmXQDzGsgm2lrPlrAHbaXd72gokz20+E1r92b14rFyQi55zyb mNbos8HHWWyGUdjEKekLkZsBdl/okb4u6SMCzeb9OsEzNk6+NAZp5AWRNUaSFlJjrdZ+gePdk RhgJEs8t8iuq/9TKPbCt+iodmfhgGY6gnFz2msMg86g7Ka/XM7TEugM0HOE9jSkvhjuR3Gdc5 D3X4ZvXsxPiijVD4Nj/t4QXwzeoN8TPuNq2zgitiozuE4DltM68iJCsZSj877MTnHFt2Y4a7C GZaTXMPWokZ0HypJpab+e3KWOpu7HznbQ5uQ0QyRkFgL9GaRTcomda0Q6nLdTk2F0338TqAFW NG5ol9N9XRvRLxRtcX/RDcFVPiBoXNCYqS8BdgzzOsikDrE1EfE6plmh4y/7zPqIngetHOCkJ VHgOxQ/QhPlckHIoCLTL64w9AaQ7h38ImC19oE8lOtOcYJyHuElSuQWhpwz00g3YPvXlXjkEq 5E10LBBv5HWOTtFOCrUqg/PPQZFkuFJNytMi8zWXwL/MY24nU4Iiihp2g==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/brTWzaSj4i_gSNjwysdw_qPdJw8>
Subject: Re: [xml2rfc] xml2rfc line break
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Aug 2021 12:21:29 -0000

Am 19.08.2021 um 14:14 schrieb Carsten Bormann:
> (You didn=E2=80=99t make your enlightened comment available to the xml2r=
fc list, which I=E2=80=99m doing herewith.)
> ...

Thanks.