[Tools-discuss] Internet Draft Index Files Updates -- XML and HTML

[Fred Baker <fred at cisco.com>]

OK, dumb question.

We have tools that generate files like the attached. They are in the  
xml2rfc toolset. Any chance we could pull these together into an XML  
database similar to that of the RFC Editor's?

<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.hixie-thewebsocketprotocol'>
<front>
<title>The Web Socket protocol</title>

<author initials='I' surname='Hickson' fullname='Ian Hickson'>
    <organization />
</author>

<date month='August' day='15' year='2009' />

<abstract><t>This protocol enables two-way communication between a user agent running untrusted code running in a controlled environment to a remote host that understands the protocol.  It is intended to fail to communicate with servers of pre-existing protocols like SMTP or HTTP, while allowing HTTP servers to opt-in to supporting this protocol if desired.  It is designed to be easy to implement on the server side.Author's note This document is automatically generated from the same source document as the HTML5 specification.  [HTML5]  Please send feedback to either the hybi at ietf.org list or the whatwg at whatwg.org list.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-hixie-thewebsocketprotocol-34' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-hixie-thewebsocketprotocol-34.txt' />
</reference>



On Aug 17, 2009, at 6:05 PM, Brian E Carpenter wrote:

> Hi,
>
> Thanks for this.
>
> Is there any reason not to add the stream info to the .txt version
> of the index?
>
> Regards
>   Brian
>
> On 2009-08-15 07:42, RFC Editor wrote:
> > Greetings,
> >
> > FYI, we have added stream information to RFC indices (XML and HTML)  
> > as
> > mentioned in Section 6 of
> > draft-iab-streams-headers-boilerplates-08. Stream is as defined in  
> > RFC
> > 4844 (IETF, IAB, IRTF, or Independent) or Legacy*. In the case of  
> > IETF
> > stream, the area and WG acronym are included.
> >
> > The following files will be updated on Monday (17 August 2009) to
> > include Stream information:
> >
> > Hyperlinked index of RFCs:
> >  http://www.rfc-editor.org/rfc-index.html  (ascending by RFC number)
> >  http://www.rfc-editor.org/rfc-index2.html (descending by RFC number)
> >
> > XML index of RFCs:
> >  ftp://ftp.rfc-editor.org/in-notes/rfc-index.xml
> >
> > XML schema:
> >  ftp://ftp.rfc-editor.org/in-notes/rfc-index.xsd
> >  Note: The new elements are <stream>, <area>, and <wg_acronym>.
> >
> > Each of these files is linked to from
> > http://www.rfc-editor.org/rfc.html.
> >
> > *As noted previously (regarding metadata pages), some RFCs are marked
> > Legacy, indicating that source information was not recorded for this
> > RFC; we are working on updating this information for RFCs for which  
> > it
> > exists.
> >
> > Thank you.
> >
> > RFC Editor
> >
> > > From Section 6 of draft-iab-streams-headers-boilerplates-08:
> >
> >   Adding a reference to the stream in the header of RFCs is only one
> >   method for clarifying from which stream an RFC originated.  The RFC
> >   editor is encouraged to add such indication in e.g., indices and
> >   interfaces.
> > _______________________________________________
> > rfc-interest mailing list
> > rfc-interest at rfc-editor.org
> > http://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss at ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss