International Aid Transparency Initiative: Activity-Information Schema
Release 2.02, 2015-12-07
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.
This is mandatory and must be a valid version.
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. Use of this attribute
is highly recommended, to allow recipients to know when a
file has been updated.
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 a URI path upon which an activity
identifier can be appended to get a differentiable 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 short, human-readable title that contains a meaningful
summary of the activity. May be repeated for different
languages.
A longer, human-readable description containing a
meaningful description of the activity. May be repeated
for different languages.
The type of description being provided. This is not
required if only one general description of the activity
is reported.
The last date/time that the data for this specific
activity was updated. This date must change whenever the
value of any field changes.
ISO 639-1 code specifying the default language used in
narrative elements throughout the activity. If this is not
declared then the xml:lang attribute MUST be specified for
each narrative element.
Default ISO 4217 alphabetic currency code for all
financial values in this activity report. If this is not
declared then the currency attribute MUST be specified for
all monetary values.
A process flag to indicate that this activity relates entirely
or partially to humanitarian aid.
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 globally unique identifier for the activity.
This MUST be prefixed with EITHER the current IATI
organisation identifier for the reporting organisation
(reporting-org/\@ref) OR a previous identifier reported in
other-identifier, and suffixed with the organisation’s own
activity identifier. The prefix and the suffix should be
separated by a hyphen "-".
Once an activity has been reported to IATI its identifier MUST
NOT be changed in subsequent updates.
An organisation involved with the activity. May be a donor,
fund, agency, etc. Specifying the @ref identifier is strongly
recommended. May contain the organisation name as narrative.
If the reporting organisation plays a role in the activity it
should be repeated here. One organisation may play more than
one role (eg, funding and implementing): in such a case each
role should be reported and the name of the organisation
repeated.
Machine-readable identification string for the
organisation. Must be in the format {Registration Agency}
- (Registration Number} where {Registration Agency} is a
valid code in the Registration Agency code list and
{Registration Number } is a valid identifier issued by the
{Registration Agency}. If this is not present then the
narrative MUST contain the name of the organisation.
The type of organisation issuing the report. See IATI
codelist for values.
An IATI code describing the organisation's role in the
activity (donor, agency, etc.).
A valid activity identifier published by the participating
organisation which points to the activity that it has
published to IATI that describes its role in this activity.
The geographical scope of the activity: regional, national,
sub-national, etc.
The geographical scope. See IATI codelist for values.
A country that will benefit from this activity. If a specific
country is not known the recipient-region element should be
used instead. For geographical location, use the location
element.
Multiple countries and regions can be reported, in which case
the percentage attribute MUST be used to specify the share of
total commitments across all reported countries and regions.
The country can also be specified at transaction rather than
activity level. If recipient-country OR recipient-region are
reported at the transaction level, ALL transactions MUST
contain a recipient-country or recipient-region element and
iati-activity/recipient-country
and iati-activity/recipient-region MUST NOT be used.
ISO 3166-1 alpha-2 code for the country.
The percentage of total commitments or total activity
budget allocated to this country. Content must be a
positive decimal number between 0 and 100, with no
percentage sign. Percentages for all reported countries
and regions MUST add up to 100%
A supranational geopolitical region that will benefit from
this activity. For sub-national geographical location, use the
location element.
Multiple countries and regions can be reported, in which case
the percentage attribute MUST be used to specify the share of
total commitments across all reported countries and regions.
Recipient-region must not be used merely to describe the
region of a country reported in recipient-country, but ONLY if
the region is a recipient IN ADDITION to the country.
Region can also be reported at transaction rather than
activity level. If transaction/recipient-country AND/OR
transaction/recipient-region are used THEN ALL transaction
elements MUST contain a recipient-country and/or
recipient-region element AND iati-activity/recipient-region
and iati-activity/recipient-region MUST NOT be used AND each
transaction MUST only contain one recipient-country or
recipient-region.
Either an OECD DAC or UN region code. Codelist is
determined by vocabulary attribute.
An IATI code for the vocabulary from which the region code
is drawn. If it is not present 1 - 'OECD DAC' is assumed.
If the vocabulary is 99 (reporting organisation), the URI
where this internal vocabulary is defined.
The percentage of total commitments or total activity
budget allocated to this region. Content must be a
positive decimal number between 0 and 100, with no
percentage sign. Percentages for all reported countries
and regions MUST add up to 100%
The type of collaboration involved in the activity's
disbursements, e.g. "bilateral" or "multilateral".
A code from the OECD DAC CRS "Bi_Multi" codelist.
Whether the activity is funded by Official Development
Assistance (ODA), Other Official Flows (OOF), etc
A code from the OECD DAC CRS "Type of flow" codelist
The type of aid being supplied (project-type intervention,
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.
A code from the OECD DAC CRS "Type of aid" codelist
The type of finance (e.g. grant, loan, debt relief, etc). This
the default value for all transactions in the activity report;
it can be overridden by individual transactions.
A code from the OECD DAC CRS "Type of finance" codelist
An other identifier for the activity. This may be a publishers
own identifier that it wishes to record with the activity.
This element is also used to trace changes to activity
identifiers, for example when and organisation has changed
it's organisation identifier.
Where applicable, the organisation that owns the other
identifier being reported. When used, then either
other-identifier/owner-org/\@ref or
other-identifier/owner-org/narrative/text() MUST be
present.
An organisation identifier. This is NOT MANDATORY
but when used MUST contain a valid organisation
identifier.
The identifier you wish to report.
This can be used to report a number of different types
of identifiers. See the OtherIdentifierType codelist
for details and options.
The type of identifier being reported, taken from
the OtherIdentifierType codelist.
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
The description of a sector defined by the reporting
organisation. (Only to be used when the reporting
organisation's own vocabulary is being used).
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.
If the vocabulary is 99 or 98 (reporting organisation), the URI
where this internal vocabulary is defined.
The code for the sector.
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%
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.
The narrative content may contain text (e.g. 2011Q1) for
accurately recording less specific dates such as month,
quarter, or year.
An IATI code defining the type of activity date being reported.
The current status of the activity. See codelist for values.
An IATI code defining the current status of the activity.
Contact information for the activity. Specify whatever is
available. You may repeat this element for each contact
person.
The name of the organisation to contact for more
information about the activity.
The department within the organisation to contact for more
information about the activity.
The name of the contact person for the activity.
The job title of the contact person at the organisation.
The contact telephone number. May be repeated for
multiple numbers.
The contact email address. May be repeated for multiple
addresses.
The contact web address. May be repeated for multiple sites.
The contact mailing address.
The type of contact. See IATI codelist for values.
Whether the aid is untied, tied, or partially tied. This
element specifies a default for all the activity's financial
transactions; it can be overridden at the individual
transaction level.
If an activity is partially tied it is recommended that tied
and untied commitments are reported as separate transactions
and that transaction/tied-status is used to classify them.
An IATI code interpreting the usage of Columns 36-38 of the
CRS++ reporting format. (Amount tied, Amount partially
untied, Amount tied)
Classification of emergencies, appeals and other humanitarian
events and actions.
The description of the code specified.
A code for the type of event or action being classified.
A code for a recognised vocabulary of terms classifying the
event or action.
A u.r.i. for the vocabulary specified which provides access to
the list of codes and descriptions.
A code for the event or action from the vocabulary specified.
A policy or theme addressed by the activity. This element was
designed for the reporting of OECD DAC CRS policy markers
(columns 20-23 and 28-31 of the CRS++ reporting format) but
the vocabulary attribute allows it use by other (including
local) systems. This element can be repeated for each policy
marker.
A description of the policy marker. This MUST ONLY be
used if vocabulary is 99 (the reporting
organisation's own marker vocabulary). May be repeated
for multiple languages.
An IATI code for the vocabulary to be used to define
policy markers. If omitted then the OECD DAC vocabulary is
assumed.
If the vocabulary is 99 (reporting organisation), the URI
where this internal vocabulary is defined.
A policy marker code from the codelist specified in the
vocabulary.
An OECD DAC CRS code indicating the significance of the policy marker
for this activity. This attribute MUST be used for all OECD DAC CRS
vocabularies.
The percentage of the total commitment that is for capital
spending
The percentage of the total commitment allocated to or
planned for capital expenditure. Content must be a
positive decimal number between 0 and 100, with no
percentage sign.
Transactions recording committed or actual funds flowing in or
out of an aid activity.
The type of the transaction (e.g. commitment,
disbursement, expenditure, etc.).
An IATI code defining the type of the transaction
(e.g. commitment, disbursement, expenditure, etc.).
The date on which the transaction was made or (in the
case of commitments) agreed. The narrative content may
contain text (e.g. 2011Q1) for accurately recording less
specific dates such as month, quarter, or year.
The amount of the contribution.
A human-readable description of the transaction.
For incoming funds this is the organisation from which
the transaction originated. If omitted on outgoing funds
the reporting-org is assumed.
The name of the organisation. This can be repeated
in multiple languages
Machine-readable identification string for the
organisation. Must be in the format {Registration
Agency} - (Registration Number} where {Registration
Agency} is a valid code in the Registration Agency
code list and {Registration Number } is a valid
identifier issued by the {Registration Agency}. If
this is not present then the narrative MUST contain
the name of the organisation.
If incoming funds are being provided from the budget
of another activity that is reported to IATI, it if
STRONGLY RECOMMENDED that this should record the
provider's unique IATI activity identifier for that
activity.
The type of organisation providing the funds.
The organisation receiving the money from the
transaction (if omitted on incoming funds then the
receiver organisation is assumed to be the reporting
organisation).
The name of the organisation. This can be repeated
in multiple languages
Machine-readable identification string for the
organisation. Must be in the format {Registration
Agency} - (Registration Number} where {Registration
Agency} is a valid code in the Registration Agency
code list and {Registration Number } is a valid
identifier issued by the {Registration Agency}. If
this is not present then the narrative MUST contain
the name of the organisation.
If outgoing funds are being provided to another
activity that is reported to IATI, this may, if
possible, record the unique IATI activity identifier
for that activity.
The type of organisation receiving the funds.
The channel through which the funds will flow for this
transaction, from an IATI codelist.
An IATI code defining channels of disbursement
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.
The free text description of the reporting
organisation's own sector definition. This can be
repeated in multiple languages
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.
If the vocabulary is 99 or 98 (reporting organisation), the URI
where this internal vocabulary is defined.
The code for the sector.
A country that will benefit from this transaction.
If a specific country is not known the recipient-region
element should be used instead.
If transaction/recipient-country AND/OR
transaction/recipient-region are used THEN ALL
transaction elements MUST contain a recipient-country
or recipient-region element AND
(iati-activity/recipient-country AND
iati-activity/recipient-region MUST NOT be used)
ISO 3166-1 alpha-2 code for the country.
A supranational geopolitical region that will benefit
from this transaction. If a specific country is not
known, then this element MUST be used.
If transaction/recipient-country AND/OR
transaction/recipient-region are used THEN ALL
transaction elements MUST contain a recipient-country
or recipient-region element AND
(iati-activity/recipient-country AND
iati-activity/recipient-region MUST NOT be used)
Either an OECD DAC or UN region code. Codelist is
determined by vocabulary attribute.
An IATI code for the vocabulary from which the region code
is drawn. If it is not present 1 - 'OECD DAC' is assumed.
If the vocabulary is 99 (reporting organisation), the URI
where this internal vocabulary is defined.
Optional element to override the top-level
default-flow-type element.
A code from the OECD DAC CRS "Type of flow" codelist
Optional element to override the top-level
default-finance-type element on a
transaction-by-transaction basis, if needed.
A code from the OECD DAC CRS "Type of finance" codelist
Optional element to override the top-level
default-aid-type element (debt relief, etc.) on a
transaction-by-transaction basis if needed.
A code from the OECD DAC CRS "Type of aid" codelist
Optional element to override the top-level
default-tied-status element on a
transaction-by-transaction basis if needed.
An IATI code interpreting the usage of Columns 36-38
of the CRS++ reporting format. (Amount tied, Amount
partially untied, Amount tied)
An internal reference linking this transaction back to the
publisher's financial management system.
A process flag to indicate that this transaction relates
entirely or partially to humanitarian aid. If the entire
activity relates to humanitarian aid this should be reported
using iati-activity/\@humanitarian, rather than for each
transaction.
The sub-national geographical identification of the target
locations of an activity. These can be described by gazetteer
reference, coordinates, administrative areas or a textual
description. Any number of locations may be reported.
Does this location describe where the activity takes
place or where the intended beneficiaries reside?
An IATI code for the geographic scope of the activity.
A unique code describing the location according to a
recognised gazetteer or administrative boundary
repository. Administrative areas should only be reported
here if the location being defined is the administrative
area itself. For describing the administrative area/s
within which a more specific location falls the
location/administrative element should be used.
A code from the gazetteer or administrative boundary
repository specified by the vocabulary
An IATI code for a recognised gazetteer or
administrative boundary repository.
The human-readable name for the location.
A description that qualifies the location, not the
activity.
A description that qualifies the activity taking place at
the location. This should not duplicate information
provided in the main activity description, and should
typically be used to distinguish between activities at
multiple locations within a single iati-activity record.
Coded identification of national and sub-national
divisions according to recognised administrative
boundary repositories. Multiple levels may be reported.
The code for the administrative area being reported
from the vocabulary specified.
An IATI code for a recognised administrative
boundary repository.
A number defining a subdivision within a hierarchical
system of administrative areas. The precise system
for defining the particular meaning of each @level
value is determined by the @vocabulary being used.
The point element is based on a subset of the GML 3.3 Point
element.
The latitude and longitude coordinates in the
format "lat lng"
The name of the spatial reference system used by the
coordinates.
Always: http://www.opengis.net/def/crs/EPSG/0/4326
Defines whether the location represents the most
distinct point reasonably possible for this type of
activity or is an approximation due to lack of more
detailed information.
A code from the Geographic Exactness Codelist.
Whether the location refers to a structure, a populated
place (e.g. city or village), an administrative
division, or another topological feature
(e.g. river, nature reserve).
A code from the Location Class codelist
A more refined coded classification of the type of
feature referred to by this location.
A feature designation code form the authorised list
(maintained by the US National
Geospatial-Intelligence Agency)
An internal reference that describes the location in the
reporting organisation's own system.
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 longer, human-readable description of the
budget-item. May be repeated for different
languages.
A code for the budget-item from the vocabulary
specified.
When multiple budget-item elements are declared
within a single country-budget-items element, then,
for each vocabulary used, the percentage values
should sum 100%.
An IATI 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).
Another separately reported IATI activity that is related to
this one. The 'type' attribute describes the type of
relationship: eg. parent, child, multifunded ...
A valid activity identifier (as defined in
iati-activity/iati-identifier).
An IATI code for the type of relationship
The legacy data element allows for the reporting of values
held in a field in the reporting organisation's system which
is similar, but not identical to an IATI element.
The original field name in the reporting organisation's
system
The original field value in the reporting organisation's
system
The name of the equivalent IATI element.
A container for reporting outputs, outcomes, impacts and other
results that stem directly from the activity. This may be
repeated for each type of result reported.
The indicator(s) that meet the results. There can be
multiple indicators for each result.
A standardised means of identifying the indicator from a
code in a recognised vocabulary. Multiple vocabularies may
be specified, but each vocabulary may be specified only
once for each indicator.
A code for a recognised vocabulary of indicators. The
value for this field should appear in the
IndicatorVocabulary codelist.
A code for an indicator defined in the specified
vocabulary specified.
If the vocabulary is 99 (reporting organisation), the
URI where this internal vocabulary is defined.
The baseline value for the indicator
The year the baseline value was taken (yyyy)
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
A location already defined and described in the
iati-activity/location element.
A cross-reference to the internal reference assigned
to a defined location: iati-activity/location/\@ref.
A category used for disaggregating the result by gender,
age, etc.
Freetext description of a category being disaggregated.
Description of the value being disaggregated.
The target value.
A record of the achieved result for this period.
A location already defined and described in the
iati-activity/location element.
A cross-reference to the internal reference assigned
to a defined location: iati-activity/location/\@ref.
A category used for disaggregating the result by gender,
age, etc.
Freetext description of a category being disaggregated.
Description of the value being disaggregated.
The actual measure.
An IATI code defining the unit of measure in which
the value is reported.
A boolean describing the behaviour of the indicator.
It is "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).
An IATI code for the type of result being reported.
Boolean flag indicating whether the data in the result set
are suitable for aggregation.
Specific terms and conditions attached to the activity that,
if not met, may influence the delivery of commitments made by
participating organisations.
The text of a specific condition attached to the
activity. Organisation-wide terms and conditions that
apply to all activities should not be reported here, but
in either iati-organisation/document-link or
iati-activity-document-link
An IATI code defining the type of condition.
A yes/no (1/0) value stating whether there are conditions
attached to the activity. It is strongly recommended that
this attribute is reported, even if there are no conditions
attached (i.e. attached="0")
The value of the activity's budget for each financial quarter or year over the lifetime of the activity. The purpose of this element is to provide predictability for recipient planning on an annual basis. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative. The sum of budgets may or may not match the sum of commitments, depending on a publisher’s business model and legal frameworks.
The start of the budget period.
The end of the period (which must not be greater than
one year)
The budget for this period.
Whether this is the original budget (prepared when the
original commitment was made) or has subsequently been
revised
The status explains whether the budget being reported is indicative or has
been formally committed. The value should appear within the BudgetStatus
codelist. If the @status attribute is not present, the budget is assumed
to be indicative.
The planned disbursement element should only be used to report
specific planned cash transfers. These should be reported for
a specific date or a meaningfully predictable period. These
transactions should be reported in addition to budgets - which
are typically annual breakdowns of the total activity
commitment.
The exact date of the planned disbursement OR the starting date
of the period in which this specific disbursement will be made.
The ending date for the period in which this specific disbursement
will be made.
The amount that is planned to be disbursed in the specified currency.
The organisation from which the planned disbursement will originate.
If omitted the reporting-org is assumed.
The name of the organisation. This can be repeated
in multiple languages
Machine-readable identification string for the
organisation. Must be in the format {Registration
Agency} - (Registration Number} where {Registration
Agency} is a valid code in the Registration Agency
code list and {Registration Number } is a valid
identifier issued by the {Registration Agency}. If
this is not present then the narrative MUST contain
the name of the organisation.
The identifier for the activity in which the planned
disbursement will be reported. If omitted the current
activity is assumed.
The type of organisation providing the funds.
The organisation receiving the money from the planned
disbursement.
The name of the organisation. This can be repeated
in multiple languages
Machine-readable identification string for the
organisation. Must be in the format {Registration
Agency} - (Registration Number} where {Registration
Agency} is a valid code in the Registration Agency
code list and {Registration Number } is a valid
identifier issued by the {Registration Agency}. If
this is not present then the narrative MUST contain
the name of the organisation.
If outgoing funds are being provided to another
activity that is reported to IATI, this may, if
possible, record the unique IATI activity identifier
for that activity.
The type of organisation receiving the funds.
Whether this is an original plan (prepared when the
original commitment was made) or has subsequently been
revised.
Additional items specific to CRS++ reporting.
This covers the four CRS++ columns titled:
"Free standing technical cooperation";
"Programme-based approach";
"Investment project";
"Associated financing"
An IATI code describing the equivalent CRS++ columns
A boolean indicating whether the flag applies. If 'false' do not report the flag
Loan repayment terms and interest rates
The type of loan repayment
An IATI codelist tabulating CRS-specified
values for the type of Repayment.
Number of repayments per annum.
An IATI codelist tabulating CRS-specified
values for the number of repayments per annum.
The CRS++ reported commitment date
First Repayment Date.
Final Repayment Date.
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)
The CRS channel code for this activity. This should only
be used for reporting to CRS. The code list contains
both organisation types and names of organisations. For
non-CRS purposes these should be reported using the
participating-org element.
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 Text() holds the forecast value for each
year.
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.
A link to an online, publicly accessible web page or
document.
IATI Document Category Code
An IATI code defining the category of the document.
The ISO 639-1 language code in which target document is
written, e.g. "en". Can be repeated to describe
multi-lingual documents.
ISO 639-1 language code
The date of publication of the document that is being linked to.
The target URL of the external document, e.g. "http://www.example.org/doc.odt".
An IANA code for the MIME type of the document being
referenced, e.g. "application/pdf".
Data type for an element containing a currency value.
The ISO 4217 alphabetic currency code of the value reported.
This is required unless the iati-activity/\@default-currency is
present and applies.