XML may not be the solution to the entire RFC generation process but it could certainly help those of use who programmatically scrape the text based documents to extract the basic info (references, obsoletes, updates, std, bcp, fyi, yada yada yada...) A subset of the DTD containing the summary info submitted along with the RFC text could be very useful. Cheers ----- Original Message ----- From: "Marshall Rose" <mrose+internet.xml2rfc@dbc.mtview.ca.us> To: "Lyndon Nerenberg" <lyndon@orthanc.ab.ca> Cc: "Paul Hoffman / IMC" <phoffman@imc.org>; <ietf@ietf.org> Sent: Tuesday, September 02, 2003 1:17 PM Subject: Re: A modest proposal - allow the ID repository to hold xml > > I'm not sure how to address the problem with legacy RFCs. I'll bet we > > could find volunteers to generate XML equivalents from the existing plain > > text documents. (We would need an XML tag to indicate which of the plain > > text or XML documents is considered authoritative.) > > actually, carl malamud and brad burdick wrote a script back in 99 that > had a 20% success rate on the legacy rfcs. the (unofficial) xml versions > of those rfcs is available online. > > steven connor did some work for me after that to produce xml versions of > the remaining rfcs which excluded the middle (i.e., just the front > matter and references sections got translated). > > so, it's not as much work as you'd think, but still far more work than > i'd like... > > /mtr > > > >