[PROJECT IDEA] IATI Extensions library

[stevieflow]

Rationale

Extensions are really useful to both IATI publishers and data users
Having a central library of extensions that are in use will help a) users document them b) data users use the data that uses them c) avoid duplication of resources when people silently work on the same / similar issue d) help test concepts and data models that could then form proposals for inclusion in the IATI standard (if really needed)

Proposal

Open Contracting have a nice solution for this, it seems

OCDS Extensions explorer: https://extensions.open-contracting.org/en/

GitHub organisation (with a repo for each extension): https://github.com/open-contracting-extensions

This might be too much for now -- but the model could be interesting in terms of us getting some of the extensions we know of (multi-currency (UNHCR); transaction cross-referencing (AfDB); additional transaction metadata (USAID)) into place...

@markbrough @davidmegginson would be interested in this, I think...

[davidmegginson]

I strongly support this suggestion. I think extensions are the best way forward for IATI, given how hard it is to move the core standard now. Just central documentation of namespaces and extension elements might be good enough to start (e.g. we don't need to write any code).

[markbrough]

Definitely keen on this!!

[stevieflow]

OK!

I started some data...

https://docs.google.com/spreadsheets/d/1qFGk9Qi39YVCeuxikTLcu6_L0xH5wYJvlOBNELFluYY/edit#gid=0

[markbrough]

Thinking about how we could add this:

• a markdown file for each extension, briefly explaining what it does
• an xsd schema which is then automatically built into documentation?

And then list these on the Dashboard?

[matmaxgeds]

I hope we can also help setup the infrastructure for others who might want an extension, but wouldn't know how to xsd it into existence.....e.g. provide the scaffolding behind the scenes. I am thinking example (draft) extensions for people to run with, a way to see other extension ideas in planning, or maybe a way for people to jot down ideas in human text, that we can convert to an extension for them.

I would love to see a 'debt' extension for example. And surely we could interest on of the climate groups in one for them. FYI, I also think that extensions are probably a much better lens to think about the 'core', which therefore covers just those parts that support multiple extensions, and then fields that only have one user group get put into an extension.

Would also be v. cool to have a table that shows which extension are most in use/popular, for newbies to know what others are using, and also search if there is one that already meets their needs.

[davidmegginson]

Sounds good. I think we also need some static narrative text and a short How-To, because the idea and details of IATI extensions won't be familiar to most of the community. I'd be happy to provide a first draft of the content.

[markbrough]

That would be fantastic, thanks @davidmegginson!

[stevieflow]

I started some data...

I also made the doc viewable !