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

9.48.1 The OECD DAC policy-marker significance values are tested when the vocabulary 99 is used #327

Open
stevieflow opened this issue Feb 14, 2024 · 2 comments
Assignees
Labels
question Rules where we have a question

Comments

@stevieflow
Copy link

I provided some data - eg:

<policy-marker code="1" significance="5" vocabulary="99"/>

The validator finds an error in this:

Firefox_Screenshot_2024-02-14T10-24-07 065Z

Here; the objection is that a significance value of 5 is not on this codelist: https://iatistandard.org/en/iati-standard/203/codelists/policysignificance/ (there are only values 0-4)

However, I have stated that the policy-marker in play here is of vocabulary 99. From this test, the logic seems to be that:

  • all policy-markers must use the same significance code list, regardless of vocabulary

I don't think that is intended - but there's no documentation or guidance to explain this, either in the schema or any associated docs

The closest I can find is a rule:

When using a reporting organisation policy marker code (vocabulary 99), it must include a narrative.

--> @markbrough any thoughts?

cc/ @Bjwebb

@stevieflow
Copy link
Author

@akmiller01 just pinging you on this --> wondered if you know if this logic came through during the build of the validator, maybe? Thanks

@stevieflow stevieflow changed the title The OECD DAC policy-marker significance values are tested when the vocabulary 99 is used 9.48.1 The OECD DAC policy-marker significance values are tested when the vocabulary 99 is used Feb 20, 2024
@stevieflow stevieflow added the question Rules where we have a question label Feb 20, 2024
@akmiller01
Copy link
Contributor

Hi @stevieflow I think this logic is actually enforced through the logic in the validator that looks at the Codelists. If you check mapping.xml from the IATI-Codelists repo, you'll see that policy-marker significance codelist mapping does not have any condition elements associated with it: https://github.com/IATI/IATI-Codelists/blob/version-2.03/mapping.xml#L199-L202

As a result, that codelist will always be enforced.

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

No branches or pull requests

3 participants