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: Wow, their code formatting is HIGHLY something.
gollark: Anyway, thus run good and not evil program?
gollark: Why ship an XML parser? Just use regexes.
gollark: No, it does NOT do that, thus run program.
gollark: Yes, that would be ridiculous; like I said, it is NOT libevilpotatos OR obfuscation to disguise NONEXISTENT evil parts.

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
  1. Chudnov, Dan; Binkley, Peter; Summers, Ed; Frumkin, Jeremy; Giarlo, Michael J.; Rylander, Mike; Singer, Ross (2006). "Introducing UnAPI". Retrieved 11 July 2017.
  2. http://wiki.refbase.net/index.php/UnAPI_service refbase UnAPI page


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.