unAPI
According to its website, an unAPI is:
<templatestyles src="Template:Blockquote/styles.css" />
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.
Contents
Server-side applications which use unAPI
- Bebop
- Evergreen
- refbase [1]
- 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
- Lua error in package.lua at line 80: module 'strict' not found.
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references> tag; parameter "group" is allowed only.
<references />, or <references group="..." />External links
- Lua error in package.lua at line 80: module 'strict' not found.
- Mailing list archives, fall 2004-summer 2006
- Current listserv for unAPI and related discussions
<templatestyles src="Asbox/styles.css"></templatestyles>
 |
This article relating to library science or information science is a stub. You can help Wikipedia by expanding it. |
<templatestyles src="Asbox/styles.css"></templatestyles>
 |
This World Wide Web–related article is a stub. You can help Wikipedia by expanding it. |
- ↑ http://wiki.refbase.net/index.php/UnAPI_service refbase UnAPI page
