Version 2.01 - Iteration 1 - 1. Strengthening the Core of the Standard – IATI Support

This is part of the formal proposal that makes up the first iteration of the Version 2.01 Upgrade process.

The current standard has very few mandatory fields. The main reason for this is that in Version 1.01 all mandatory validation was done via the XML Schema, and it is very difficult using XML logic alone to apply such rules. Additional validation procedures have since been established to now propose that all activities under all circumstances should always contain:

Reporting organisation

The reporting-org element is MANDATORY.
ALL the following rules must apply to the organisation-identifier in reporting-org/@ref

It is mandatory
The agency prefix MUST be a valid code in the IATI code list
The identifier MUST be the prefix to the iati-identifier
The identifier MUST be the same as that recorded by the publisher on the IATI Registry
The identifier MUST only contain alphanumeric characters and hyphen, underscore, colon or period

for discussion go to http://support.iatistandard.org/entries/41097678-Modify-reporting-org-ref-validation-and-guidance

IATI activity identifier

The iati-identifier is MANDATORY
It MUST be globally unique among all activities published by a single reporting organisation
It MUST be prefixed with the organisation-identifier found in reporting-org/@ref
The identifier MUST only contain alphanumeric characters and hyphen, underscore, colon or period
for discussion go to http://support.iatistandard.org/entries/41097918-Modify-iati-identifier-validation-and-guidance

Participating organisation

At least one occurrence of participating-org is MANDATORY
For each occurrence of participating-org @role is MANDATORY
For each occurrence of participating-org @ref or text() is MANDATORY
for discussion go to http://support.iatistandard.org/entries/41047217-Modify-participating-org-Validation-and-guidance

Title

The title is MANDATORY
It is recommended that the title contains a meaningful summary of the activity
for discussion go to http://support.iatistandard.org/entries/41584666-Modify-title-validation-and-guidance

Description

The description is MANDATORY
It is recommended that the description contains a meaningful description of the activity
for discussion go to http://support.iatistandard.org/entries/41584706-Modify-description-validation-and-guidance

Activity Date

At least one occurrence of activity-date is MANDATORY
All activities MUST contain a start date: either planned or actual
for discussion go to http://support.iatistandard.org/entries/41089758-Modify-activity-date-validation-and-guidance

Sector

At least one occurrence of Sector is MANDATORY
sector/@code is MANDATORY
If Sector/@vocabulary is not present then the DAC vocabulary is assumed
Use of DAC codes (either 5-digit or 3-digit) is recommended
for discussion go to http://support.iatistandard.org/entries/22993317-Modify-sector-validation-and-guidance

Transaction

At least one occurrence of Transaction is MANDATORY
New activities should not be reported until the initial Commitment is available to be published.
for discussion go to http://support.iatistandard.org/entries/55997436-Modify-transaction-validation-and-guidance

Technical details about implementing this proposal can be found at: https://github.com/IATI/IATI-Schemas/issues/66

IATI Consultations Archive

Live discussions and consultations can be found at discuss.iatistandard.org.

Version 2.01 - Iteration 1 - 1. Strengthening the Core of the Standard