Re: [xml2rfc-dev] docName?

Henrik Levkowetz <henrik@levkowetz.com> Thu, 09 May 2019 10:17 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E25512011A for <xml2rfc-dev@ietfa.amsl.com>; Thu, 9 May 2019 03:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SUBJ_BRKN_WORDNUMS=0.01] 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 TP4xetPdjnJ7 for <xml2rfc-dev@ietfa.amsl.com>; Thu, 9 May 2019 03:17:24 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5898120100 for <xml2rfc-dev@ietf.org>; Thu, 9 May 2019 03:17:24 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:56918 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1hOg78-0005T8-8i; Thu, 09 May 2019 03:17:23 -0700
To: Miek Gieben <miek@miek.nl>, Julian Reschke <julian.reschke@gmx.de>
References: <20190408214850.fbwdzhza7g4omyvs@miek.nl> <c49cafe0-37d7-8f32-7056-d37df808d96f@gmx.de> <20190509060348.77yjfr3uuff7e67j@miek.nl>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <9f6f2abd-5cda-2611-b1e6-4e912a17f5bb@levkowetz.com>
Date: Thu, 09 May 2019 12:17:07 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20190509060348.77yjfr3uuff7e67j@miek.nl>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="4aCCppXnjdXfpPBULAXp5VtR9J8lNikRg"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, julian.reschke@gmx.de, miek@miek.nl
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/KbDzXm_IufGDHc7zbQGsdscay-w>
Subject: Re: [xml2rfc-dev] docName?
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2019 10:17:27 -0000

Hi Miek,

On 2019-05-09 08:03, Miek Gieben wrote:
> [ Quoting <julian.reschke@gmx.de> in "Re: [xml2rfc-dev] docName?..." ]
>>On 08.04.2019 23:48, Miek Gieben wrote:
>>>Hi,
>>>
>>>Compiling an xml doc with v3, gives this error:
>>>
>>>Parsing file 8341.xml
>>>8341.xml(3): Warning: Expected a 'docName' attribute in the <rfc/>
>>>element, but found none.
>>>
>>>Is docName now back ?
>>
>>Actually is was never gone in xml2rfc as per
>><https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-08#section-3.1.21.5>.
>>
>>Note that I agree with Henrik's summary, but it sure would be cool if we
>>had a coherent description of what v3-as-accepted-by-xml2rfc is.
> 
> So, what's the state of this? XML not having a docName are rejected: https://github.com/mmarkdown/mmark/issues/76
> while the parser only emit a warning...

I'd like to know the rejection message from the datatracker.  There are
any number of possible rejection reasons that have nothing to do with
docName, even if the description in #76 seems to indicate that it's related.

I may be able to fish the rejection reason out if I know the draft name and
submission date.  Could you provide that?

I'll check the code to see if the warning should be an error, but would really
like to see the rejection message to understand what's up.

> I know need to make code changes for something that is actually not described 
> anywhere, but seems mandatory.

You can expect that docName will continue to be needed.


Regards,

	Henrik