sector
iati-activities/iati-activity/transaction/sector
This is the reference page for the XML element 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.
6.2.2: Each activity must have a specified sector, either at activity level OR for all transactions.
6.6.2: Sectors must only be declared at activity level OR for all transactions.
Attributes
- @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 SectorVocabulary codelist.
- @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.
- @code
The code for the sector.
This attribute is required.
This value must be of type xsd:string.
This value must be on the Sector codelist, if the relevant vocabulary is used.
This value must be on the SectorCategory codelist, if the relevant vocabulary is used.
This value must be on the UNSDG-Goals codelist, if the relevant vocabulary is used.
This value must be on the 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.
<sector vocabulary="2" code="111" />
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:
<sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
Full example:
<transaction ref="1234" humanitarian="1">
<transaction-type code="1" />
<transaction-date iso-date="2012-01-01" />
<value currency="EUR" value-date="2012-01-01">1000</value>
<description>
<narrative>Transaction description text</narrative>
</description>
<provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
<narrative>Agency B</narrative>
</provider-org>
<receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
<narrative>Agency A</narrative>
</receiver-org>
<disbursement-channel code="1" />
<sector vocabulary="2" code="111" />
<!--Note: only a recipient-region OR a recipient-country is expected-->
<recipient-country code="TM" />
<recipient-region code="616" vocabulary="1" />
<flow-type code="10" />
<finance-type code="110" />
<aid-type code="A01" vocabulary="1" />
<aid-type code="1" vocabulary="2" />
<tied-status code="3" />
</transaction>
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:
Subelements