IETF Logo Mail Archive

[Xml-sg-cmt] Fwd: [xml2rfc] #548 (v3 vocabulary): Invalid XML entities inserted by v2v3 converter

Robert Sparks <rjsparks@nostrum.com> Wed, 28 April 2021 15:01 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: xml-sg-cmt@ietfa.amsl.com
Delivered-To: xml-sg-cmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC4B3A0E52 for <xml-sg-cmt@ietfa.amsl.com>; Wed, 28 Apr 2021 08:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level:
X-Spam-Status: No, score=-2.078 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, 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 Vuufojt8WwWR for <xml-sg-cmt@ietfa.amsl.com>; Wed, 28 Apr 2021 08:01:13 -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 A0D423A0E4C for <xml-sg-cmt@ietf.org>; Wed, 28 Apr 2021 08:01:13 -0700 (PDT)
Received: from unformal.localdomain ([47.186.1.92]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 13SF1Cl7088268 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <xml-sg-cmt@ietf.org>; Wed, 28 Apr 2021 10:01:12 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1619622073; bh=1kqR92RDThYuMrwUEFyTsVSD8zz6GvWMwC5PEhLDJQM=; h=Subject:References:To:From:Date:In-Reply-To; b=mN8hQwRQwOdWROhbWS9F0lj5lrrKeuZyyFsivSJJKRXYNBX9jlEiwiZ2XIQLJB5io 5s8H4IgJ92Azqsfkf229X2c28BHhlfShdX8kknaWa2nlK7FdwwvmmljMfkB9NAbX8F jyqO+SFEFYanHdU6cPwATx0rNbGLqvS809rZkOP0=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.1.92] claimed to be unformal.localdomain
References: <087.dc9c0b098e8cbdaa2fa7b1150b4e7742@tools.ietf.org>
To: xml-sg-cmt@ietf.org
From: Robert Sparks <rjsparks@nostrum.com>
X-Forwarded-Message-Id: <087.dc9c0b098e8cbdaa2fa7b1150b4e7742@tools.ietf.org>
Message-ID: <34ea4980-67df-aaef-312c-ea1ddb44d2a1@nostrum.com>
Date: Wed, 28 Apr 2021 10:01:07 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <087.dc9c0b098e8cbdaa2fa7b1150b4e7742@tools.ietf.org>
Content-Type: multipart/alternative; boundary="------------C57E9FAEE8FD42720653B60F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml-sg-cmt/0BmwxoB-viMUpiDN2Vyj7R5Didk>
Subject: [Xml-sg-cmt] Fwd: [xml2rfc] #548 (v3 vocabulary): Invalid XML entities inserted by v2v3 converter
X-BeenThere: xml-sg-cmt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working list for the xml and style guide change management team <xml-sg-cmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/>
List-Post: <mailto:xml-sg-cmt@ietf.org>
List-Help: <mailto:xml-sg-cmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml-sg-cmt>, <mailto:xml-sg-cmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2021 15:01:17 -0000

Re: a recent conversation.



-------- Forwarded Message --------
Subject: 	Re: [xml2rfc] #548 (v3 vocabulary): Invalid XML entities 
inserted by v2v3 converter
Date: 	Wed, 28 Apr 2021 04:27:15 -0000
From: 	xml2rfc issue tracker <trac@tools.ietf.org>
To: 	henrik@levkowetz.com, martin.thomson@gmail.com
CC: 	rjsparks@nostrum.com



#548: Invalid XML entities inserted by v2v3 converter


Comment (by martin.thomson@gmail.com):

I'm in the process of reviewing QUIC documents for AUTH48 and the presence
of entities is causing significant problems with the post-processing that
is necessary. A standard XML parser cannot process the XML that is
produced.

The python XML parser drops these entity references. I understand that
lxml can be taught these, but using lxml would force the use of a
different processing model, which would require that I rewrite a tool
completely. I can't justify that.

While I appreciate that the RPC want this feature, it should not be the
case that others are forced to deal with the problems that it causes.
Surely there are other ways that the needs of the RPC can be accommodated.
Inserting the definitions directly rather than referencing a non-existent
file, perhaps.

-- 
---------------------------------------+--------------------------
   Reporter:  martin.thomson@gmail.com  |      Owner:
       Type:  enhancement               |     Status:  under_review
   Priority:  medium                    |  Milestone:
  Component:  v3 vocabulary             |    Version:
Resolution:                            |   Keywords:
---------------------------------------+--------------------------

Ticket URL: <https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/548#comment:4>
xml2rfc <http://tools.ietf.org/tools/xml2rfc/>

v2.23.0 | Report a Bug | By Email