Application programming interface - Revision history

Shawndouglas: /* Notes */ Added cat

2022-09-17T21:15:49Z

Notes: Added cat

← Older revision		Revision as of 21:15, 17 September 2022
Line 5:		Line 5:
	<!---Place all category tags here-->		<!---Place all category tags here-->
	[[Category:Articles transcluded from other wikis]]		[[Category:Articles transcluded from other wikis]]
			[[Category:Software and hardware terms]]

Shawndouglas: Updated to a transclusion

2022-01-07T20:23:38Z

Updated to a transclusion

Show changes

Shawndouglas: Minor grammatical changes

2015-05-26T17:16:13Z

Minor grammatical changes

← Older revision		Revision as of 17:16, 26 May 2015
Line 1:		Line 1:
	[[File:Linux kernel API.svg\|right\|thumb\|650px\|This diagram shows a comparison of the Linux kernel API with the POSIX API.]]		[[File:Linux kernel API.svg\|right\|thumb\|650px\|This diagram shows a comparison of the Linux kernel API with the POSIX API.]]
	An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers.		An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers. An API can be created for applications, libraries, operating systems, etc. as a way of defining their "vocabularies" and resource request conventions (e.g. function-calling conventions). It may include specifications for routines, data structures, object classes, and protocols used to communicate between the consumer program and the implementer program of the API.<ref>{{cite web\|

	An API can be created for applications, libraries, operating systems, etc., as a way of defining their "vocabularies" and ~~resources~~ request conventions (e.g. function-calling conventions). It may include specifications for routines, data structures, object classes, and protocols used to communicate between the consumer program and the implementer program of the API.<ref>{{cite web\|
	title=Definition of: API\|		title=Definition of: API\|
	url=http://www.pcmag.com/encyclopedia/term/37856/api\|		url=http://www.pcmag.com/encyclopedia/term/37856/api\|
Line 17:		Line 15:
	==Concept==		==Concept==
	An API can be:		An API can be:
	* general, the full set of an API that is bundled in the libraries of a programming language, e.g. Standard Template Library in C++ or Java API.		* general: the full set of an API that is bundled in the libraries of a programming language, e.g. Standard Template Library in C++ or Java API.

	* specific, meant to address a specific problem, e.g. Google Maps API or Java API for XML Web Services.		* specific: meant to address a specific problem, e.g. Google Maps API or Java API for XML Web Services.

	* language-dependent, meaning it is only available by using the syntax and elements of a particular language, which makes the API more convenient to use.		* language-dependent: meaning it is only available by using the syntax and elements of a particular language, which makes the API more convenient to use.

	* language-independent, written so that it can be called from several programming languages. This is a desirable feature for a service-oriented API that is not bound to a specific process or system and may be provided as remote procedure calls or web services. For example, a website that allows users to review local restaurants is able to layer their reviews over maps taken from Google Maps, because Google Maps has an API that facilitates this functionality. Google Maps' API controls what information a third-party site can use and how they can use it.		* language-independent: written so that it can be called from several programming languages. This is a desirable feature for a service-oriented API that is not bound to a specific process or system and may be provided as remote procedure calls or web services. For example, a website that allows users to review local restaurants is able to layer their reviews over maps taken from Google Maps, because Google Maps has an API that facilitates this functionality. Google Maps' API controls what information a third-party site can use and how they can use it.

	API may be used to refer to a complete interface, a single function, or even a set of APIs provided by an organization. Thus, the scope of meaning is usually determined by the context of usage.		API may be used to refer to a complete interface, a single function, or even a set of APIs provided by an organization. Thus, the scope of meaning is usually determined by the context of usage.
Line 29:		Line 27:
	==Advanced explanation==		==Advanced explanation==
	An API may describe the ways in which a particular task is performed.		An API may describe the ways in which a particular task is performed.
	In procedural languages like C ~~language~~ the ''action'' is usually ''mediated'' by a function call.
			In procedural languages like C, for example, the ''action'' is usually ''mediated'' by a function call.

	For instance: the <code>math.h</code> include file for the C language contains the definition of the function prototypes of the mathematical functions available in the C language library for mathematical processing (usually called <code>libm<code>).		For instance: the <code>math.h</code> include file for the C language contains the definition of the function prototypes of the mathematical functions available in the C language library for mathematical processing (usually called <code>libm<code>).

Shawndouglas: Added image.

2015-05-26T17:04:40Z

Added image.

← Older revision		Revision as of 17:04, 26 May 2015
Line 1:		Line 1:
			[[File:Linux kernel API.svg\|right\|thumb\|650px\|This diagram shows a comparison of the Linux kernel API with the POSIX API.]]
	An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers.		An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers.

Shawndouglas: /* References */ Updated cat.

2014-08-22T16:21:19Z

References: Updated cat.

← Older revision		Revision as of 16:21, 22 August 2014
Line 223:		Line 223:

	<!---Place all category tags here-->		<!---Place all category tags here-->
	[[Category:Software terms]]		[[Category:Software and hardware terms]]

Shawndouglas: /* References */ Added cat

2014-08-06T19:03:47Z

References: Added cat

← Older revision		Revision as of 19:03, 6 August 2014
Line 221:		Line 221:
	==References==		==References==
	{{reflist\|colwidth=50em}}		{{reflist\|colwidth=50em}}

			<!---Place all category tags here-->
			[[Category:Software terms]]

Shawndouglas: Added attribution.

2014-04-24T23:18:01Z

Added attribution.

← Older revision		Revision as of 23:18, 24 April 2014
Line 1:		Line 1:
	~~''(This article was taken from Wikipedia)''~~

	An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers.		An '''application programming interface''' ('''API''') is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction, similar to the way the user interface facilitates interaction between humans and computers.

Line 210:		Line 208:
	* [[SWIG]] opensource interfaces bindings generator from many languages to many languages (Typically Compiled->Scripted)		* [[SWIG]] opensource interfaces bindings generator from many languages to many languages (Typically Compiled->Scripted)
	* F2PY:<ref>[http://www.f2py.org/ F2PY.org]</ref> Fortran to Python interface generator.		* F2PY:<ref>[http://www.f2py.org/ F2PY.org]</ref> Fortran to Python interface generator.

	~~==References==~~
	~~{{reflist\|colwidth=50em}}~~

	==External links==		==External links==
Line 219:		Line 214:
	* [http://java.sun.com/developer/technicalArticles/WebServices/soa/ Service-Oriented Architecture (SOA): The Road to Enterprise Application Integration (EAI)]		* [http://java.sun.com/developer/technicalArticles/WebServices/soa/ Service-Oriented Architecture (SOA): The Road to Enterprise Application Integration (EAI)]
	* [http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2489/186491/186605/Jtc1_Directives.pdf?nodeid=3959538&vernum=0 ISO/IEC JTC 1 Directives, 5th Edition Version 3.0, Annex J: Guidelines for API standardization]		* [http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2489/186491/186605/Jtc1_Directives.pdf?nodeid=3959538&vernum=0 ISO/IEC JTC 1 Directives, 5th Edition Version 3.0, Annex J: Guidelines for API standardization]

			==Notes==

			The bulk of this article is reused from [http://en.wikipedia.org/wiki/Application_programming_interface the Wikipedia article].

			==References==
			{{reflist\|colwidth=50em}}

Shawndouglas: Experimenting with date templates.

2013-10-26T16:07:44Z

Experimenting with date templates.

← Older revision		Revision as of 16:07, 26 October 2013
Line 5:		Line 5:
	An API can be created for applications, libraries, operating systems, etc., as a way of defining their "vocabularies" and resources request conventions (e.g. function-calling conventions). It may include specifications for routines, data structures, object classes, and protocols used to communicate between the consumer program and the implementer program of the API.<ref>{{cite web\|		An API can be created for applications, libraries, operating systems, etc., as a way of defining their "vocabularies" and resources request conventions (e.g. function-calling conventions). It may include specifications for routines, data structures, object classes, and protocols used to communicate between the consumer program and the implementer program of the API.<ref>{{cite web\|
	title=Definition of: API\|		title=Definition of: API\|
	url=http://www.pcmag.com/~~encyclopedia_term~~/~~0,2542,t=application+programming+interface&i=~~37856~~,00.asp~~\|		url=http://www.pcmag.com/encyclopedia/term/37856/api\|
	publisher=PC Magazine\|		publisher=PC Magazine\|
	~~year=1996\|~~
	accessdate=28 June 2009}}</ref><ref>{{cite web\|		accessdate=28 June 2009}}</ref><ref>{{cite web\|
	first=David\|		first=David\|
Line 121:		Line 120:
	\|coauthors = Schahram Dustdar, and Amit Sheth		\|coauthors = Schahram Dustdar, and Amit Sheth
	\|title = Services Mashups: The New Generation of Web Applications		\|title = Services Mashups: The New Generation of Web Applications
	\|url = http://~~dsonline~~.~~computer~~.org/~~portal~~/~~site/dsonline/menuitem.9ed3d9924aeb0dcd82ccc6716bbe36ec/index~~.jsp?~~&pName~~=~~dso_level1~~&~~path~~=~~dsonline/2008/09~~&~~file~~=~~w5gei~~.~~xml&xsl=article~~.~~xsl~~		\|url = http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=4620089&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D4620089
	\|work = IEEE Internet Computing, vol. 12, no. 5		\|work = IEEE Internet Computing, vol. 12, no. 5
	\|publisher = Institute of Electrical and Electronics Engineers		\|publisher = Institute of Electrical and Electronics Engineers
	\|pages = 13–15		\|pages = 13–15
	\|~~year~~ = 2008		\|date = September 2008
	}}		}}
	</ref> Web APIs allow the combination of multiple services into new applications known as Mashup_(web_application_hybrid)\|mashups.<ref>		</ref> Web APIs allow the combination of multiple services into new applications known as Mashup_(web_application_hybrid)\|mashups.<ref>
Line 159:		Line 158:
	\|title = Run Older Programs On Windows XP		\|title = Run Older Programs On Windows XP
	\|url = http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx		\|url = http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx
	\|publisher = Microsoft		\|archiveurl = https://web.archive.org/web/20110320094425/http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx
			\|publisher = Microsoft
	\|pages = 4		\|pages = 4
	\|language = EN		\|language = EN
	\|~~month~~ = October		\|date = 15 October 2001
	\|~~year~~ = ~~2001~~		\|archivedate = 20 March 2011
			\|accessdate = 26 October 2013
	}}</ref>		}}</ref>

Line 186:		Line 187:
	publisher=USENIX\|		publisher=USENIX\|
	format=PDF\|		format=PDF\|
	~~year~~=2005\|		date=April 2005
	~~month=April\|~~
	accessdate=04 June 2009}}</ref>		accessdate=04 June 2009}}</ref>

