I suspect that in many cases, end-users are going to be most
comfortable with your approach as opposed to a more technically
correct method that requires them to imagine how the topics under
review will actually appear in documents.
How much reuse is there of your topics?
If you are only actually producing a small number of documents,
people may be most comfortable reviewing the intended outputs.
This has the advantage of also detecting issues with map files as
well as content questions. The downside is that you may also have
to provide the git history to help reviewers focus on the changes
since the last review.
This puts an onus on the editors to create useful comments when
committing changes which is not a bad thing!
Ron
--
You received this message because you are subscribed to the Google Groups "DITA-OT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--