Current IATI rules state that EITHER recipient-region OR recipient-country should be used. The rules also state that when multiple countries or regions are reported a percentage split should be reported which must add up to 100%. This is unsatisfactory as an activity may well include both regional and country-level spending. Here are four possible solutions.
- Allow for both existing elements to be used with the percentage split shared between them.
- Allow for the reporting of region and country at transaction as well as activity level
- Deprecate recipient-region and recipient-country and replace them with a single recipient element and a single recipient code list. (Given that there is no single globally agreed list of region definitions this approach is challenging)
- Deprecate recipient-region and recipient-country and replace them with a single recipient element. Add a new @type attribute to allow for the distinction between code lists.
A combination of 1. and 2. may be the best solution?