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
Client tools which can use unAPI
gollark: ₱700™
gollark: …
gollark: Maybe if you actually worked on it instead of just dithering on trying to get <@378840449152188419> to look for weeks?
gollark: …
gollark: My ridiculously convoluted serialization scheme appears to break on it somehow.
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 is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.