IETF Logo Mail Archive

Re: [xml2rfc-dev] docName?

Miek Gieben <miek@miek.nl> Thu, 09 May 2019 06:03 UTC

Return-Path: <miek@miek.nl>
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 F16D5120189 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 8 May 2019 23:03:54 -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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20150623.gappssmtp.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 qOj_BBZzTItK for <xml2rfc-dev@ietfa.amsl.com>; Wed, 8 May 2019 23:03:52 -0700 (PDT)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 22556120125 for <xml2rfc-dev@ietf.org>; Wed, 8 May 2019 23:03:51 -0700 (PDT)
Received: by mail-wm1-x329.google.com with SMTP id y197so1486380wmd.0 for <xml2rfc-dev@ietf.org>; Wed, 08 May 2019 23:03:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=XBF0ppLmPB7X8m98PF/4svhKdTCfV48z9zUkA+xRWoE=; b=VZeVsOTfJAHQEbanik4pGFVvSkgalcnfSr4C9A9ahlHp67xcO5BkDuT0MZ8WAKjgTT D/8mU5njevVG5EH5Fw1wlPC3Wy0mJ+AxtbxD5OPk2aDCixhoZsthbvB9aGrSImN7rC2H 5VMO0ClwW1GWsKMDSSBaJTcG1JtBjAjXNCIBeBJVFb6o4aVGpwaoRpQ7KUAV2WSm+TjF 8BxWq/yeaLj3mNBSDQQlVqR82L5X5W8/57hZEliZaUDAY6qo7dBtcetcR8OL5ORIL/Oc 7wcW2dfln1mbMFPrTvr4eyKrKuqHQTF5XSvd+ssc+OKd22vdarThQdIFuSpmftGOIHX5 BSTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=XBF0ppLmPB7X8m98PF/4svhKdTCfV48z9zUkA+xRWoE=; b=ZUL7dsGEUX7bkgYa8m/5OO5Y6IBiCjDniI85OPK+UyzShg/7LFeczJ4eU5ti+3+JsX 5dAGgZVTz5MIpLZhheSzD5SIPHOwJxcJmNt+aI3uUr7kbFGqyQVQqV1+BU8LedVPEeqz 6QfAeDawptOupqcZEqvODajUwLqf/MIsDmnv4eIb9wO3GrX4PAA8wnDgE3pNcFj6Kalb RgIF82xeAkq7hoY0PwQQpb6QsHfy632cchJ/2ATzRSwpeQYeikiOKbSKBzwPKSlcw8TN 23+8P4ZIMbkginPVB4xGLFDZRLWB8BW8stO8YxzGoPBbVI+NHQ1XApyIMcaHutvxkQVh oajQ==
X-Gm-Message-State: APjAAAX+d6aeeitA6E4bhCNuLUi40s/KFnTXpgAR4J4hhgq3whmDjD0q aY2woOSDGlpEv3mOnvO0pkpysA==
X-Google-Smtp-Source: APXvYqy8FamrDWgW/pzWxT2BKwZK8BAk+WG2tN3HQBYlcN/9nLqFMGdCpVnqQRVrZQcFqOJTckQm7w==
X-Received: by 2002:a1c:f310:: with SMTP id q16mr1419779wmq.102.1557381830192; Wed, 08 May 2019 23:03:50 -0700 (PDT)
Received: from miek.nl (router.mikrotime.com. [81.187.237.61]) by smtp.gmail.com with ESMTPSA id r64sm4109868wmr.0.2019.05.08.23.03.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 08 May 2019 23:03:49 -0700 (PDT)
Date: Thu, 09 May 2019 07:03:48 +0100
From: Miek Gieben <miek@miek.nl>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
Message-ID: <20190509060348.77yjfr3uuff7e67j@miek.nl>
References: <20190408214850.fbwdzhza7g4omyvs@miek.nl> <c49cafe0-37d7-8f32-7056-d37df808d96f@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <c49cafe0-37d7-8f32-7056-d37df808d96f@gmx.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/JArK8P6-iyUpI-AJ5T5lB4DwlpA>
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 06:04:06 -0000

[ 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 know need to make code changes for something that is actually not described 
anywhere, but seems mandatory.

v2.23.0 | Report a Bug | By Email