Paper 5 Technical Paper FINAL

Document Sample
Paper 5 Technical Paper FINAL Powered By Docstoc
					               PAPER 5: Technical Paper
A. Format and Definitions of IATI Standard for remaining data

                   B. IATI Licensing Standard
     Meeting of IATI Signatories and Steering Committee Members

                    OECD, Paris, 9 February 2011
                                     A Format and Definitions of IATI Standard for remaining data
                                  (Changes to the version used in the consultation shown in track changes)

Introduction
The detailed codes lists to be used are available at the online forum (www.iaticonsultation.org). The technical formats for publishing are unchanged from those
included in each of the consultation papers; some definitions have been updated in the light of the comments received. Once approved, the formats will be added to
the repository of the official standard (http://iatistandard.org), available in English, French and Spanish. The standard will be kept up-to-date in the light of
implementation experience.

Documents
Section         Item        Definition                    Data Format XML                               Occurs Examples and Notes

Document Link               Information pertaining to a                 country-budget                  0..*
                            published document that is
                            related to an organisation
                            or an activity

                url         The web address where the u.r.l.            document-link/@url              1..1   <document-link
                            document can be                                                                    url="http://reporting.org/activities/documents/xx546.doc"/>
                            downloaded.

                document    The Internet Media Type       File Format   document-link/@format           1..1   <document-link format="application/msword">
                format      ("MIME type") of the          Code
                            document linked to, as
                            defined and maintained by
                            the Internet Assigned
                            Numbers Authority.
Section   Item           Definition                    Data Format XML                            Occurs Examples and Notes

          language       The ISO 639 code for the      Language   document-link/@xml:lang         0..1     <document-link xml:lang="en">
                         language of the document.     Code
                         Only required if different
                         from the activity’s default
                         language.

          category       The type of content       document- document-link/category               1 0..*
                         contained within the      link/category
                         document. If the document
                         spans multiple content
                         types this element should
                         be repeated.

          category-code The code for the content       Document   document-link/category/@code    1..1     <category code="A04"/>
                        type                           Category
                                                       Code

          category-      A description of the content Text        document-link/category/text()   0..1     <category code="A04">Conditions</category>
          description    type

          title          The full title of the         Text       document-link/title/text()      1..1     <title>Project Conditions</title>
                         document
Results and Conditions
Section   Item          Definition                   Data        XML                                 Occurs Examples and Notes
                                                     Format

Results                                                          Results                             0..1   <results>

          Result        a text description of the     Text       results/result/text()               1..*   <results>
                        result the activity is aiming
                        to achieve e.g. build 10                                                            <result result-type=”output”>build 10 schools
                        schools
                                                                                                            </result>

                                                                                                            </results>
          Result-type   whether it is an output,     Code list   results/result/@result-type         1.1
                        outcome, or impact
                        indicator

          Indicator     The indicator(s) that meet Text          results/result/indicator/           0.*    <results>
                        the results. There can be
                        multiple indicators for each                                                        <result result-type=”output”>build 10 schools
                        ‘result’
                                                                                                            <indicator measure=”unit”>

                                                                                                            <indicator-description>number of schools built</indicator-
                                                                                                            description>

                                                                                                            </indicator>

                                                                                                            </result>

                                                                                                            </results>
          Measure       The type of measurement Code list        results/result/indicator/@measure   0.*
                        for the indicator value e.g.
                        unit, percentage
Section   Item          Definition                  Data     XML                                             Occurs Examples and Notes
                                                    Format

          Indicator     The description of the      Text     results/result/indicator/text()
          description   indicator

          Baseline      The value of the baseline   Text     results/result/indicator/baseline/numbertext() 0.1    <indicator measure=”percentage”>
                        measure A comment on
                        the baseline measure                                                                       <indicator-description>gross primary school enrolment
                                                                                                                   rate</indicator-description>

                                                                                                                   <baseline year=”2008” value=”55%”>Baseline
                                                                                                                   comment</baseline>

                                                                                                                   <target year=”2015” value=”85%”>Target
                                                                                                                   Comment</target>

                                                                                                                   <actual year=”2010” value=”62%”>Actual
                                                                                                                   Comment</actual>

                                                                                                                   </indicator>
          Year          The Year the baseline       YYYY     results/result/indicator/baseline/@year         0.1
                        measure was taken

          Value         The baseline measure.       Text     results/result/indicator/baseline/@value        0.1

          Target        The target valuecomment Text         results/result/indicator/target/numbertext ()   0.*
                        for the indicator. There can
                        be many targets set as
                        milestone measures

          Target-date   The year the result is      YYYY     results/result/indicator/target/@year           0.*
                        aiming to be realised

          Value         The target value            Text     results/result/indicator/target/@value          0.*
Section      Item          Definition                  Data        XML                                             Occurs Examples and Notes
                                                       Format

             Actual        A record of the achieved    Text        results/result/indicator/actual/numbertext ()   0.*
                           result, or an interim
                           measure to track progress

             Actual-date   The year the actual         YYYY        results/result/indicator/actual/@year           0.*
                           measure was taken

             Value         The actual measure.         Text        results/result/indicator/actual/@value          0.*

Conditions                                                         conditions                                      0..1

             attached      A yes/no value stating     Yes/No       conditions/@attached                            1..1   <conditions attached=”no” />
                           whether there are
                           conditions attached to the
                           activity

             condition     Multiple conditions                     conditions/condition                            1..*
                           allowed

             type          Condition type – e.g.       Condition   conditions/condition/@type                             <condition type=”policy” />
                           policy, performance.        Type Code

             description   The text describing the    Text         conditions/condition/text()                            <condition type=”policy”>
                           conditions attached to the
                           activity                                                                                       text of conditions to go here</condition>
Activity Budget and Planned Disbursements
Section   Item           Definition                      Data Format XML                       Occurs Examples and Notes

Budget    budget         The value of the aid                       budget                     0..*   This is wanted as a minimum most useful by the financial
                         activity's budget for each                                                   year of the recipient country.
                         financial year of the                                                        (If that is not available, Ccan optionally also be provided for
                         recipient as in the original                                                 each calendar year and/or financial year of the donor.)
                         project document.
          type           Is budget original or revised Budget Type budget/@type                1..1   <budget type=”original”>
                                                       Code

          period-start   ISO 8601 code for the start Date           budget/period-start        1..1   <period-start>2011-01-01</period-start>
                         date of the reporting period
                         (yyyy-mm-dd).

          period-end     ISO 8601 code for the end Date             budget/period-end          1..1   <period-end>2011-12-31</period-end>
                         date of the reporting period
                         (yyyy-mm-dd).

          value          The total budget for the      Integer      budget/value/text()        1..1   <value value-date="2010-10-01">700000</value>
                         specified period in the
                         specified currency. (Positive
                         integer.)

          value-date     Date of value for currency      Date       budget/value/@value-date   1..1   <value value-date="2010-10-01">700000</value>
                         conversions.(yyyy-mm-dd)

          currency       The ISO 4217 code for the       Currency   budget/value/@currency     0..1   <value currency="GBP" value-date="2010-10-
                         currency in which the           Code                                         01">700000</value>
                         project is denominated.
                         [only if different to default
                         currency]
Section        Item           Definition                    Data Format XML                                   Occurs Examples and Notes

Planned        planned-       The amount it is planned to              planned-disbursement                   0..*   This is wanted as a minimummost useful by the financial
Disbursement   disbursement   disburse on the activity in                                                            year of the recipient country.
                              each of the next three                                                                 (If that is not available, Ccan optionally also be provided for
                              financial years of the                                                                 each calendar year and/or financial year of the donor.)
                              recipient.

               date-updated   The date on which this line Date         planned-disbursement/@updated                 <planned-disbursement updated=”2010-12-01”>
                              of information was last
                              updated. Previous updates
                              for the same period should
                              also be reported.

               period-start   ISO 8601 code for the start Date         planned-disbursement/period-start      1..1   <period-start>2011-01-01</period-start>
                              date of the reporting period
                              (yyyy-mm-dd).

               period-end     ISO 8601 code for the end Date           planned-disbursement/period-end        1..1   <period-end>2011-12-31</period-end>
                              date of the reporting period
                              (yyyy-mm-dd).

               value          The amount to be disbursed Integer       planned-disbursement/value/text()      1..1   <value value-date="2010-11-01">7000</value>
                              in the specified currency.
                              (Positive integer.)

               value-date     Date of value for currency    Date       planned-disbursement/value/@value-date 1..1   <value value-date="2010-11-01">7000</value>
                              conversions.(yyyy-mm-dd)

               currency       The ISO 4217 code for the     Currency   planned-disbursement/value/@currency   0..1   <value currency="GBP" value-date="2010-11-
                              currency of the               Code                                                     01">7000</value>
                              disbursement. [only if
                              different to default
                              currency
Recipient Country Budget Identifier
Section      Item           Definition                  Data Format XML                                        Occurs Examples and Notes

Recipient                                                            country-budget                            0..*
Country
Budget
Identifier

             vocabulary     Vocabulary: name of          Text        country-budget/@vocabulary                1..1   <country-budget vocabulary=”RW-BUDGET”>
                            country or global functional
                            classification system (This
                            allows for country-specific,
                            common codes, or any
                            other classification agreed
                            between countries and
                            donors)

             accountable-   The budget classification                country-budget/ accountable-institution   1..*
             institution    and percentage breakdown
                            for the named accountable
                            institution

             institution-   The unique organisation     Organisation country-budget/ accountable-              0..1   <accountable-institution ref=”RW-1001”/>
             identifier     identifier for the          Identifier   institution/@ref
                            accountable institution.

             institution-   The name of the             Text         country-budget/ accountable-              0..1   <accountable-institution ref=”RW-1001”>Rwandan Ministry
             name           accountable institution.                 institution/text()                               of Health</accountable-institution>
Section   Item           Definition                  Data Format XML                                           Occurs Examples and Notes

          institution-   The percentage of the total Percent      country-budget/ accountable-institution             <accountable-institution ref=”RW-1001”
          share          commitment that is                       /@percent                                           percent=”100”>Rwandan Ministry of Health</accountable-
                         allocated to this institution                                                                institution>
                         (Allows for cases where
                         there is more than one
                         accountable institution;
                         must add up to 100% for all
                         the accountable institutions
                         used)

          implementing- The budget classification                 country-budget/ accountable-                 1..*
          institution   and percentage breakdown                  institution/implementing-institution
                        for the named
                        implementing institution

          implementing The unique organisation       Organisation country-budget/ accountable-               0..1     <implementing-institution ref=”RW-1201”/>
          institution- identifier for the            Identifier   institution/implementing-institution /@ref
          identifier   implementing institution.

          implementing The name of the               Text         country-budget/ accountable-                 0..1   < implementing-institution ref=”RW-1201”>Rural Health
          institution- implementing institution.                  institution/implementing-institution /text()        Department</ implementing-institution>
          name

          implementing The percentage share           Percent     country-budget/ accountable-                        < implementing-institution ref=”RW-1201”
          institution- allocated to this                          institution/implementing-institution                percent=”100”>Rural Health Department</ implementing-
          share        implementing institution                   /@percent                                           institution>
                       within this accountable
                       institution. (Allows for cases
                       where there is more than
                       one implementing
                       institution; must add up to
                       100% for all the
                       implementing institutions
                       used)
Section       Item            Definition                    Data Format XML                                     Occurs Examples and Notes

              budget-                                                  country-budget/ accountable-
              identifier                                               institution/implementing-institution
                                                                       /budget-item

              budget-         The functional budget code Text          country-budget/ accountable-             1..1   <budget-item code=”A2”>
              identifier-code (from the vocabulary                     institution/implementing-institution
                              specified)                               /budget-item/@code

              budget-         The description of the code Text         country-budget/ accountable-             0..1   <budget-item code=”A2”>Rural Clinics Programme</budget-
              identifier-                                              institution/implementing-institution /          item>
              description                                              budget-item /text()

              budget-         The percentage share          Percent    country-budget/ accountable-                    <budget-item code=”A2” percent=”60”>Rural Clinics
              identifier-     allocated to this budget                 institution/implementing-institution            Programme</budget-item>
              share           item within this institution.            /budget-item/@percent
                              (Allows for more than one
                              budget code per
                              accountable institution;
                              must add up to 100% for
                              each institution used)

Capital       capital-spend   The percentage of the total              capital-spend                            0..1
Expenditure                   commitment that is for
                              capital spending
              percent                                       Percent    capital-spend/@percent                   1..1   <capital-spend percent=”75”/>
B.The IATI Licensing Standard
Open Aid Information Licensing Standard
This Open Aid Information (OAI) Licensing Standard helps encourage the use and reuse of aid information
to help provide better, and more effective, aid to those who receive it. The OAI Licensing Standard is the
result of work by the IATI Secretariat in collaboration with governments, NGOs, international
organisations, lawyers, and open knowledge experts from around the world. This OAI Licensing Standard
is deliberately worded in sufficiently general terms that it could be used for any type of aid-related
information, not just for information published to the IATI Standard.

Summary of the standard
Open Aid Information compliant with this Standard

    ● must be public domain or licensed under an attribution-only open license (the “legal tools”)
        [Element 1];
    ● the legal tools used must be appropriate for data [Element 3];
    ● Intellectual Property (IP) Policies related to the Open Aid Information must be in plain language
        and easily accessible to users [Element 4].

This Standard strongly recommends that Open Aid Information:

    ●   Should use a recognised and established open public license appropriate for databases [Element
        2];
    ●   Should include FAQs and licensing help by the aid information publishers whenever possible
        [Element 5].



What is open aid information?
This standard concerns open aid information. But what is open aid information?

    ● By open we mean open as in the Open (Knowledge) Definition — in essence information (data
        and documents) is open if it can be freely used, reused and redistributed by anyone.
    ● By aid information we mean data and information on aid flows by both official and private
        providers of development assistance (inc. NGOs and Foundations)

Element 1: Aid information must be published under public domain waivers or
attribution-only open licenses as defined by the Open Knowledge Definition.
The goal is for aid information to be effectively used and added to by others as widely as possible.
Therefore the use of licenses which limit commercial re-use or limit the production of derivative works by
excluding use for particular purposes or by specific persons or organisations is discouraged. These
restrictive licenses make it impossible to effectively integrate and re-purpose datasets and prevent
commercial activities that could be used to support preservation and innovation with aid information. As
a result, we have selected the Open Knowledge Definition as our standard for openness for aid
information as it provides for a stable, accepted, legal standard of openness used in multiple fields.
Further, we want to make aid information as widely usable as possible, even within the context of the
Open Knowledge Definition (OKD). Therefore we limit OKD-compliant licenses to those that place aid
information into the public domain (also known as dedications or waivers [2]) and those that (at most)
require attribution of source. Share-alike clauses [1] for aid information are specifically prohibited under
this Standard, as they can cause “license silos” by preventing legal interoperability even between other
openly licensed material -- because they require the use of only that share-alike license.

We therefore recommend and limit open aid information compliant with this Standard as:

    1. Public domain - no copyright, database rights, or contractual rights over the open aid
       information. [3] Examples include Creative Commons’ CC0 tool and the Open Data Commons
       Public Domain Dedication and License (PDDL); OR
    2. Attribution-only open licenses - licenses that allow for use and reuse, with the only restriction
       being that attribution (credit) be given. Examples include the Creative Commons Attribution
       licenses (CC-BY) and the Open Data Commons Attribution License.

Public domain approaches are preferred for aid information.
We strongly recommend that aid information, especially where the result of public funding, be explicitly
placed in the public domain. This is to better serve democracy, transparency, and greater public
participation. We understand that this is not always possible or preferable for publishers, and thus an
open license requiring only attribution to the source is provided as an alternative.

Publishing aid information in the public domain complies with related open data initiatives, including the
Panton Principles, and the Science Commons Protocol for Implementing Open Access Data. Public
domain still means that in many academic disciplines and in other contexts that users will voluntarily
follow established social norms of citation and attribution. Social and academic norms can still apply.

Notes:
This standard applies to aid information, and so does allow for some restrictions, such as for non-aid
information and for technical reasons, such as:
       Technical restrictions on use of web services (such as limiting the number of calls per hour via an
        API).
       Any type of disclaimer of warranties.
       “No endorsement” language and separate (non-open) policies for any trademarks or reserved
        symbols.

[1] Also known as copyleft or reciprocal licensing clauses. Share Alike licenses do comply with the Open
Knowledge Definition, but as noted would not comply with this standard.

[2] Copyright vests automatically, and so giving up rights over a work in copyright before they expire (due
to end of the term) requires a special tool known as a dedication to the public domain or a waiver of
rights. Licenses in this context depend on an underlying copyright to function.

[3] Databases compatible with the Science Commons Protocol for Implementing Open Access Data and
the Panton Principles will fulfil this requirement.
Licenses: Open Data Commons Public Domain Dedication and License (PDDL); Creative Commons
CC0 tool or Public Domain certification; Open Data Commons Attribution License (ODC-BY);
Creative Commons Attribution License (CC-BY)
-------------------

Element 2: Aid information publishers should use recognised public domain
waivers or open licenses.
Making use of recognised open licenses and waivers (together, “legal tools”) helps encourage the
greatest use and reuse of aid information by tapping into already existing online communities built
around these legal tools. [4] This greatly helps use and reuse as recipients of open aid information don’t
have to continually learn new legal terms -- they can learn how one legal tool works and apply it across
multiple sources of open aid information.
In economic terms, using an established and widely used open license or waiver lowers the transaction
costs for users of aid information and by doing so can increase uptake by the community and increase
understanding and therefore compliance with the licenses. For aid information publishers, using an
established legal tool means not having to hire lawyers to draft, maintain, and update a specialist legal
document.
In simple terms, using recognised tools makes it easier on everyone, including both publishers and users.


[4] Providers of open licenses with recognised communities are often referred to as “Public licensing
bodies”. For more information, see http://www.jordanhatcher.com/2010/open-licenses-vs-public-
licenses/

-------------------

Element 3: The legal tools used must be appropriate for data.
Aid information published under this initiative will often be data and databases. Many widely recognised
licenses are not intended for, and are not appropriate for, data or collections of data (databases). We
recommend using legal tools specifically tailored for data for the publication of aid information. The two
key elements:
         Legal - the legal tool must clearly cover the rights over data -- including copyright, database
          rights, and contract -- while taking into account the global networked environment and the many
          different legal jurisdictions involved. Many content or software licenses don’t include database
          rights, for example.

         Practical - particularly for open licenses requiring attribution, the legal tools must take into
          account the practical questions that often come up in a database environment in complying with
          the license terms, such as how and when to attribute the source.

If a legal tool meets these two elements, generally it can be safe for use for aid information compliant
with this standard.

-------------------
Element 4: IP Policies related to aid information must be in plain language and
easily accessible to users.
Publishers should make use of plain language and should highlight their IP policies to users accessing aid
information in order to make it as easy as possible for users to access, read, and understand the rights
that they have to use, reuse, and redistribute the aid information.

-------------------

Element 5: Publishers should include FAQs and licensing help whenever possible.
In order to further help facilitate understanding of their rights and obligations under the license,
publishers and IATI itself should publish detailed FAQs and related licensing help resources. As part of the
work behind this Standard, IATI will build the materials and resources available to both publishers and
users to learn more about Open Aid Information.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:9/29/2012
language:English
pages:15