Re: xml and txt submission on web page

John C Klensin <john-ietf@jck.com> Fri, 15 June 2018 13:41 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2805130ED2 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2018 06:41:24 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 3eBeWPU7Phj5 for <ietf@ietfa.amsl.com>; Fri, 15 Jun 2018 06:41:22 -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 DEE7F130ED3 for <ietf@ietf.org>; Fri, 15 Jun 2018 06:41:21 -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 1fToyc-000Hol-I2; Fri, 15 Jun 2018 09:41:18 -0400
Date: Fri, 15 Jun 2018 09:41:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Julian Reschke <julian.reschke@gmx.de>
cc: ietf@ietf.org
Subject: Re: xml and txt submission on web page
Message-ID: <B38B022522FC3DFAC09E1258@PSB>
In-Reply-To: <7ded41cd-9e0a-03b8-181d-ec3293024f7d@gmail.com>
References: <fcee1ad8-255c-5619-1945-bab24c95ca89@gmail.com> <6c352737-991e-c4c2-a104-e7ebfe548009@forfun.net> <4E469EA123CE8A23BCF57C77@PSB> <8f6fc380-85ab-d012-2869-0ea0b821a4c7@gmail.com> <0813D666DD13EF9BB96D0992@PSB> <0e4353ce-72dd-a804-761e-10790d421c3f@gmail.com> <93807EEB-6FF7-447B-8330-85540CC51AAB@vigilsec.com> <bb906889-1383-7a1f-9f18-ff67f71424b3@gmail.com> <9FAE6A35-21E1-4B02-9ECA-4B3BC19517BF@vigilsec.com> <5db2ae76-c53c-700e-ac59-a8f6ee1ab56c@gmail.com> <0807a932-6820-5629-5ac1-1c3fbb790d63@gmail.com> <F76094B0-469A-4E7E-A110-388A2E763990@isc.org> <87c3ee6f-38e9-7596-f385-aa4a74d26885@gmail.com> <9d46ab31-52a7-8cbd-14bb-fbe3dd2b497d@gmx.de> <7ded41cd-9e0a-03b8-181d-ec3293024f7d@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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/ietf/CQmEVSjiaLQfHGZYBbJEVMl6q3g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2018 13:41:25 -0000

Julian,

I understand the reasoning and those of us who use the
submission system (and XML2RFC, etc.) frequently have long ago
gotten used to the conventions.   However, it seems to me that
having xml2rfc enforce those conventions (e.g., by generating a
warning message when "draft-foo-bar.txt" appears rather than
"draft-foo-bar-00" would be rather easy.   Compared to that and
while I'm sure it is unintentional, the present situation
somewhat resembles a hazing process of torturing newcomers until
they eventually figure things out, get enough advice and/or
abuse, and thread their way through sufficient documents to be
considered worthy to join the club.  

I think we should be able to do at least a little bit better,
don't you?

best,
    john


--On Friday, June 15, 2018 14:23 +0200 Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:

> 
> 
> Le 15/06/2018 à 11:48, Julian Reschke a écrit :
>> On 2018-06-15 11:01, Alexandre Petrescu wrote:
>>> ...
>>> Yes, from an abstract layer.
>>> 
>>> But from a mundane point of view:
>>> 
>>> Among 'draft-person.txt' and 'draft-person'
>>> which one is a 'full draft name'?
>>> ...
>> 
>> See 
>> <https://greenbytes.de/tech/webdav/rfc7749.html#element.rfc.a
>> ttribute.docName>. 
> 
> Please, if you want feedback from me, do not point me to URLs.
> URLs take time to click, and are invisible after some time
> whereas the message is still visible.
> 
> Better - paste the content here, so I can reply to it.
> 
> Of course, you are free to walk me back and forth between all
> sites of the Internet and wikipedia, and I will take advantage
> of that walking back and forth to maybe check whether it is
> secure, or whether it is IPv6 or just IPv4, or others.
> 
> But if we want to stay to the point, and if we are open to
> remarks and difficulties, and if we want to be kind to the
> humble submitter, then we listen.
> 
> That website says:
>> 2.33.3. "docName" Attribute
>> 
>> For Internet-Drafts, this specifies the draft name (which
>> appears below the title).
>> 
>> A processor should give an error if both the "docName" and
>> "number" attributes are given in the <rfc> element.
>> 
>> Note that the file extension is not part of the draft
> 
> How comes a file extension is not part of the draft?
> 
> Maybe it is not part of the draft _name_?
> 
> Nobody expects a file extension to be part of the draft
> (contents of that draft.)
> 
> Alex
> 
> , so in general it should end with the current draft number
> ("-", plus two digits).
>> 
>> Furthermore, it is good practice to disambiguate current
>> editor copies from submitted drafts (for instance, by
>> replacing the draft number with the string "latest").
>> 
>> See Section 7 of [IDGUIDE] for further information.
> 
> 
>> 
>> 
>> Best regards, Julian
>> 
>