unAPI

The UnAPI specification is only two pages long.[1]

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

Zotero

gollark: They're an avid osmarks.net user, probably.

gollark: "SolarFlame5".

gollark: https://web.archive.org/web/20210322123606/https://hpage.osmarks.net/index.html

gollark: It does.

gollark: Someone wants the old "welcome to nginx" page with self-replication, do you still have it?

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

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 is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.