There will be situations where reporting organizations want to publish additional data that are not covered by the default IATI elements. This can be done by using an XML namespace to extend the schema.
This allows reporting organizations to invent any required markup and add it to an IATI activity report. IATI users who don’t recognize the extended markup are required simply to ignore it without reporting an error. Here is an example:
<iati-activity xmlns:acme=”http://example.org/acme/ns#” >
In this example, ACME has defined its own namespace using the URL “http://example.org/acme/ns#” and mapped that to the prefix “acme”. It then adds the new element, acme:risk-level, to provide information about its risk assessment for the activity. IATI users who don’t recognize the “http://example.org/acme/ns#” namespace are required to ignore the acme:risk element rather than reporting an error, so the extended markup does not harm compatibility. Users who are familiar with the namespace, however, can take advantage of the additional information.