Some WG's produce a "roadmap" document that does this. However, experience
shows that a large number of related drafts is a situation to be avoided
wherever possible. It seems like a good idea at first, but if they
need to cross-reference each other it becomes a nightmare to keep them
all in sync. Years later backlash sets in.
On Wed, 9 Apr 2003 at 10:43:27 -0600 (MDT) Alex Rousskov asked:
Also, given a relatively large number of related drafts, would it make
any sense to have one short "OPES Requirements" draft that lists all
available drafts and describes the relationship between them? Or do we
want to repeat pretty much the same explanations in every draft
instead? Are there similar cases in other WG?