Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the XML Schema or the Ruleset check for empty IATI Identifiers in activities #500

Open
simon-20 opened this issue Jul 24, 2024 · 3 comments

Comments

@simon-20
Copy link

simon-20 commented Jul 24, 2024

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.

@stevieflow
Copy link
Contributor

Nice, thanks @simon-20

Have you an example activity / file that currently illustrates this?

Thanks

@simon-20
Copy link
Author

Yep, the activities at the end of this dataset currently have empty <iati-identifier> elements:

https://iatiregistry.org/dataset/ares-programme22-27

@stevieflow
Copy link
Contributor

Ah yes - can see that , thanks @simon-20

Should an activity / file fail this, it should declared as Critical imho

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants