Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for extensions #76

Open
dalepotter opened this issue May 31, 2015 · 3 comments
Open

Add documentation for extensions #76

dalepotter opened this issue May 31, 2015 · 3 comments

Comments

@dalepotter
Copy link
Contributor

Include links to known extensions (France / USA), and best practices, experiences with generating extensions.

@dalepotter
Copy link
Contributor Author

This issue might better sit in the IATI-Extra-Documentation (under the current documentation structure) with the source for the current page on namespaces and extensions being here: https://github.com/IATI/IATI-Extra-Documentation/blob/version-2.03/en/namespaces-extensions.rst
Also linking to IATI/IATI-Guidance#21 which also touched on this issue.

Regardless of where this issue sits, it might be worth adding to this page. Whilst IATI/IATI-Extra-Documentation@243283c added extra context on the use of 'namespaced' element fields, there is currently no explicit reference that IATI Standard attributes can also be namespaced.

It might also be worth highlighting known/commonly-used extensions (as identified by @rolfkleef in a Discuss post) as real-world usage examples. Citing these publishers may also help from a data use perspective, since it identities publishes who may be providing information supplementary to the IATI Standard fields.

@samuele-mattiuzzo
Copy link
Contributor

Thanks Dale!

@andylolz
Copy link
Contributor

Extensions are currently listed on this dashboard page, and they add quite a lot of noise.

One way to highlight extension usage might be to separate them out on the dashboard, and then point to an extension-specific page.

This avoids pointing to individual publishers manually, which I guess would involve maintaining a curated list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants