As a Dynamic Document developer I have to deliver XML/Graphics to my customer. Our development process can span months/years and to manage milestone checkpoints a baseline is created for each. There are instances where a book or chapter map do not get revised from milestone to milestone, keeping them at the same version/iterations. The primary object, a book or bookmap, for any given baseline, may be the same version/iteration as the last. The best method of tying a baseline to a new primary object is to revise the book. This would ensure an "Export Compound Document" of a version/iteration would be exactly what was baselined.
i.e. Each baseline contains a new version of the primary object. Arbortext Browser would export the primary object and all associated and versioned dependents in that baseline. The structure is downloaded locally for delivery to the customer.
A solution could be that a baseline requires a revision change to the primary object. That could lock the baseline down to a version of the book, and all the linked dependents, that can then be exported with "Export Compound Document". Again books get minimally revised during development, so an automated revision to the book to create the baseline should solve this issue.