Why not just add the revision foreign keys directly to your revision type rather than deal with a mapping table at all for this case?
It sounds like you're tying revisions tightly together, which, as Dave points out, is CR abuse, but if it's justified ... why not do it directly? Or is this a many-to-one or many-to-many mapping (if true then a custom mapping table seems like the right thing to do).
