Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml

Sandy Ginoza <sginoza@amsl.com> Fri, 26 May 2017 19:18 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D6F1204DA for <tools-development@ietfa.amsl.com>; Fri, 26 May 2017 12:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, 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 HZhbOTgI2E9Y for <tools-development@ietfa.amsl.com>; Fri, 26 May 2017 12:18:05 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6BFC1201F2 for <tools-development@ietf.org>; Fri, 26 May 2017 12:18:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 2E37E1C6B8C; Fri, 26 May 2017 12:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqVbCAUgBUuL; Fri, 26 May 2017 12:17:54 -0700 (PDT)
Received: from sandygiozasmbp2.home (unknown [47.156.91.59]) by c8a.amsl.com (Postfix) with ESMTPSA id DE21D1C52E7; Fri, 26 May 2017 12:17:53 -0700 (PDT)
From: Sandy Ginoza <sginoza@amsl.com>
Message-Id: <EE7FE0BC-1B58-4E1E-AE2F-7889B38B3B69@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C9ADF92B-5320-4259-BCE3-9849C6A50B11"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 26 May 2017 12:18:04 -0700
In-Reply-To: <E5A96E3B-8D3A-4046-8D14-FCD260B66CA6@amsl.com>
Cc: henrik@levkowetz.com, tools-development@ietf.org, Alice Russo <arusso@amsl.com>
To: Megan Ferguson <mferguson@amsl.com>
References: <591F6199.60801@levkowetz.com> <E5A96E3B-8D3A-4046-8D14-FCD260B66CA6@amsl.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/DSOWdMB42RXxpCwoFj8AuPPXEvw>
Subject: Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2017 19:18:07 -0000

Hi All,

xml v2 does not handle the formatting for these types of reference entries, and I believe the goal for id2xml is to convert .txt to .xml v2 (so this will not be addressed via id2xml) — though, please correct me if I’m mistaken.  If not, we will continue to manually update these entries post xml2rfc. 

However, I am curious about where the reference information to create the XML entry is being pulled from.  Does it XMLize the text entry or does it pull info from somewhere else? 

Thanks,
Sandy

> On May 26, 2017, at 11:49 AM, Megan Ferguson <mferguson@amsl.com> wrote:
> 
> 2) I was curious about how a reference to a BCP that included more than one RFC would be handled (for example, BCP 9 below).  
> 
> 
> In text, it would appear as:
> 
>   [BCP9]     Bradner, S., "The Internet Standards Process -- Revision
>              3", BCP 9, RFC 2026, October 1996.
> 
>              Kolkman, O., Bradner, S., and S. Turner, "Characterization
>              of Proposed Standards", BCP 9, RFC 7127, January 2014.
> 
>              Dusseault, L. and R. Sparks, "Guidance on Interoperation
>              and Implementation Reports for Advancement to Draft
>              Standard", BCP 9, RFC 5657, September 2009.
> 
>              Housley, R., Crocker, D., and E. Burger, "Reducing the
>              Standards Track to Two Maturity Levels", BCP 9, RFC 6410,
>              October 2011.
> 
>              Resnick, P., "Retirement of the "Internet Official
>              Protocol Standards" Summary Document", BCP 9, RFC 7100,
>              December 2013.
> 
>              Dawkins, S., "Increasing the Number of Area Directors in
>              an IETF Area", BCP 9, RFC 7475, March 2015.
> 
>              <http://www.rfc-editor.org/info/bcp9 <http://www.rfc-editor.org/info/bcp9>>
> 
> 
> I don’t have a draft in queue to test this on, so I just manually added a reference to BCP 9 and corresponding citation 
> to draft-ietf-rtgwg-yang-key-chain-24.txt. Below is the resulting XML from id2xml:
> 
> <reference anchor="BCP9"><front><title>The Internet Standards Process -- Revision 3</title>
> 	<author fullname="S. Bradner" initials="S." surname="Bradner"/>
> 	<date month="October" year="1996"/>
> 	</front>
> 	<seriesInfo name="BCP" value="9"/>
> 	<seriesInfo name="RFC" value="2026"/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 	<reference><front/>
> 	</reference>
> 
> *Note - references to multi-RFC BCPs and STDs are rare and require manual post-xml2rfcv2 updates with our current tools. 
> The current possible workaround in xml is to include an <annotation> element.  However, I *believe* only one such element is allowed.