Scrapping text of purely code elements
- This proposal is to remove the ability to supply multilingual text between element braces on elements that require the use of codelists. In these cases the code itself should be seen as unambiguous and authoratitive, and the codelists available on iatistandard.org should be upgraded to supply all necessary translations of both code names and descriptions.
- This will apply to the following elements:
- Activity Standard
- activity-status
- activity-scope
- collaboration-type
- default-finance-type
- default-flow-type
- default-aid-type
- default-tied-status
- transaction/transaction-type
- transaction/flow-type
- transaction/aid-type
- transaction/finance-type
- transaction/tied-status
- transaction/disbursement-channel
- document-link/category
- document-link/language
- related-activity
- crs-add/loan-terms/repayment-type
- crs-add/loan-terms/repayment-plan
- location/exactness
- location/location-id
- location/administrative
- Organisation Standard
-
document-link/category
-
document-link/language
- for discussion go to http://support.iatistandard.org/entries/41585166-General-Standardise-multi-lingual-text-fields
Including nested, multi-lingual text elements for all elements containing free text
- Example 1
- Current Usage
- <title xml:lang="en">English Title</title>
- <title xml:lang="fr">Titre français</title>
- Proposed Change
- <title>
- <narrative xml:lang="en">English Title</narrative>
- <narrative xml:lang="fr">Titre français</narrative>
- </title>
- Example 2
- Current Usage
- <sector vocabulary="RO" xml:lang="en code="456">Water and sanitation</sector>
- <sector vocabulary="RO" xml:lang="fr" code="456">Eau et assainissement</sector>
- Proposed Change
- <sector vocabulary="99" code="456">
- <narrative xml:lang="en">Water and sanitation</narrative>
- <narrative xml:lang="en">Eau et assainissement</narrative>
- </sector>
- Elements to be modified are:
- Activity Standard
- reporting-org
- participating-org
- title
- description
- activity-date
- contact-info/organisation
- contact-info/person-name
- contact-info/job-title
- contact-info/mailing-address
- recipient-country
- recipient-region
- location/name
- location/description
- location/activity-description
- sector (for use only with reporting organisation's own codes)
- policy-marker (for use only with reporting organisation's own codes)
- country-budget-items/budget-item/description
- transaction/description
- transaction/receiver-org
- transaction/provider-org
- transaction/recipient-country
- transaction/recipient-region
- document-link/title
- conditions/condition
- result/title
- result/description
- result/indicator/title
- result/indicator/description
- result/indicator/baseline/comment
- result/indicator/period/target/comment
- result/indicator/period/actual/comment
- Organisation Standard
- reporting-org
- iati-organisation
- recipient-country-budget/recipient-country
- document-link/title
- document-link/recipient-country
For technical details about implementing this proposal go to : https://github.com/IATI/IATI-Schemas/issues/68
1 Comments