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.
Server-side applications which use unAPI
Client tools which can use unAPI
- Daniel Chudnov; Peter Binkley, Jeremy Frumkin, Michael J. Giarlo, Mike Rylander, Ross Singer, Ed Summers (July 2006). "Introducing unAPI". Ariadne (48).
- Chudnov, Daniel (April 2007). "unAPI". Computers in Libraries 27 (4): 21. ISSN 1041-7915. Retrieved 2008-03-11.
- http://wiki.refbase.net/index.php/UnAPI_service refbase UnAPI page
- Mailing list archives, fall 2004-summer 2006
- Current listserv for unAPI and related discussions
|This article relating to library science or information science is a stub. You can help Wikipedia by expanding it.|
|This World Wide Web–related article is a stub. You can help Wikipedia by expanding it.|