unAPI
 | This article relies largely or entirely on a single source. (June 2017) |
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
- 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
Client tools which can use unAPI
See also
Further information
- Daniel Chudnov; Peter Binkley; Jeremy Frumkin; Michael J. Giarlo; Mike Rylander; Ross Singer; Ed Summers (July 2006). "Introducing unAPI". Ariadne (48).
References
- ^ Chudnov, Dan; Binkley, Peter; Summers, Ed; Frumkin, Jeremy; Giarlo, Michael J.; Rylander, Mike; Singer, Ross (2006). "Introducing UnAPI". Retrieved 11 July 2017.
- ^ http://wiki.refbase.net/index.php/UnAPI_service refbase UnAPI page
External links
- "unAPI". Archived from the original on 2014-12-18.
- Mailing list archives, fall 2004-summer 2006
- Current listserv for unAPI and related discussions
 | This article about a digital library is a stub. You can help Wikipedia by expanding it. |