[rfc-i] rfc docName for drafts

julian.reschke at gmx.de (Julian Reschke) Fri, 10 June 2016 05:55 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Fri, 10 Jun 2016 07:55:10 +0200
Subject: [rfc-i] rfc docName for drafts
In-Reply-To: <ebbe94a6-f9a5-c20d-6a4a-890e0ec50e02@alum.mit.edu>
References: <ebbe94a6-f9a5-c20d-6a4a-890e0ec50e02@alum.mit.edu>
Message-ID: <cb4dab10-1962-2c77-d959-52a6d3d20596@gmx.de>

On 2016-06-09 20:49, Paul Kyzivat wrote:
> 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.

Actually, the convention is to leave the extension out, and it's 
documented like that in RFC 7749: 
<https://greenbytes.de/tech/webdav/rfc7749.html#element.rfc.attribute.docName>

> 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.

Yes.

> ...


Best regards, Julian