"Negative Delta" file approach

Hi everyone

For long term discussion, we need to formulate our proposal for the "Negative Delta" file approach, that we all agreed in the previous meeting was preferable to simply just deleting invalid existing content. The aim is to provide a valid methodology by which we can remove technical/content anomalies that would otherwise have been permanent invalid features, without providing any benefit to the terminology.
The proposal would need to enable to cleansing of these issues within the existing RF2 structure, whilst not losing the complete audit trail (as we do with deletion), providing a machine readable way to trace the history going forwards.

This will likely have a reasonable impact on the users in the community, and so this change will have to be thoroughly disseminated out and socialised with all members, vendors and affiliates, so let's start putting the proposal together now with the aim to finalise it in October, and socialise it in time for inclusion in the July 2018 International Edition.

Please submit all of your thoughts on pros/cons, and proposals of how best this will work (including any technical restrictions, etc).

Thanks very much!

Andrew