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

[Henrik Levkowetz <[e-mail]>]

On 2017-05-26 21:18, Sandy Ginoza wrote:
> 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.

For version 1.x of id2xml this is right.  The intention is to produce a
version 2.x of id2xml which will produce vocabulary v3 xml as part of the
current work.  At that time, entries like the one below should be
correctly parsed into xml (v3) by id2xml.

> 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?

That would be interesting to know, yes.

	Henrik

> Thanks,
> Sandy
> 
>> On May 26, 2017, at 11:49 AM, Megan Ferguson <[e-mail]> 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.
> 
> 
> 
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-development
>