IATI Version 2.03 - Update

Delays / Concerns Vision Governance Content

Candidate Technical Implementation Timeline Candidate Content Candidate Technical Implementation Candidate Schema Tools update Release Candidate Go Live 1 Oct 8 Jan

Content Humanitarian Results Codelists Miscellaneous

Humanitarian Pledges (FTS Compatibility) Modalities (Cash Transfers, Ear-marking) Organisation Types (Localisation)

Results Disaggregation (Consistency across baseline, target, actual) Qualitative reporting (Free-text, ordinal) Indicator vocabularies (At result OR indicator level) Document-links

Codelist Management Re-categorising embedded codelists (Embedded, Non-embedded, replicated, third-party) Organisation identifiers

Miscellaneous Improving definitions relating to traceability, hierarchies and secondary reporters CRS Channels of delivery can describe participating organisation Flag activities for which forward-looking budgets are not appropriate ‘Sector-type’ classifications that be apportioned percentage splits

Revision of Upgrade Processes Paper 10 Members’ Assembly Meeting 03-05 October 2017

Current Rules

Underlying principles The Standard is a logical implementation of IATI’s vision and mission The aim of the Standard is to enable the delivery of timely, comprehensive and forward-looking data to all users The Standard needs to reflect the changing nature of development cooperation and humanitarian aid as well as innovations in interoperability and the information technology landscape IATI is a multi-stakeholder initiative and the Standard needs to reflect the needs of its diverse communities

Separating Content and Implementation What problem will the change solve? Real-world use case Implementation How do we solve the problem? Translation of content into schema

Semantic Versioning Current New Type No. Integer 2.01 Major 3.0.0 Decimal 2.02 Minor 3.1.0 - Patch 3.1.1

Governance Major Members’ Assembly is responsible for initiating and approving. Governing Board is responsible for overseeing progress Minor Governing Board responsible for initiating, overseeing and approving. Patch Technical team in open consultation with community under direction of Secretariat.

Consensus Wherever possible decisions on changes to the standard should be reached by consensus Consensus means an absence of active dissent amongst those involved in the consultation process If consensus cannot be reached the matter will be referred to the Governing Board for its assistance in resolving the dispute The Governing Board, taking note of advice from the TAG Chair and the Technical Lead, may adjudicate on an unresolved dispute.

Timelines (TAG) Initiation Content consultation Content approval Technical Consultation Technical approval Technical Implementation Final approval