This item has been moved to the '2.02 Decimal Upgrade Proposals' forum for inclusion the upcoming decimal upgrade.

I assume this means adding "Reporting Organisation" as a value to the code list. 

I'm happy with this so long as the guidance stresses that this should be used only if it is absolutely necessary 

This proposal has been discussed amongst the IATI Technical Team following the end of the initial suggestion phase of the v2.02 upgrade.

The IATI Technical Team supports this proposal.  Furthermore, we suggest adding an attribute for publishers to report the URL of their chosen vocabulary.  

Further updates on work towards the practical implementation of this proposal into the version 2.02 of the IATI standard will be posted as part of this thread.

There is a possibly confusing distinction between RO sectors and RO regions:

• When using multiple sectors, the percentages for all sectors within one vocabulary should add up to 100.
• When using multiple regions: whould the percentages of all countries and all regions across all vocabularies add up to 100?

Maybe simpler: are you allowed to report regions from multiple vocabularies?

Please see below for the technical implementation that is suggested in the Version 2.02 - Formal Proposal:

Codelist addition: Region Vocabulary

• Add new code:

• Code: 99

• Name: Reporting Organisation

• Description: The region reported corresponds to a region vocabulary maintained by the reporting organisation for this activity.

• Add guidance for:

• iati-activities/iati-activity/recipient-region/@vocabulary

• iati-activities/iati-activity/transaction/recipient-region/@vocabulary

• If using your own vocabulary, it is recommended that this is used in addition to the DAC OECD region vocabulary (code 1).

This proposal has been added as a GitHub issue, for inclusion in the version 2.02 development branch of the appropriate code repository: https://github.com/IATI/IATI-Codelists/issues/87

This proposal has now been incorporated into a version 2.02 code repositories (see the above GitHub issue link for technical details). The relevant page on a development version of the 2.02 reference and documentation site is available to view here.

We welcome scrutiny on the implementation of this proposal and encourage the community to feedback and suggest solutions for any errors, omissions and problems. This should be done before Monday 7 December, when the process will commence to release version 2.02 as a live version of the IATI Standard. More information on the inspection phase is available here.