Re: [xml2rfc] xml2rfc online: references to I-Ds and associated dates
John C Klensin <john-ietf@jck.com> Thu, 11 July 2019 23:13 UTC
Return-Path: <john-ietf@jck.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 504C7120041 for <xml2rfc@ietfa.amsl.com>; Thu, 11 Jul 2019 16:13:56 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 seICfx2Q9NPD for <xml2rfc@ietfa.amsl.com>; Thu, 11 Jul 2019 16:13:54 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6BC120033 for <xml2rfc@ietf.org>; Thu, 11 Jul 2019 16:13:54 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hliG8-000OMA-U4; Thu, 11 Jul 2019 19:13:52 -0400
Date: Thu, 11 Jul 2019 19:13:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, xml2rfc@ietf.org
Message-ID: <118C3616CE78C9B5BAE651CC@PSB>
In-Reply-To: <5aa01f36-374b-6236-ecc1-58610d50c6e6@gmail.com>
References: <60AB35B3B946D11980DA5426@PSB> <5aa01f36-374b-6236-ecc1-58610d50c6e6@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/rZi0Evj0SibhFsAXnRJjjToGAlk>
Subject: Re: [xml2rfc] xml2rfc online: references to I-Ds and associated dates
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 11 Jul 2019 23:13:56 -0000
--On Friday, July 12, 2019 10:09 +1200 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > On 12-Jul-19 09:51, John C Klensin wrote: >> Hi. >> >> I happened to look today at the reference produced for an I-D >> by xml2rfc (at least by the online version at >> https://xml2rfc.tools.ietf.org/ ) >> >> The XML for the relevant cited I-D says (irrelevant material >> elided and the identity of the I-D changed to avoid >> distractions): >> >> <reference <reference anchor="ID.draft-ietf-foo-bar" >> target="https://datatracker.ietf.org/doc/draft-ietf-foo-bar >> /"> ... >> <date month="June" day="12" year="2019" /> >> </front> >> </reference> >> >> The output is "June 2019". >> >> Now, independent of what the RFC Editor decides to do with the >> reference entry when/if the document gets to them [1], while >> the document in which this is embedded is still an I-D, it >> can be very important to the reader to know which version of >> the I-D was cited and, of course, two or more versions of an >> I-D in the same month is not uncommon. > > Two versions on the same day is not impossible. For an actual > case, I once did this: > > <!-- ********** This reference is specifically to version 07 > of the draft and is therefore ********** hand-crafted > instead of using the I-D bibliography. --> > > <reference anchor='RPL-07'> > <front> > <title>RPL: IPv6 Routing Protocol for Low power and Lossy > Networks</title> <author initials="T." surname="Winter" > fullname="T. Winter"/> <author initials="P." surname="Thubert" > fullname="P. Thubert"/> <date month='March' year='2010'/> > </front> > <seriesInfo name="Internet-Draft" > value="draft-ietf-roll-rpl-07"/> </reference> > > You can see the eventual result, which was not 100% > satisfactory, in https://tools.ietf.org/html/rfc6294 Well, I just looked at the RFC and someone, probably the RFC Editor, discarded your seriesInfo material entirely, leaving just the authors, title, month and year, and the notorious "work in progress". If my guess about the relationship between [RPL] and [RPL-7] is correct, the latter is certainly not a work in progress either. And, if those are the two versions in question, they are in the same month but a year apart. However, that is all about the RFC and other rules, including the insertion of "work in progress" apply. For the I-D case, there is no question that the information can be forced in. One can use your strategy, one can use something a little more like I wrote, with the link in the target attribute of <reference>, and then use <seriesInfo name="Internet-Draft" version="07"/> or one can use an annotation element and describe what is going on. Probably there are other options too. But, as a long-term fan of the principle of generic markup, I wasn't looking for a workaround, I was looking for the information that appears in the markup to be reflected in the output unless there is a substantive reason to not do so. At least some years ago, if a complete date appeared in markup, a complete date also appeared in the output. Either its disappearance is an unintended side-effect of some other change or someone decided to take it out. Either way, I suggest the result is not what we want and that it would make sense to restore the prior behavior. best, john
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Carsten Bormann
- [xml2rfc] xml2rfc online: references to I-Ds and … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Brian E Carpenter
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Carsten Bormann
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Carsten Bormann
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Brian E Carpenter
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Henrik Levkowetz
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Carsten Bormann
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Heather Flanagan
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Henrik Levkowetz
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke
- Re: [xml2rfc] xml2rfc online: references to I-Ds … John C Klensin
- Re: [xml2rfc] xml2rfc online: references to I-Ds … Julian Reschke