I know that this request for three additions to the Org Registration Agency codelist is grounded in a use case for the Open Contracting Data Standard. It’s a great example of cross-over and synergy between two open data standards, working in different domains.
As more organisations prepare, publish and use data across standards, updates to this list could be key. The current IATI documentation states:
Because there is a need to add registration agencies quickly, so that people can do their work, and because we anticipate many additions that will not be of interest to most people, we will add values to this list without making announcements. Values to be added will be agreed at the weekly team meeting.
It’s great that codes can be added quite quickly. However, the community might want to add and utilise codes immediately in some instances - and perhaps without the need for a sanction from the “centre”. Could such a situation exist, and be helpful?
Rather than wait for a code to be added to the central list (a pull mechanism) could we imagine a setup where a data publisher would actively inform the community of their intended code (a push)? It is then a task to maintain the publication of the list, but not approve the content, making this list chaordic ; powered from the periphery, unified from the core
I appreciate that this might sound like a play on concepts - but it could be important to position the management of this list as community-led, rather than centrally-governed. This may well be the intention already, so it would be useful to clarify.