sector ====== ``iati-activities/iati-activity/transaction/sector`` This is the reference page for the XML element ``sector``. .. index:: single: sector Definition ~~~~~~~~~~ A recognised code, from a recognised vocabulary, classifying the purpose of this transaction. If this element is used then ALL transaction elements should contain a transaction/sector element and iati-activity/sector should NOT be used. This element can be used multiple times, but only one sector can be reported per vocabulary. Rules ~~~~~ This element may occur any number of times. Either ``transaction/sector`` or ``sector`` must be present. Attributes ~~~~~~~~~~ .. _iati-activities/iati-activity/transaction/sector/.vocabulary: @vocabulary An IATI code for the vocabulary (codelist) used for sector classifications. If omitted, OECD DAC 5-digit Purpose Codes are assumed. It is recommended that OECD DAC 5-digit Purpose Codes are used wherever possible. It is also recommended that if a publisher has its own classification system or systems, then the vocabularies 99 or 98 (Reporting Organisation's own vocabularies) should be used in addition to the DAC codes. Note that at transaction level, only one sector per vocabulary can be reported. This value must be of type xsd:string. This value must be on the :doc:`SectorVocabulary codelist `. .. _iati-activities/iati-activity/transaction/sector/.vocabulary-uri: @vocabulary-uri 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. This value must be of type xsd:anyURI. .. _iati-activities/iati-activity/transaction/sector/.code: @code The code for the sector. This attribute is required. This value must be of type xsd:string. This value must be on the :doc:`Sector codelist `, if the relevant vocabulary is used. This value must be on the :doc:`SectorCategory codelist `, if the relevant vocabulary is used. This value must be on the :doc:`UNSDG-Goals codelist `, if the relevant vocabulary is used. This value must be on the :doc:`UNSDG-Targets codelist `, if the relevant vocabulary is used. Example Usage ~~~~~~~~~~~~~ Example ``sector`` of a ``transaction`` within an ``iati-activity``. | The ``@vocabulary`` attribute declares a valid code (*2*) from the *SectorVocabulary* codelist. | An example value *111* from this vocabulary is declared with the ``@code`` attribute. .. code-block:: xml | The ``sector`` element can be repeated in any ``transaction``. | The ``vocabulary`` is used to declare which ``SectorVocabulary`` classification list is in use. If this is omitted, then IATI assumes a *SectorVocabulary* of *1* (OECD DAC CRS Purpose Codes (5 digit)). | If a vocabulary is not on the *SectorVocabulary* codelist, then the value of *99* or *98* (Reporting Organisation) should be declared. | If a publisher uses a vocabulary of 98 or 99 (i.e. 'Reporting Organisation'), then the ``@vocabulary-uri`` attribute should also be used, for example: .. code-block:: xml Full example: .. literalinclude:: ../../../activity-standard-example-annotated.xml :language: xml :start-after: :end-before: Changelog ~~~~~~~~~ 2.03 ^^^^ The definition of the ``@vocabulary-uri`` was `updated `__. 2.02 ^^^^ The ``@vocabulary-uri`` attribute was `added `__. 2.01 ^^^^ The ``sector`` element was `added `__ as a child element of ``transaction``. Developer tools ~~~~~~~~~~~~~~~ Find the source of this documentation on github: * `Schema `_ * `Extra Documentation `_ Subelements ~~~~~~~~~~~ .. toctree:: :titlesonly: :maxdepth: 1 sector/narrative