This is part of the formal proposal that makes up the first iteration of the Version 2.01 Upgrade process.
Combined usage of recipient-country and recipient-region
- Current guidance advising use of only one or other of these elements should be reversed
- recipient-region should only be used to indicate that the region as a whole is a recipient, not as an added description to a named recipient-country
- if both elements are used percentages must be reported and they should add up to 100% across all recipient- elements
- for discussion go to http://support.iatistandard.org/entries/41585486-Modify-recipient-country-and-recipient-region-merge-
For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/71
Tightening up on version
[added by the IATI technical team on 30 April 2014]
Up until now the need for publishers to accurately report the version of the standard that they are using has not been of great importance as all current versions are backwardly compatible. With an integer upgrade this is not the case and it becomes critical for consumers of IATI data to know which version they are processing. The version is reported in two places: at file level (iati-activities) and record level (iati-activity). The reason for this is to facilitate the processing of a single activity independent of the original file in which it was published (for example, from the data store) AND provide a speedy way for whole files to be processed. It is therefore proposed that:
- iati-activities/@version is MANDATORY
- iati-activity/@version is MANDATORY
- All @version attributes in a given file MUST have the same value
- The value of @version MUST be on the (new to 2.01) version codelist
- for discussion go to http://support.iatistandard.org/entries/57866638-Tightening-up-on-version
For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/109
Segmentation and file size
[added by the IATI technical team on 12 May 2014]
- In order to ensure that all all IATI-XML files can be handled by all consuming systems it is proposed that a limit of 40MB is placed on the size of any single XML file.
- Publishers are still encouraged to segment there data into meaningful chunks, BUT the guidance to segment by country is no longer necessarily considered to be best practice.
- (NB the rule that the activity iati-identifier must be unique still applies. i.e. the same activity should not be reported in two different files by the same publisher)
- for discussion go to http://support.iatistandard.org/entries/61867937-File-size-and-segmentation
For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Extra-Documentation/issues/145