[rfc-i] rfc docName for drafts
pkyzivat at alum.mit.edu (Paul Kyzivat) Thu, 09 June 2016 18:49 UTC
From: pkyzivat at alum.mit.edu (Paul Kyzivat)
Date: Thu, 9 Jun 2016 14:49:07 -0400
Subject: [rfc-i] rfc docName for drafts
Message-ID: <ebbe94a6-f9a5-c20d-6a4a-890e0ec50e02@alum.mit.edu>
It seems that, for drafts, the convention is for the docName to be the filename of the text version of the draft. (E.g., draft-foo-bar-03.txt) This then appears on the first page of the document. And it appears with .txt even when the rendition of the document you are looking at isn't a txt document. Is this convention universal, or is it just within the realm I inhabit. As we move to a world where the authoritative form isn't txt, and where the form typically viewed isn't txt, ISTM that this convention ought to be changed. Perhaps the file extension for the format should be omitted. Or perhaps this ought to contain the tracker name for the document (without the version), though the version ought to be present somewhere in the text of the document, regardless of format. Thanks, Paul
- [rfc-i] rfc docName for drafts Paul Kyzivat
- [rfc-i] rfc docName for drafts Joe Hildebrand jhildebr
- [rfc-i] rfc docName for drafts Heather Flanagan RFC Series Editor
- [rfc-i] rfc docName for drafts Paul Kyzivat
- [rfc-i] rfc docName for drafts Julian Reschke
- [rfc-i] rfc docName for drafts Paul Kyzivat