Tightening up on version

Bill Anderson

June 29, 2020 09:41

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 DELETED
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

Have more questions? Submit a request

4 Comments

Date Votes

0

Ben Webb June 16, 2014 15:47

Should the same rules that apply to iati-activities/@version and iati-activity/@version also apply to iati-organisations/@version and iati-organisation/@version? I think having this be consistent across the two schemas would be useful.

Comment actions Permalink
0

Bill Anderson August 13, 2014 08:46

On 12 August 2014 the IATI Technical Team reviewed this issue and took note of Herman van Loon's argument here - http://support.iatistandard.org/entries/50761977--version-should-be-consistent.

The team agreed that duplication was not the best solution and decided to drop the proposal that individual activities MUST contain a version. It agreed that a separate solution should be found to record versions on individual activity blobs, as delivered by the Data Store and other services.

Comment actions Permalink
0
IATI Tech Team August 26, 2014 11:25
Discussion on versions is now split across a number of posts, so for clarity:
- The (revised) proposal for iati-activities/@version can be found here - http://support.iatistandard.org/entries/77311697-Version-2-01-Iteration-2-8-Miscellaneous
- The proposal for iati-organisations/@version can be found here - http://support.iatistandard.org/entries/76652763-Version-2-01-Iteration-2-6-Improvements-to-the-Organisation-Standard
Comment actions Permalink
0

IATI Tech Team August 26, 2014 14:38

Omitted to record that the logic of enforcing only iati-activities/@version means that iati-activity/@version should be DELETED

Comment actions Permalink

Article is closed for comments.

IATI Consultations Archive

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

Tightening up on version

4 Comments