You are viewing VERSION 2.02 of IATI Standard Reference View another version

sector

iati-activities/iati-activity/sector

This is the reference page for the XML element sector.

Definition

A recognised code, from a recognised vocabulary, classifying the purpose of the activity. Sector MUST EITHER be reported here OR at transaction level for ALL transactions

Rules

This element may occur any number of times.

2.1.1: When multiple sectors, within a vocabulary (e.g. 1 - OECD DAC) are declared, each must have a percentage.

2.1.4: When a single sector is declared, the percentage must either be omitted, or set to 100.

2.2.1: When using a reporting organisation sector code (vocabulary 98 or 99), it must include a narrative.

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.

6.7.2: If sector is declared at transaction level, a sector must be declared for all transactions.

102.1.1: When a non OECD DAC sector vocabulary is used, sector vocabulary 1 - OECD DAC should also be used.

Attributes

@vocabulary

An IATI code for the vocabulary (see 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 DAC codes.

Publishers using 98 or 99 must also include a narrative in the narrative element.

Note that if multiple sector codes are used in multiple vocabularies, then each vocabulary’s percentages should add up to 100%.

Sector can also be reported at the transaction level rather than the activity level. Sector must only be reported at EITHER transaction level OR activity level.

This value must be of type xsd:string.

This value must be on the SectorVocabulary codelist.

@vocabulary-uri

If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined.

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.

@percentage

The percentage of total commitments or total activity budget to this item. Content must be a positive decimal number between 0 and 100, with no percentage sign. All reported sectors from the same vocabulary MUST add up to 100%

This value must be of type xsd:decimal.

2.1.2: Percentage values for sectors, within a vocabulary (e.g. 1 - OECD DAC), must add up to 100%.

12.3.2: The sector percentage value must be 0.0 or positive.

Example Usage

Example sector of 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 iati-activity.

When multiple sector are declared, then the @percentage values should sum to 100% for the specific iati-activity.

  <sector vocabulary="2" code="111" percentage="50" />
  <sector vocabulary="2" code="112" percentage="50" />
  <sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" percentage="100">
   <narrative>A description of the sector</narrative>
  </sector>

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" />

Changelog

2.02

The vocabulary-uri attribute was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

1.03

Where used, the @percentage attribute is now designated as a decimal value and no longer as a positive Integer

Developer tools

Find the source of this documentation on github:

Subelements