Based on the positive feedback from my RFC-Editor graph, I've updated
some work that I started some time ago - a set of graphs, two per
working group. These graphs show inter-document dependencies(*) of
all I-Ds that are working group documents, and one "hop" forwards and
back - for example, if a foowg document depends on
draft-fenner-great-stuff, then the individual draft shows up, but not
*that* document's dependencies. The two graphs are <wgname>.pdf,
which includes relationships that my script could determine are not
normative, and <wgname>-norm.pdf which does not. Sometimes when the
full graph is too much, the -norm graph is still readable.
It's an interesting way to see what relationships exist, and what
other groups / documents may be referencing a given WG's work.
http://rtg.ietf.org/~fenner/ietf/deps/viz/
Each page includes a key for what the shapes and colors mean.
Feedback is welcome.
Bill
(*) - Of course, these dependencies are gathered programmatically,
using heuristics run over Internet Drafts, looking for filenames of
other drafts. This means that some dependencies are not found - e.g.,
references like
[Ken-Arch]Kent, S., and Seo, K., "Security Architecture for the
Internet Protocol", RFC ???, ??? 200?.
that are meant to be to an I-D are never seen in my data. (I'm not
picking on IPsec or this reference format - just noting the
limitations of my heuristics) The type of reference is also picked up
by heuristics, looking for sections titled, e.g., "Normative
References". I'm happy to look at the specifics of any document that
the heuristics failed on.
The actual data behind the graphs can be seen in my mysql database;
https://rtg.ietf.org/phpmyadmin/ user ietf password ietf database
draftdep table dep
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf