-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Lyndon" == Lyndon Nerenberg <lyndon@orthanc.ab.ca> writes:
Lyndon> - give me a list of all the documents "belonging" to a particular
Lyndon> WG
Ironically, it is easier with IDs than RFCs :-)
Lyndon> - for any given RFC, show me the chain of document dependencies
Lyndon> (obsoletes, updated by, obsoleted by) that pass through this
Lyndon> document
Lyndon> - for any given RFC, generate a dependency graph based on the
Lyndon> normative references in this document
...
Lyndon> I'm not sure how to address the problem with legacy RFCs. I'll
Lyndon> bet we could find volunteers to generate XML equivalents from the
For this kind of thing, you don't need the entire document in XML, just
the references.... I believe that all of the RFCs have been converted such
that they can be referenced. Adding what they reference wouldn't be that
hard at this point.
Lyndon> And just to eliminate any lingering doubt, I'll note that I'm now
Lyndon> using xml2rfc for all my current and future drafts. (There,
Lyndon> *that* just gave several people heart attacks ;-)
] Out and about in Ottawa. hmmm... beer. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat
iQCVAwUBP1UNCIqHRg3pndX9AQHEOwP8CcwObPWYdXkzHkQk0EoQ3qtkUEOq+1PW
G483bW66OqLShldAeZEwJHFMgu1RDz1fMY/i4ylNq/62IP6Jxr30/QleAVQ7DsVL
64MyzR4XOK/OQjlgtiyE88hzou9vPwuwOUkw2awjtDRQVn09PjcMFPHxWXKTzGYD
R1IUCKC5KRg=
=IhDN
-----END PGP SIGNATURE-----