The notion behind the content repository is that the pieces which display content work with items, not revisions - the live revision is the one which should always be shown.
So any existing code you might want to use is structured this way, in particular code that lets you attach forms or templates to items. It's all very consistent and I don't think we want to start breaking that consistency. Karl Goldstein and his crew thought this stuff out in detail when they designed it, and I think the basic design is sound.
Are you wanting to in essence provide an audit trail of the changes in classification?
