International Aid Transparency Initiative: Activity-Information Schema
Release 1.03, 2012-09-06
NOTE: the xml.xsd and iati-common.xsd schemas must be in the
same directory as this one.
This W3C XML Schema defines an XML document type for information
about one or more aid-related activities, following the standard
published at http://iatistandard.org/
This document type may be extended with additional elements and
attributes, but they must belong to an explicit XML namespace.
Top-level list of one or more IATI activity records.
A number indicating the IATI specification version in use.
A date/time stamp for when this file was generated. This
is not necessarily the last-updated date for the
individual activity records in it. Uses ISO 8601 date
format, e.g. "2010-03-12T18:45:00+01:00". Use of this
attribute is highly recommended, to allow recipients to
know when a file has been updated.
IATI publishers are not obliged to publish their own
Linked Data. However, if a publisher chooses to publish
linked data about their IATI activities then allowing them
to declare where this data is published would support
discovery of it, and any additional information they may
choose to publish as Linked Data alongside it.
This attribute is URI path upon which an activity
identifier can be appended to get a dereferenceable URI
for any activity contained within a file.
Where a publisher declares using one of these properties
that authoritative linked data is accessible for an
activity then consuming applications that are generating
Linked Data from an IATI XML file should assert an
owl:sameAs relationship to the relevant URI.
Top-level element for a single IATI activity report.
A number indicating the IATI specification version in use.
Defaults to "1.0" if not specified. It is required to
specify this attribute if the document is using features
specific to an IATI specification other than the initial
1.0 version.
The last date/time that the data for this specific
activity was updated. This date must change whenever the
value of any field changes.
Default ISO 4217 currency code for all financial values in
this activity report. See
http://iatistandard.org/codelists/currency
The hierarchical level within the reporting organisation's
subdivision of its units of aid. (eg activity = 1;
sub-activity = 2; sub-sub-activity = 3). If hierarchy is
not reported then 1 is assumed. If multiple levels are
reported then, to avoid double counting, financial
transactions should only be reported at the lowest
hierarchical level.
A Linked Data URI for a given activity (overrides
iati-activities/@linked-data-default if set)
A link to a web site providing more information about the aid
activity. Multiple versions of the link may appear for
different languages.
An organisation (including the reporting organisation)
involved with the activity. May be a donor, fund, agency,
etc. Specifying the @identifier and @role attributes is
strongly recommended. May contain the organisation name as
content.
For the value of the @type attribute, see
http://iatistandard.org/codelists/organisation-type
For the value of the @ref attribute, see the list of
officially-registered organizations at
http://iatistandard.org/codelists/organisation
A code describing the organisation's role in the activity
(donor, agency, etc.).
See http://iatistandard.org/codelists/organisation_role
What geographical area does the activity encompass?
eg. Global, Regional, Multi-National, National, Multiple
(sub-national) administrative areas, etc
A partner country that will benefit from this activity. This
element is primarily for administrative and geopolitical
purposes. If a specific country is not known, the activity
report can use the recipient-region element instead. For
geographical location, use the location element.
For the value of the @code attribute, see
http://iatistandard.org/codelists/country
A geopolitical region (above the country level) that will
benefit from this activity. This element is primarily for
administrative and geopolitical purposes. If the specific
country/-ies are known, the activity report can use the
recipient-country element instead. For geographical location,
use the location element.
For the value of the @code attribute, see
http://iatistandard.org/codelists/region
The vocabulary from which the region code is drawn. If it
is not present 1 - 'OECD DAC' is assumed.
The type of collaboration involved in the project's
disbursements, e.g. "bilateral" or "multilateral".
For the value of the @code attribute, see
http://iatistandard.org/codelists/collaboration_type
The type of assistance provided, e.g. Official Development
Assistance (ODA). Type types will be defined by IATI.
For the value of the @code attribute, see
http://iatistandard.org/codelists/flow_type
The type of aid being supplied (budget support, debt relief,
etc.). This element specifies a default for all the
activity's financial transactions; it can be overridden at the
individual transaction level.
For the value of the @code attribute, see
http://iatistandard.org/codelists/aid_type
The type of finance (e.g. debt relief). The types will be
defined by IATI. This the default value for all transactions
in the activity report; it can be overridded by individual
transactions.
For the value of the @code attribute, see
http://iatistandard.org/codelists/finance_type
An alternative, non-IATI identifier for the activity. This
identifier is not guaranteed to be unique or persistent (it
depends on the owner organisation's policies, not IATI's).
If other-identifier is present then either @owner-ref or
@owner-name must be present
An identifier for the owner of this identifier, in URI
format.
See the list of officially-registered organizations at
http://iatistandard.org/codelists/organisation
Free text providing a human-readable name for the owner
of this identifier.
Sector code and name. For the value of the @code attribute,
see http://iatistandard.org/codelists/sector
Either the @code attribute or descriptive text content must be
present.
The code for the sector. If the vocabulary is "DAC" or
missing then the CRS Sector Code should be used.
Code is not mandatory but highly recommended. Either code
or description must be present.
The vocabulary (codelist) used for sector
classifications. If omitted, assume DAC. "DAC" codes
should be used wherever possible. It is also recommended
that if a publisher has its own classification system then
the vocabulary "RO" (Reporting Organisation's own
vocabulary" should be used in addition to "DAC". NB that
if multiple sector codes are used in multiple vocabularies
then each vocabulary's percentages should add up to 100%.
See http://iatistandard.org/codelists/vocabulary
The planned and actual start and completion dates of the
activity. Start dates may reflect either the commencement of
funding, planning or physical activity. End dates should,
wherever possible, reflect the ending of physical activity.
Dates should be in ISO 8601 date YYYY-MM-DD format, e.g.
2010-10-01.
For the value of the @type attribute, see
http://iatistandard.org/codelists/activity_date_type
The text content may contain a general date text (e.g. 2011Q1)
for recording less specific dates such as month, quarter, or
year.
An activity milestone date in ISO 8601 date format,
e.g. "2010-12-01".
The current status of the project (e.g. "planned"), using a
list defined by IATI. For the value of the @code attribute,
see http://iatistandard.org/codelists/activity_status
Contact information for the project. Specify whatever is
available. You may repeat this element for each contact
person.
The organisation to contact for more information about the
activity.
This is required if content-info is included.
The name of the contact person at the organisation.
If person-name is present then either person-name/text()
or job-title/text() must be present
The job title of the contact person at the organisation.
You may repeat this element for different languages.
If person-name is present then either person-name/text()
or job-title/text() must be present
The contact telephone number, if available. May be
repeated for multiple numbers.
The contact email address, if available. May be
repeated for multiple addresses.
The contact mailing address, if available.
The contact web address, if available. May be repeated
for multiple sites.
Specify whether the aid is untied, tied, or partially tied,
using a code list created by IATI. The content is free text
that can optionally provide more detail. For the value of the
@code attribute, see
http://iatistandard.org/codelists/tied_status
A policy or theme addressed by the activity. A text
description of the theme appears in the content, and a formal
identifier appears in the @ref attribute. The @vocabulary
attribute can also help to segment the markers into separate
vocabularies. This element can be repeated for each policy
marker. For the value of the @code attribute, see
http://iatistandard.org/codelists/policy_marker
Policy marker code. If vocabulary is missing or "DAC" use
the IATI Policy Marker Code list which is based on columns
20-23 and 28-31 of the CRS++ reporting format.
Policy vocabulary used. Default is "DAC", but "RO" may also
be used for publisher's own markers.
See http://iatistandard.org/codelists/vocabulary
The significance of the policy marker for this activity
(e.g. principal or significant), from a list defined by
IATI. If a marker is not significant, the policy-marker
element will not be present.
See http://iatistandard.org/codelists/policy_significance
The percentage of the total commitment that is for capital
spending
Committed or actual money flowing in or out of an aid
activity.The @ref attribute allows uniquely identifying a
transaction, to match it up with the corresponding in- or
outflow in a different activity.
The amount of the contribution (or its value, if in
kind).
A human-readable description of the transaction.
The type of the transaction (e.g. commitment,
disbursement, expenditure, etc.). The @ref attribute
contains a code defined by IATI, and the content is an
optional free-text description of the type.
For the value of the @code attribute, see
http://iatistandard.org/codelists/transaction_type
The organisation providing the money for the
transaction (if omitted, the provider organisation is
the reporting organisation).
For the value of the @ref attribute, see the list of
officially-registered organizations at
http://iatistandard.org/codelists/organisation
If the funds are being provided from the budget of
another activity that is reported to IATI, this
should record the unique IATI activity identifier for
that activity.
The organisation receiving the money from the
transaction (if omitted, then the receiver
organisation is the reporting organisation).
For the value of the @ref attribute, see the list of
officially-registered organizations at
http://iatistandard.org/codelists/organisation
If the funds are being provided to another activity
that is reported to IATI, this should record the
unique IATI activity identifier for that activity.
A milestone date for this transaction (such as the
decision date, disbursement date, etc.).
The ISO 8601 version of the transaction date.
Optional element to override the top-level
default-flow-type element.
For the value of the @code attribute, see
http://iatistandard.org/codelists/flow_type
Optional element to override the top-level
default-aid-type element (debt relief, etc.) on a
transaction-by-transaction basis if needed.
For the value of the @code attribute, see
http://iatistandard.org/codelists/aid_type
Optional element to override the top-level
default-finance-type element on a
transaction-by-transaction basis, if needed.
For the value of the @code attribute, see
http://iatistandard.org/codelists/finance_type
Optional element to override the top-level
default-tied-status element (pooled, etc.) on a
transaction-by-transaction basis if needed.
For the value of the @code attribute, see
http://iatistandard.org/codelists/tied_status
The channel through which the funds will flow for this
transaction, from an IATI code list.
A geographical location.
The type of location (e.g. "PCL" for a political
entity), from an IATI-defined subset of the UCPD/Aiddata
code list.
See http://iatistandard.org/codelists/location_type
The human-readable name for the location. May be
repeated in different languages.
A human-readable description of the location (not the activity).
Coded identification of national and sub-national
divisions according to recognised administrative
boundary repositories. Multiple levels may be reported.
The ISO 3166-1 alpha2 code for the country
(e.g. "GB" for the United Kingdom).
For the @code attribute, see
http://iatistandard.org/codelists/country
The UNSALB level-one administrative code for a
subdivision of a country.
See http://iatistandard.org/codelists/admin1
The UNSALB level-two administrative code for a
subdivision of a country.
See http://iatistandard.org/codelists/admin2
Geodetic coordinates for the location (latitude, longitude).
The decimal latitude (north is positive), e.g. "45.5"
for 45.5 degrees north (45 degrees 30 minutes).
The decimal longitude (east is positive), e.g. "-75.5"
for 75.5 degrees west (74 degrees 30 minutes).
An IATI-defined subset of UCPD precision codes for
the location (e.g. "2" for within 25 km of the
specified latitude/longitude).
See http://iatistandard.org/codelists/geographical_precision
Identifier for this location's entry in a geographical
gazetteer, such as GEOnet. The entry identifier is the
element content.
Reference to the gazetteer containing the entry.
See http://iatistandard.org/codelists/gazetteer_agency
Recipient country budget items.
This item encodes the alignment of activities with both the
functional and administrative classifications used in the
recipient country's Chart of Accounts. This applies to both
on- and off-budget activities.
Identifier for a single item in the recipient-country
budget. If more than one identifier is reported the
percentage share must be reported and all percentages
should add up to 100 percent.
A code for the common functional classification or country
system (This allows for common codes, country-specific, or
any other classification agreed between countries and
donors).
XX.XX Related Activity
Another IATI activity related to this one. The 'type'
attribute describes the type of relationship (e.g. parent,
sibling). This does not need to be used to express funding
relationships, since those are covered in individual
transactions.
For the value of the @type attribute, see
http://iatistandard.org/codelists/related_activity_type
Hold a single name=value pair of legacy data. This element is
*not* for adding new data types; instead, it holds the
original (non-IATI) value or code for an existing data type.
The original field name.
The original field value.
The name of the equivalent IATI element (if available).
A measurable result of aid work.
The indicator(s) that meet the results. There can be
multiple indicators for each result.
The baseline value for the indicator
The year the baseline value was taken
The baseline value.
The period covered for the results
reported. Multiple periods can be reported for a
single indicator.
The start of the reporting period
The end of the reporting period
The target milestone for this period
The target value.
A record of the achieved result for this period.
The actual measure.
The type of measurement for the indicator value
e.g. unit, percentage, NDP.
True if the indicator improves from small to large
(e.g. clinics built); false if it improves from
large to small (e.g. cases of a disease). Defaults
to true if omitted.
Boolean flag indicating whether the data in the result set
are suitable for aggregation.
Content type for a baseline or actual/planned outcome for an
indicator.
The year of the baseline or outcome.
The value of the baseline or outcome.
Conditions attached to the activity.
Description of one condition attached to the activity.
A yes/no (1/0) value stating whether there are conditions
attached to the activity.
The value of the aid activity's budget for each financial year
as in the original project document.
The starting date for the budget period, in ISO 8601
format (e.g. 2010-04-01 for 1 April 2010). This element
must be present.
The ending date for the budget period, in ISO 8601
format (e.g. 2011-03-31 for 31 March 2011). This
element must be present.
The total value of the organisation's aid budget for
this period. This element is required.
The starting date for the disbursement period, in ISO 8601
format (e.g. 2010-04-01 for 1 April 2010). This element
must be present.
The ending date for the disbursement period, in ISO 8601
format (e.g. 2011-03-31 for 31 March 2011). This
element must be present.
The amount to be disbursed in the specified currency.
The date on which this line of information was last
updated. Previous updates for the same period should also
be reported.
Additional items specific to CRS++ reporting.
Does this flag apply? If 'false' do not report the flag
Loan repayment terms and interest rates
Type of Repayment. 1 = equal principal payments
(EPP); 2 = annuity; 3 = lump sum; 5 = other,
Codes are listed at
http://iatistandard.org/codelists/crs-repayment-type
Number of repayments per annum. 1 = annual; 2 =
semi-annual; 4 = quarterly; 12 = monthly. Codes
are listed at
http://iatistandard.org/codelists/repayment-nopa.
Commitment date.The date must be in ISO 8601
format (YYYY-MM-DD).
First Repayment Date. The date must be in ISO
8601 format (YYYY-MM-DD).
Final Repayment Date. The date must be in ISO
8601 format (YYYY-MM-DD).
Interest Rate. If an ODA loan with variable
interest rate, report the variable rate here and
the reference fixed rate as rate-2
Enter the rate without the percentage sign.
Second Interest Rate. If an ODA loan with
variable interest rate, report the variable rate
as rate-1 and the reference fixed rate here
Enter the rate without the percentage sign.
The status of loan and interest repayments for the most
recently reported financial year
Interest received during the reporting year
The amount of principal owed on the loan at the
end of the reporting year.
Arrears of principal at the end of the
year. Included in principal-outstanding
Arrears of interest at the end of the year
CRS Reporting Year (CRS++ Column 1)
This section allows entry of data required for the OECD
DAC Forward Spending Survey at an activity level.
A container to hold separate forecasts for each of
the years specified
The calendar year that the forward spend covers
The exact date when the information was collected or
extracted from donors' aid management systems.
True if the partner country is a priority partner country.
If there are plans to phase out operations from the
partner country, this column shows the projected
year of last disbursements.