Shawndouglas: Changed date format in attempt to remove invalide date parameter

2013-10-26T15:59:33Z

Changed date format in attempt to remove invalide date parameter

← Older revision		Revision as of 15:59, 26 October 2013
Line 8:		Line 8:
	publisher=PC Magazine\|		publisher=PC Magazine\|
	year=1996\|		year=1996\|
	accessdate=2009~~-06-28~~}}</ref><ref>{{cite web\|		accessdate=28 June 2009}}</ref><ref>{{cite web\|
	first=David\|		first=David\|
	last=Orenstein\|		last=Orenstein\|
Line 14:		Line 14:
	title=QuickStudy: Application Programming Interface (API)\|		title=QuickStudy: Application Programming Interface (API)\|
	publisher=Computerworld\|		publisher=Computerworld\|
	date=2000~~-01-10~~\|		date=10 January 2000\|
	accessdate=2009~~-06-04~~}}</ref>		accessdate=04 June 2009}}</ref>

	==Concept==		==Concept==
Line 134:		Line 134:
	\|url = http://www.pcworld.com/businesscenter/article/145039/so_what_is_an_enterprise_mashup_anyway.html		\|url = http://www.pcworld.com/businesscenter/article/145039/so_what_is_an_enterprise_mashup_anyway.html
	\|work = [[PC World (magazine)\|PC World]]		\|work = [[PC World (magazine)\|PC World]]
	\|date = 2008~~-04-23~~		\|date = 23 April 2008
	}}</ref>		}}</ref>

Line 146:		Line 146:
	{{cite web		{{cite web
	\|title = Dynamic Community content via APIs		\|title = Dynamic Community content via APIs
	\|date = October ~~26 2009~~		\|date = 26 October 2009
	~~\|year =~~ 2009
	}}		}}
	yes		yes
Line 189:		Line 188:
	year=2005\|		year=2005\|
	month=April\|		month=April\|
	accessdate=2009~~-06-04~~}}</ref>		accessdate=04 June 2009}}</ref>

	==API examples==		==API examples==

Shawndouglas: Removed cat.

2013-10-24T16:17:37Z

Removed cat.

← Older revision		Revision as of 16:17, 24 October 2013
Line 220:		Line 220:
	* [http://java.sun.com/developer/technicalArticles/WebServices/soa/ Service-Oriented Architecture (SOA): The Road to Enterprise Application Integration (EAI)]		* [http://java.sun.com/developer/technicalArticles/WebServices/soa/ Service-Oriented Architecture (SOA): The Road to Enterprise Application Integration (EAI)]
	* [http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2489/186491/186605/Jtc1_Directives.pdf?nodeid=3959538&vernum=0 ISO/IEC JTC 1 Directives, 5th Edition Version 3.0, Annex J: Guidelines for API standardization]		* [http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2489/186491/186605/Jtc1_Directives.pdf?nodeid=3959538&vernum=0 ISO/IEC JTC 1 Directives, 5th Edition Version 3.0, Annex J: Guidelines for API standardization]


	~~{{DEFAULTSORT:Application Programming Interface}}~~
	~~[[Category:Application programming interfaces\|*]]~~