• 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

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. 

• iati-activities/@version is MANDATORY
• iati-activity/@version is DELETED 
• 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
• see also a similar proposal for the Organisation Standard

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/109

Segmentation and file size

• 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

Redefine activity-website as a document-link

• Remove the iati-activities/iati-activity/activity-website element
• Add documentary-category codelist categories for Organisation Webpage, Sector Webpage, Country Webpage and Activity Webpage
• for discussion go to http://support.iatistandard.org/entries/76684383-Redefine-activity-website-as-a-document-link

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/118

Allow multiple languages to be specified for a single document

• Change cardinality of document-link/language from single to multiple occurrences
• This applies to both Activity and Organisation standard
• for discussion go to http://support.iatistandard.org/entries/77513977-Multiple-languages-per-document

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/130

Delete all previously deprecated items

• Delete elements, attributes and codes that have previously been deprecated.
• Delete (not deprecate) elements, attributes and codes that are being removed in this upgrade.
• for discussion go to http://support.iatistandard.org/entries/78002476-Delete-previously-deprecated-items
• see also http://support.iatistandard.org/entries/51310806-Delete-don-t-just-deprecate-codes-in-2-01 

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/114

Planned-disbursement Type

• Delete planned-disbursement/@updated 
• Add planned-disbursement/@type (using IATI codelist BudgetType)
• for discussion go to http://support.iatistandard.org/entries/77495498-Align-planned-disbursement-with-budget

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/117

Addition to RelatedActivityType Codelist

• Add a value to the codelist:
• 5 - Third Party - A report by another organisation on the same activity (excluding activities reported as part of financial transactions - eg. provider-activity-id - or a co-funded activity using code = 4)
• for discussion go to http://support.iatistandard.org/entries/76862583-Referencing-another-publisher-s-report-of-the-same-activity

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/131

Vocabulary Codelists

• Add Sector Vocabulary codelist (derived from current Vocabulary codelist) and link to sector/@vocabulary
• Add Policy Marker Codelist and link to policy-marker/@vocabulary
• for discussion go to http://support.iatistandard.org/entries/78019646-Separate-vocabulary-codelists

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/132

Date and DateTime formats

• All dates must now validate against xsd:date
• All datetimes must now validate against xsd:datetime
• for discussion go to http://support.iatistandard.org/entries/77542148-Date-and-DateTime-formats

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/133

URL validation

• Where links are expected we have changed some datatypes from xsd:string to xsd:anyURI

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/116

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/129

Rename crs-add/aid-type-flag

• Rename the element iati-activity/crs-add/aid-type-flag to iati-activity/crs-add/other-flags
• Rename codelist AidTypeFlag to CRSAddOtherFlags 
• for discussion go to http://support.iatistandard.org/entries/29705458-Confusion-Between-Aid-Type-Flag-Type-of-Aid- 

For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/140

Add contact-info/department

• Add a new element iati-activity/contact-info/department
• This also requires a narrative sub-element 
• For discussion go to http://support.iatistandard.org/entries/44571616-Organisational-unit-within-contact-details

 For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/141

Description Type

[added 08-09-2014 - this is a bug fix]

• All description types currently contain a type attribute. This is only applicable to iati-activity/description
• Delete the following attributes
• country-budget-items/budget-item/description/@type
• result/description/@type
• result/indicator/description/@type

 For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Schemas/issues/163

Review Embedded codelist descriptions

[added 10-09-2014]

• Embedded codelist descriptions have been reviewed and updated - https://docs.google.com/spreadsheets/d/1gVpcS8DR_-QDB8pxKdPHRuuRPmWs1yIWfBaGAhXDwew/edit

 For technical details about implementing this proposal go to: https://github.com/IATI/IATI-Codelists/issues/3