This proposal is part of the 2.03 upgrade process, please comment by replying below.
Standard
Activity and Organisation
**Schema Object** None
**Type of Change** Redefine embedded codelist as non-embedded
**Issue** The IATI standard contains a mixture of “embedded” and “non-embedded” codelists. Embedded codelists can only be modified through the formal upgrade process. Non-embedded codelists can be modified through a [light-touch consultation process](http://iatistandard.org/202/codelists/codelist-management/). In order to increase the flexibility and responsiveness of the standard only those codelists that impact on the functionality of data processing should remain embedded and all others should be redefined as “Non-embedded”.
**Proposal** Redefine the following Embedded codelists as Non-embedded.
- ActivityScope; BudgetIdentifier; BudgetIdentifierSector-category; BudgetIdentifierSector; BudgetIdentifierVocabulary; CRSAddOtherFlags; ConditionType; ContactType; DescriptionType; DisbursementChannel; DocumentCategory-category; DocumentCategory; GazetteerAgency; GeographicExactness; GeographicLocationClass; GeographicLocationReach; GeographicVocabulary; GeographicalPrecision; IndicatorMeasure; LoanRepaymentPeriod; LoanRepaymentType; OtherIdentifierType; PolicyMarker; PolicyMarkerVocabulary; PublisherType; RegionVocabulary; ResultType; SectorVocabulary; TiedStatus; VerificationStatus
**Standards Day** Accepted in principle but check details of which should be moved
**Links** http://bit.ly/2m1jy70 Previous discussions - https://iaticonnect.org/group/standard-management-consultations-0/discu…
Hi Hayden
Code lists i.m.o. should never depreciate old values since these values could legitimately have been used in past activities which are still published. A solution could be to flag old values. Values in non-embedded code lists which are no longer valid, could be flagged by 2 fields ‘valid from’ and ‘valid until’ where ‘valid until’ is empty when it is the current value.
In this way downward compatibility is guaranteed.
At 2.02 a method was added to deprecate (withdraw) codes through use of use of the status, activation-date and withdrawal-date attributes on Codelists. The proposal wasn’t, however, fleshed out to cover usage. For example, the following points were not answered:
As such, there stand the points raised in my previous post.