At the moment the IATI standard does not allow the use of multiple vocabularies
recipient- region at transaction level.
The guidance currently states that @vocabulary attribute is only allowed to exist
1 for the following elements:
See Activity Summary table for reference.
This has been flagged as an issue for users who want to classify their data using multiple vocabularies and also in line with the below recommendation in the guidance.
Given that the community agrees that multiple vocabularies should be allowed, there are two suggested options:
- Consider this as a bug fix and fix immediately.
- Issue should be taken forward at the next decimal upgrade.
Please comment in response to this post.