IETF Logo Mail Archive

Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]

"HANSEN, TONY L" <tony@att.com> Thu, 19 December 2019 05:07 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 79D01120033 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 21:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.95
X-Spam-Level:
X-Spam-Status: No, score=-4.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 iCh_Pt0FVd32 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 21:07:15 -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 5D01A120018 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 18 Dec 2019 21:07:15 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 010CDF40721; Wed, 18 Dec 2019 21:06:56 -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 C7DC1F40721 for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 21:06:55 -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 Fb5KP5WZ1lXx for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 21:06:53 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) by rfc-editor.org (Postfix) with ESMTPS id 4757FF40720 for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 21:06:53 -0800 (PST)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id xBJ55k12033468; Thu, 19 Dec 2019 00:07:02 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049459.ppops.net-00191d01. with ESMTP id 2wyt1ahwgn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 19 Dec 2019 00:07:02 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id xBJ571t7010660; Thu, 19 Dec 2019 00:07:01 -0500
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [135.66.87.38]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id xBJ56tWF010594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Dec 2019 00:06:56 -0500
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [127.0.0.1]) by zlp27130.vci.att.com (Service) with ESMTP id 82AB54000538; Thu, 19 Dec 2019 05:06:55 +0000 (GMT)
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (unknown [130.9.129.152]) by zlp27130.vci.att.com (Service) with ESMTPS id 70065400A00F; Thu, 19 Dec 2019 05:06:55 +0000 (GMT)
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.138]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0468.000; Thu, 19 Dec 2019 00:06:54 -0500
From: "HANSEN, TONY L" <tony@att.com>
To: Pete Resnick <resnick@episteme.net>
Thread-Topic: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]
Thread-Index: AQHVtcYM4tABaWwSq02ZR4RhB/cWA6fA6LWA
Date: Thu, 19 Dec 2019 05:06:54 +0000
Message-ID: <78286BEB-CC6E-43D4-A43F-79E2FA9C19E0@att.com>
References: <0e6427dd-df73-4946-a688-e02e9d68ae65@joelhalpern.com> <64ec190d-62fe-bcf1-ffd6-012d0da403f3@gmx.de> <8A76E9C0-921E-42CF-8EDD-6F95A91C06F4@amsl.com> <84D67BB2-D6A0-4CE6-827F-ABD130E7B512@episteme.net>
In-Reply-To: <84D67BB2-D6A0-4CE6-827F-ABD130E7B512@episteme.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.9.133.194]
Content-ID: <873182DBB3E21F489BD305E63BE1AEA3@LOCAL>
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-18_08:2019-12-17,2019-12-18 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 mlxscore=0 mlxlogscore=694 clxscore=1011 phishscore=0 priorityscore=1501 malwarescore=0 adultscore=0 bulkscore=0 impostorscore=0 suspectscore=0 spamscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912190041
Subject: Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]
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-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 12/18/19, 12:10 PM, "rfc-interest on behalf of Pete Resnick" <rfc-interest-bounces@rfc-editor.org on behalf of resnick@episteme.net> wrote:

    Since we're on the topic: I don't see bibxml files for the STD and BCP 
    series available. It would be nice if the RFC Editor could create them. 
    For example, it would be nice to be able to simply include 
    reference.BCP.14.xml, which could contain:
    . . .
    
Oh goody, a small programming task for my end-of-year vacation. :)

Please peruse these directories and let me know what you think.

    http://xml2rfc.tools.ietf.org/public/rfc/bibxml-test/	uses xi:include
    http://xml2rfc.tools.ietf.org/public/rfc/bibxml-test2/	expands the references

If either is acceptable, I'll turn them loose with a more permanent reference name. 

What do you think of this as the permanent reference name?

    http://xml2rfc.tools.ietf.org/public/rfc/bibxml-bcp-fyi-std

	Tony



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

v2.23.0 | Report a Bug | By Email