Hi, no sadly not. Attributes on the RevisionEntity are sufficient for data from the whole transaction or request scope (like logged in users, processing channel,...) but not for data for each single AUD-table-row. What if you would like to add a hash to each audit row?

The pull request's code changes are only a little refactoring so that the table modifications for ValidityAuditStrategy are not hardcoded any more. In my opinion it makes the framework just a little bit more extensible.