SDK metadata to assist migration of existing notices

[rousso]

We are considering adding a new folder to the SDK to support the migration of existing notices from one SDK version to another. For instance, if a field has been functionally replaced by a different field, or a codelist has been substituted, we’d like to include metadata in the SDK that enables applications to map values from the older version to the newer one.

The current idea is to introduce a migration folder in the SDK, where this information will be stored in JSON format. The specific encoding is still undecided, so any feedback you can share now would be valuable.

[subreport-jk]

In our implementation, we effectively do a comparison between two versions of the fields.json and extract the nodes and fields that have been added, moved or removed and then use that information to generate xslt files we can apply to achieve the necessary transformation of our data structure.

Having this information provided to us in the SDK would probably not have a huge impact on our approach, but it would at least allow us to cut out the "cherry picking" part.