Re: [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
Kent Watsen <kent+ietf@watsen.net> Tue, 26 February 2019 16:25 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 77F72130EF5 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 08:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=amazonses.com
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 MJXA1bFUS57T for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 08:25:00 -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 39998130ECF for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Feb 2019 08:25:00 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 73EF3B8220F; Tue, 26 Feb 2019 08:24:40 -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 86D94B8220F for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 4Hje-ZDQM4gb for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:24:36 -0800 (PST)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) by rfc-editor.org (Postfix) with ESMTPS id C5707B8220E for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 08:24:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1551198294; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=HQnnG5QnV99os7N54WDbApMxmOglPPi1CHNlNbSxpis=; b=BTTqj2FvH4/A41L39ULJLkR29YyUR9Plhns6QOFqkNx5Kw/lV/gR1m2RoqA6uC15 eIV7L77YiO0frc+kcV9nqR3EG5BE+1UjWAL3W+ylId0deOSr+F5L5qFEznTB/zhwSQw DyZH1zre6vXK+QTgn6BA3tcnaDH7r2Tv/pTZYRs0=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001692a9f8f0f-a4ba1870-6959-4518-8503-6e30424b1ac9-000000@email.amazonses.com>
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 26 Feb 2019 16:24:54 +0000
In-Reply-To: <2e4a853c-6622-81e8-adf5-02deb3e1d6e3@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
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>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.02.26-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
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-Type: multipart/mixed; boundary="===============6354422054801818942=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Hi Julian, > I notice that you seem to propose new extension attributes for stuff you can already do without. See, in particular, > > https://greenbytes.de/tech/webdav/rfc7991.html#element.artwork.attribute.name > > https://greenbytes.de/tech/webdav/rfc7991.html#element.sourcecode.attribute.name Yes, I was originally using the "name" attribute, but then I found that prep tool was using "originalSrc", which made more since to me, since the goal is to capture the entire path (more than just the name). > https://greenbytes.de/tech/webdav/rfc7991.html#includingexternal <https://greenbytes.de/tech/webdav/rfc7991.html#includingexternal> I'm familiar with XInclude, but note that more than just including a file is going on (e.g., date substitutions, content generation, validation, etc.). > The following discussion about CODE BEGIN etc should also be interesting: > > <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/8> 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. Kent
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Fwd: New Version Notification for draft-k… Kent Watsen
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Kent Watsen
- Re: [rfc-i] Fwd: New Version Notification for dra… Julian Reschke
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] New Version Notification for draft-kw… Kent Watsen
- Re: [rfc-i] New Version Notification for draft-kw… Julian Reschke
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] New Version Notification for draft-kw… Kent Watsen
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Joel M. Halpern
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Julian Reschke
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Kent Watsen
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Julian Reschke
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Julian Reschke
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Kent Watsen
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Henrik Levkowetz
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Stephan Wenger
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Kent Watsen
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Carsten Bormann
- Re: [rfc-i] [Ietf-and-github] New Version Notific… Kent Watsen