IATI Consultations Archive

Live discussions and consultations can be found at discuss.iatistandard.org.

Add URI attribute to elements where 'Reporting organisation' vocabularies are used

This proposal relates to another proposal (accepted as part of the v2.02 upgrade of the standard) which will allow organisations to use their own internally defined geographic regions

The IATI standard has a number of attributes/elements where reporting organisation vocabularies can be used as a 'codelist', such as:

Region Vocabulary

  • iati-activities/iati-activity/recipient-region/@code (if iati-activities/iati-activity/recipient-region/@vocabulary = 99)
  • iati-activities/iati-activity/transaction/recipient-region/@code (if iati-activities/iati-activity/transaction/recipient-region/@vocabulary = 99)

Sector Vocabulary

  • iati-activities/iati-activity/sector/@code (if iati-activities/iati-activity/sector/@vocabulary = 98 or 99)
  • iati-activities/iati-activity/transaction/sector/@code (if iati-activities/iati-activity/transaction/sector/@vocabulary = 98 or 99)

This proposal suggests the addition of an optional attribute for publishers to record the URI where more information about the reporting organisation vocabulary can be found (if 'Reporting organisation' is set as the vocabulary)  For example:

  • iati-activities/iati-activity/recipient-region/@vocabulary-uri
  • iati-activities/iati-activity/transaction/recipient-region/@vocabulary-uri

  • iati-activities/iati-activity/sector/@vocabulary-uri

  • iati-activities/iati-activity/transaction/sector/@vocabulary-uri

Have more questions? Submit a request

3 Comments

  • 0
    Avatar
    IATI Tech Team

    Please see below for the technical implementation that is suggested in the Version 2.02 - Formal Proposal:

    New attribute: recipient-region/@vocabulary-uri

    • Add new attribute: vocabulary-uri

    • Example

      • Current usage
        <recipient-region code="A1" vocabulary="99" percentage="50" />

     

    • Add definition:
      ‘If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined'

     

    New attribute: transaction/recipient-region@vocabulary-uri

    • Add new attribute: vocabulary-uri

    • Example

      • Current usage
        <recipient-region code="A1" vocabulary="99" />

      • Proposed usage
        <recipient-region code="A1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" />

     

    • Add definition:
      ‘If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined’

     

    New attribute: sector/@vocabulary-uri

    • Add new attribute: vocabulary-uri

    • Example

      • Current usage
        <sector vocabulary="98" code="A1" percentage="50" />

      • Proposed usage
        <sector vocabulary="98" vocabulary-uri="http://example.com/vocab.html" code="A1" percentage="50" />

    • Add definition:
      ‘If the vocabulary is 98 or 99 (reporting organisation), the URI where this internal vocabulary is defined’

     

    New attribute: transaction/sector/@vocabulary-uri

    • Add new attribute: vocabulary-uri

    • Example

      • Current usage
        <sector vocabulary="99" code="A1" />

      • Proposed usage
        <sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />

    • Add definition:
      ‘If the vocabulary is 98 or 99 (reporting organisation), the URI where this internal vocabulary is defined'

     

    New attribute: policy-marker/@vocabulary-uri

    • Add new attribute: vocabulary-uri

    • Example

      • Current usage
        <policy-marker vocabulary="1" code="2" significance="3" />

      • Proposed usage
        <policy-marker vocabulary="1" vocabulary-uri="http://example.com/vocab.html"  code="2" significance="3" />

    • Add definition:
      ‘If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined’

  • 0
    Avatar
    IATI Tech Team

    This proposal has been added as a GitHub issue, for inclusion in the version 2.02 development branch of the IATI-Schemas: https://github.com/IATI/IATI-Schemas/issues/279

  • 0
    Avatar
    IATI Tech Team

    This proposal has now been incorporated into a version 2.02 code repositories (see the above GitHub issue link for technical details). The relevant pages on a development version of the 2.02 reference and documentation site is available to view here:

    We welcome scrutiny on the implementation of this proposal and encourage the community to feedback and suggest solutions for any errors, omissions and problems. This should be done before Monday 7 December, when the process will commence to release version 2.02 as a live version of the IATI Standard. More information on the inspection phase is available here.

Please sign in to leave a comment.