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

Guidelines - Duplication of Ruleset Contents #346

Closed
hayfield opened this issue May 10, 2017 · 1 comment
Closed

Guidelines - Duplication of Ruleset Contents #346

hayfield opened this issue May 10, 2017 · 1 comment

Comments

@hayfield
Copy link
Contributor

As part of the investigation under #334 - identifying must statements among Guidelines.

There are several Guidelines that are contained within the Standard Ruleset.

http://iatistandard.org/202/activity-standard/overview/iati-activity/
Every iati-activity must have a globally unique iati-identifier

http://iatistandard.org/202/activity-standard/overview/iati-identifier/
The iati-identifier must be unique for every iati-activity within the complete dataset published.

http://iatistandard.org/202/activity-standard/overview/classifications/
A sector is mandatory. - note that the details here are unclear (without investigation, it looks like they are optional in the Schema)

http://iatistandard.org/202/activity-standard/overview/budgets/
When declaring a value-date for any budget, this date must be in the past.

http://iatistandard.org/105/activity-standard/overview/transactions/
Neither of transaction-date and value-date can be in the “future”.

@amy-silcock
Copy link
Contributor

Must statements among guidelines are allowed as long as they match what's in the Standard. Sector is mandatory at activity or transaction level - not both.

The new overview pages better explain the rules and guidance for each element. In the move to the new website these will replace the current overview pages.

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

No branches or pull requests

2 participants