unAPI
Jump to navigation
Jump to search
This article relies largely or entirely on a single source. (June 2017) |
The topic of this article may not meet Wikipedia's general notability guideline. (October 2023) |
According to its website, an unAPI is:
a tiny HTTP API any web application may use to co-publish discretely identified objects in both HTML pages and disparate bare object formats. It consists of three parts: an identifier microformat, an HTML autodiscovery link, and three HTTP interface functions, two of which have a standardized response format.
The unAPI specification is only two pages long.[1]
Server-side applications which use unAPI
[edit | edit source]- Bebop
- Evergreen
- Koha
- refbase[2]
- WordPress (via a plugin)
- VITAL, digital repository
- invenio digital library framework
- Omeka S, web-publishing platform for academic and cultural repositories
- Glottolog a clld app supports unAPI on its root page.
Client tools which can use unAPI
[edit | edit source]See also
[edit | edit source]References
[edit | edit source]Further reading
[edit | edit source]- Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
