@version attribute on iati-activity about iati-schemas

[bill-anderson]

Should be in iati-activities only. (can't see the use case for two activities in the same file employing different versions)

Documentation should say: "defaults to the current version ..."

[stevieflow]

Is that a proposal to *remove" @Version from iati-activity? I had understood the rationale for including it was in the use case where people parse out activities (as in the datastore). In this case, how would we know what version these activity documents relate to (although granted, this is not in use currently)?

[bill-anderson]

Yup you're right, the use case is not for loading into the data store (which can inherit from iati-activities) but in the xml blobs that can be accessed separately.What then is the point of having it in iati-activities??

[stevieflow]

Please also note that the description text with this particular attribute is:

"A number indicating the IATI specification version in use. Defaults to "1.0" if not specified. It is required to specify this attribute if the document is using features specific to an IATI specification other than the initial 1.0 version."

Whereas for iati-activities it is just:

"A number indicating the IATI specification version in use."

[Bjwebb]

The purpose of having @version in iati-activities is so that a data user can easily look at a file, and work out what version of the IATI Standard is needed to interpret the file. I don't think it should be possible to have activities of differing versions in a file (as this is problematic for data consumers), but this is not a constraint we currently describe anywhere.

I've written my proposal for this up on the support forum http://support.iatistandard.org/entries/50761977--version-should-be-consistent

[Bjwebb]

This has been fixed in 2.01 by requiring both version attributes, and requiring that all versions in a file are the same:
http://support.iatistandard.org/entries/57866638-Tightening-up-on-version
#109