You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Brief Description
The Standard implicitly prohibits non-empty IATI Identifiers for activities, by saying that they MUST be composed of certain prefixes and suffixes. However, this is only in the human readable text, and not part of the Ruleset, or the XML Schema. As such, activities that have empty identifiers are currently marked as valid, and need not trigger any errors or warnings.
Expected Results/Behaviour
Activities with empty identifiers should fail validation based on XML Schema, or at least the Ruleset.
Actual Results/Behaviour
Currently they are let through by the Validator (because it just implements the Schema and Ruleset), with the result that activities with empty identifiers can enter into the tool chain. This has caused problems for some tools.
The text was updated successfully, but these errors were encountered:
Brief Description
The Standard implicitly prohibits non-empty IATI Identifiers for activities, by saying that they MUST be composed of certain prefixes and suffixes. However, this is only in the human readable text, and not part of the Ruleset, or the XML Schema. As such, activities that have empty identifiers are currently marked as valid, and need not trigger any errors or warnings.
Severity
Medium
Issue Location
https://iatistandard.org/en/iati-standard/203/activity-standard/iati-activities/iati-activity/iati-identifier/
Expected Results/Behaviour
Activities with empty identifiers should fail validation based on XML Schema, or at least the Ruleset.
Actual Results/Behaviour
Currently they are let through by the Validator (because it just implements the Schema and Ruleset), with the result that activities with empty identifiers can enter into the tool chain. This has caused problems for some tools.
The text was updated successfully, but these errors were encountered: