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

Add new reference element (as a child of the result element) #362

Closed
6 tasks done
dalepotter opened this issue Oct 31, 2017 · 0 comments
Closed
6 tasks done

Add new reference element (as a child of the result element) #362

dalepotter opened this issue Oct 31, 2017 · 0 comments
Assignees
Milestone

Comments

@dalepotter
Copy link
Contributor

dalepotter commented Oct 31, 2017

Add a new element iati-activities/iati-activity/result/reference with definition:

A reference element to allow for the coded identification of a results framework.

The element will have an occurrence rule of 0..*.

This will also add the following sub-attributes/elements with definitions:

  • iati-activities/iati-activity/result/reference/@code - occurs 1..1, type xsd:string

A code from the codelist identified in vocabulary that identifies a results framework

  • iati-activities/iati-activity/result/reference/@vocabulary - occurs 1..1

A code for the results framework vocabulary. The code must be a valid value in the ResultVocabulary codelist

  • iati-activities/iati-activity/result/reference/@vocabulary-uri - occurs 0..1, type xsd:anyURI

The URI where this vocabulary is defined. If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

Tasks:

The addition of the new ResultVocabulary codelist has been added as a new issue on the IATI-Codelists-NonEmbedded repository.

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

3 participants