Question about updated 2.03 'value' attribute

(Eimantas Stonys) #1

Hello! I have a question. I am porting our application to support IATI v. 2.03. On the 2.03 changelog it says, that for iati-activities/iati-activity/result/indicator/period/target element, the attribute @value was made optional and rules for its use added (see: Although, in the documentation it doesn’t mention what are the possible values of this element.

In the discussion (Results – represent more than quantitative data (included 2.03)) Mike Smith says, that the @value attribute has to be a valid number. But is this official ? If so, what kind of number ? Why this number is not specified in the documentation ( ? Can it include absolutely any string ?

Hope someone can help me with this and tell me what are the ‘official’ requirements.

(Andy Lulham) #2

Relevant bit of the documentation (emphasis mine):


The target value.

This should be a numeric value if the measure is quantitative.

This value must be of type xsd:string.

Here’s the referenced change to the standard ruleset, checking that @value is present for quantitative measures:

There’s nothing checking that @value is numeric for quantitative measures.

(Eimantas Stonys) #3

Thank you very much Andy! I will implement the checking in our system (OIPA), but do you have any idea why such things are not in the official documentation and they’re hidden as links to issues in comments within… pull requests ??.. Do you know why there is 0 info in this in docs ?

For example for me it would make sense to add this to the documentation…

(Andy Lulham) #4

The IndicatorMeasure code descriptions are here:

I think I’d conclude from those descriptions that codes 1, 2, 3 and 4 are quantitative. I.e. the same thing that’s stated in the comment you link to. But you’re right that this is not made explicit, and perhaps it should be.

The rule I mentioned above is documented here:

So I’m not sure I’d agree that there’s 0 info on this in the docs. But there’s certainly always room for improvement! For instance, I think I’d expect element pages to link to relevant ruleset rules.