Re: [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt

Julian Reschke <julian.reschke@gmx.de> Tue, 26 February 2019 16:33 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715B312F1AB for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 08:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.181
X-Spam-Level:
X-Spam-Status: No, score=-5.181 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.018, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 RsXdNswGo94d for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 08:33:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA460130EEA for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Feb 2019 08:33:18 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 43DCFB82256; Tue, 26 Feb 2019 08:32:59 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 4A65EB82256 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nnh5mIpJwtb1 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:32:56 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by rfc-editor.org (Postfix) with ESMTPS id 55F33B82255 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:32:56 -0800 (PST)
Received: from [192.168.178.124] ([91.61.52.137]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfVzj-1gf5Nw3USp-00P4rQ; Tue, 26 Feb 2019 17:33:07 +0100
To: Kent Watsen <kent+ietf@watsen.net>
References: <155112114000.10633.2593235416875795961.idtracker@ietfa.amsl.com> <01000169261421c7-978ecbf5-dcc4-4738-ba58-f409ce6adaf1-000000@email.amazonses.com> <2e4a853c-6622-81e8-adf5-02deb3e1d6e3@gmx.de> <010001692a9f8f0f-a4ba1870-6959-4518-8503-6e30424b1ac9-000000@email.amazonses.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ea32731b-55cf-aa67-a87a-184dfbad6d49@gmx.de>
Date: Tue, 26 Feb 2019 17:33:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <010001692a9f8f0f-a4ba1870-6959-4518-8503-6e30424b1ac9-000000@email.amazonses.com>
Content-Language: en-US
X-Provags-ID: V03:K1:7BggZyH25KrWZKq3mudF7Ic1hzsClJyY5nXBlRXGZQd6wWio88D TlViuKnUIHdbSpNFBTGl3m1EQWxZgRQM4roBzYGxsilF/K9LV/Yvl8ikYSUlwnX0HNVkQML GZX6HpcHkSAx0XFtMJzbFv2cNzpnAIf2XOihgvO67JPm7+gerb8r6GfzFSysnlr/O3Eoosj 2MdTz2o7lYC/FGCMd45IA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:5sYg1NwVVZA=:75etJUOtkie4DnQQmiqKIn PccvvvEKqa48N+c76Pq2MMK4hUUdQmiqHpF3PxMDczDs4O2beAtnKVEOOHeI0dPxaVYa1wkMO MUrGSkl/ep17slOnutIHLgj0U6CqGXiViCtg287YgEJl+IEGNVnWr1FdBiVBk+4v/ep0pyk3p D+uVAKN4FM8dZPlgqtpxuWA7FRpLV+TZVyP95SKP5yI2tEDemwchnoe+S3TEyrbxkoaOJlYeT 3dSTBmqHfx1TaGHWJS0wFgG6JqkI2Px1CuG5IjW5JyAsEBaMhzy1rETLb6cePM/3SnybEwIIf NJvFWEWhIxZ+smMftscG12Bfl/JsR3N1Z2Av62RL6vILiooRPQLJU6p408LXfdnEjH/z9Fiff ombUKlnMkEvUkIKfYzTIwKmzedyXtNRWSKm4Ps07F1jPGBXQzhDy5P+IuemhuToNrsWgET5BZ YhWK6EgvBeC08G7iXKnU4i5Ozkd0gChb7jrqpFRw5QZvwyrx+LUyAchwnC+9etimmSIkVDP9S hgQu/oYWwe//gAqcqYDwZxgY2IWyhKehNldz6SNt5yapGUODzmt6c7GTZxJQc5HusK9WN60D1 SlGiiPCjysrTnBaWU3JdrWL+E51arxPmYfTqaZXwVoqA1R1MP4vlcUxk5dJRoRs+0+GDbITct HcD0fxr7Hp8zSS+urdbiaXvZQDfNiASaf4oFKe1VG7P2e56T3VIoFHwqpWnwc/JPMOTYFKGjf WujqcAUEdtinOSNwkA6VEyraRTxOH+rFtoERE+JbZ2C9FoSGcmQpwTbs850RSk0nFunzm5Te5 KRaPK+pJuKzTd4Dy3pXHf5N7No3FV2AnFnfTcakcNxXNx1bzFxe0+c3jl8DQiHhzYANQfgqSO +3PdE/tJnWZsIGeAopnqxel30YDDypXzO5FyE0uqd6Q/nmeJrJw02SLjVZNkuKStC9nOkSytU nwo90XUf1qg==
Subject: Re: [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, ietf-and-github@ietf.org
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 26.02.2019 17:24, Kent Watsen wrote:
> ...
> I hadn't seen this issue before, but I did see Henrik's comments about 
> markers in
> draft-levkowetz-xml2rfc-v3-implementation-notes.  FWIW, the 
> "xiax:markers" attribute
> is primarily only to support xml2rfc v2 documents; v3 documents can just 
> use the built-in
> "markers" attribute.
> 
> That said, I think that markers are, in general, a mistake.  That they 
> were only put their
> for tools scrapping plain-text documents.   Assuming tools extract from 
> XML, then no
> markers are needed, neither for framing (to aid the scraping process) or 
> for capturing
> the file's name (which is better served by the aforementioned "name" 
> attribute.
> ...

The original reason for "CODE BEGINS" etc was for licensing (to clarify 
that part of the content is considered to be a "code component").

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest