IATI Consultations Archive

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

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

Avatar
Bill Anderson
Follow
This is part of the formal proposal that makes up the second 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: 

Enforcing Order on the Schema

  • The order in which elements are reported MUST follow the sequence dictated by the Schema.
  • Schema cardinality rules are enforced.
  • for details and discussion go to http://support.iatistandard.org/entries/76669023-Enforcing-Order-on-the-Activity-Schema

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 [Removed 29-08-2014]
    • 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
  • Once an activity has been reported to IATI its identifier MUST NOT be changed in subsequent updates, [Added 29-08-2014]
  • It MUST be prefixed with the organisation-identifier found in reporting-org/@ref [Removed 29-08-2014]
  • It MUST be prefixed with the organisation identifier referenced in reporting-org/@ref when the activity was first reported. [Added 03-09-2014]
  • 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

Title 

Description

Activity Date

Sector

Transaction

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

Have more questions? Submit a request

2 Comments

Date Votes
  • 0
    Avatar
    IATI Tech Team

    Following on from continuing discussion on the mailing list  (comments from Herman van Loon, Bill Anderson and David Megginson) the proposal (see above) for the activity identifier has been modified to read:

    IATI activity identifier

    • The iati-identifier is MANDATORY
    • It MUST be globally unique among all activities published by a single reporting organisation
    • Once an activity has been reported to IATI its identifier MUST NOT be changed in subsequent updates,[Added 29-08-2014]
    • It MUST be prefixed with the organisation-identifier found in reporting-org/@ref [Removed 29-08-2014]
    • It MUST be prefixed with the organisation identifier referenced in reporting-org/@ref when the activity was first reported. [Added 03-09-2014]
    • The identifier MUST only contain alphanumeric characters and hyphen, underscore, colon or period

     

  • 0
    Avatar
    IATI Tech Team

    Edits have made to the proposal above in line with Bill Anderson's 29-08-2014 post on http://support.iatistandard.org/entries/77310197-Version-2-01-Iteration-2-5-A-consistent-approach-to-OECD-DAC-organisation-identifiers

Article is closed for comments.