Re: [xml2rfc] xml2rfc online: references to I-Ds and associated dates
John C Klensin <john-ietf@jck.com> Fri, 12 July 2019 14:44 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 81E6612034A for <xml2rfc@ietfa.amsl.com>; Fri, 12 Jul 2019 07:44:12 -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 iZefKq4cxKZP for <xml2rfc@ietfa.amsl.com>; Fri, 12 Jul 2019 07:44:10 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 2E0C2120350 for <xml2rfc@ietf.org>; Fri, 12 Jul 2019 07:44:03 -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 1hlwmF-0003at-RS; Fri, 12 Jul 2019 10:43:59 -0400
Date: Fri, 12 Jul 2019 10:43:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc@ietf.org
Message-ID: <6BAEB8CB8436D7938BB5D807@PSB>
In-Reply-To: <7138e8a5-1c7a-cb5d-2d00-35389a7fada0@levkowetz.com>
References: <60AB35B3B946D11980DA5426@PSB> <7138e8a5-1c7a-cb5d-2d00-35389a7fada0@levkowetz.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/ZD5hoqLYc1d1OkEaj22ec5jW43g>
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: Fri, 12 Jul 2019 14:44:13 -0000
Henrik, This was definitely from the v2 formatter. If it is fixed in v3, that seems like a satisfactory answer and I'll work around it in the interim. thanks, john --On Friday, July 12, 2019 15:16 +0200 Henrik Levkowetz <henrik@levkowetz.com> wrote: > Hi John, > > On 2019-07-11 23: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". > > After looking through various output formats, my conclusion > here is that this is the output from the v2 text formatter, > not the v3 text formatter. The v3 text formatter renders the > date with day, month, and year if all 3 are given. So going > forward, it seems that this has already been addressed > (assuming we leave the v2 formatter untouched at this late > stage in its life cycle). > > > Best regards, > > Henrik > >> >> 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. >> >> Authors who are happy with month and year can presumably just >> leave the day out of the XML. But, if an author believes the >> day is important enough to include in the source file, why is >> that part of the date being suppressed? Is there any hope of >> fixing that, which would revert things to earlier behavior? >> >> best, >> john >> >> [1] It is a completely separate matter from the above and >> probably a topic for another list and another time, but the >> reality, IMO, is that there are two types of I-D references >> that might appear in an RFC. One is a recent draft that is >> still, or might reasonably expected to be, under active >> development. For those, the current "work in progress" form >> is appropriate. I'd still argue for explicit version numbers >> and dates, by they are probably of limited utility. The >> other is a document that is being referenced for historical >> context, has typically been expired for years, and for which >> it is clear that no further development will occur, possibly >> because the referencing document superceded it. If we are >> going to allow references to such I-Ds at all (IIR, for many >> years, we didn't) those references need to be complete with >> accurate dates and version numbers. In addition, claiming >> that they are works in progress, especially when the text of >> the document in which the citation is imbedded says that they >> are obsolete... well, I think the technical term in the >> bibliographical world would be "plain silly". But, again, >> that is a different set of issues from the above and not an >> xml2rfc problem, at least until policies change. >> >> _______________________________________________ >> xml2rfc mailing list >> xml2rfc@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc >> >
- 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