unAPI

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

• Bebop
• Evergreen
• refbase ^[1]
• WordPress (via a plugin)

Client tools which can use unAPI

• Zotero

See also

• COinS

Further information

• 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. 

References

External links

• unAPI
• Mailing list archives, fall 2004-summer 2006
• Current listserv for unAPI and related discussions