Language is handled in two ways in code lists - as an attribute of the XML file and as a column in -some- tables.
To be able to provide a version of an activity with code labels provided where available by native language text, it is important that the structure be agreed. Form the point of authoring, maintenance and performance, separate documents per codelist/language is preferable and already handled by the database. This approach makes the language column where present redundant .
Is there a reference to discussion of this issue anywhere in IATI?
Language is handled in two ways in code lists - as an attribute of the XML file and as a column in -some- tables. To be able to provide a version of an activity with code labels provided where available by native language text, it is important that the structure be agreed. Form the point of authoring, maintenance and performance, separate documents per codelist/language is preferable and already handled by the database. This approach makes the language column where present redundant .
Is there a reference to discussion of this issue anywhere in IATI?