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.
Server-side applications which use unAPI
- Bebop
- Evergreen
- Koha
- refbase2
- 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
See also
Further reading
- Chudnov, Daniel (2012-03-19). Koster, James (ed.). "unAPI: an un-API for webapps - A super-simple way to get stuff". refbase. Archived from the original on 2014-12-18. Retrieved 2020-11-09.
- Back, Godmar; Binkley, Peter; Celeste, Eric; Chudnov, Daniel; Clarke, Kevin; D'Arcus, Bruce; Dodds, Leigh; Eaton, Alf; Fawcett, Graham; Frumkin, Jeremy; Giarlo, Michael; Hellman, Eric; Liu, Xiaoming; Pearson, Phillip; Rhyno, Art; Rylander, Mike; Sanderson, Rob; Singer, Ross; Summers, Ed; Toub, Steve; Yee, Raymond; Young, Jeff (2006-07-23) [2006-01-14]. "contribution". unAPI Version 1 (normative). By Chudnov, Daniel. Koster, James (ed.). 1.0. Archived from the original on 2014-03-31.
External links
References
Chudnov, Daniel "Dan"; Binkley, Peter; Frumkin, Jeremy; Giarlo, Michael J.; Rylander, Mike; Singer, Ross; Summers, Ed (2006-07-30). "Introducing UnAPI". Ariadne (48). Archived from the original on 2020-11-09. Retrieved 2017-07-11. http://www.ariadne.ac.uk/issue48/chudnov-et-al ↩
"UnAPI service". refbase. Archived from the original on 2020-11-09. Retrieved 2020-11-09. http://wiki.refbase.net/index.php/UnAPI_service ↩