Wikipedia

API

For other uses, seeAPI (disambiguation).
"Api.php" redirects here. For the Wikipedia API, seeSpecial:ApiHelp.

Anapplication programming interface(API) is a connection betweencomputersor betweencomputer programs.It is a type of softwareinterface,offering a service to other pieces ofsoftware.[1]A document or standard that describes how to build such a connection or interface is called anAPI specification.A computer system that meets this standard is said toimplementorexposean API. The term API may refer either to the specification or to the implementation.

In contrast to auser interface,which connects a computer to a person, an application programming interface connects computers or pieces of software to each other. It is not intended to be used directly by a person (theend user) other than acomputer programmerwho is incorporating it into software. An API is often made up of different parts which act as tools or services that are available to the programmer. A program or a programmer that uses one of these parts is said tocallthat portion of the API. The calls that make up the API are also known assubroutines,methods, requests, orendpoints.An API specificationdefinesthese calls, meaning that it explains how to use or implement them.

One purpose of APIs is tohide the internal detailsof how a system works, exposing only those parts a programmer will find useful and keeping them consistent even if the internal details later change. An API may be custom-built for a particular pair of systems, or it may be a shared standard allowinginteroperabilityamong many systems.

The term API is often used to refer toweb APIs,[2]which allow communication between computers that are joined by theinternet.There are also APIs forprogramming languages,software libraries,computeroperating systems,andcomputer hardware.APIs originated in the 1940s, though the term did not emerge until the 1960s and 70s.

Purpose

edit

An API opens a software system to interactions from the outside. It allows two software systems to communicate across a boundary — an interface — using mutually agreed-upon signals.[3]In other words, an API connects software entities together. Unlike auser interface,an API is typically not visible to users. It is an "under the hood" portion of a software system, used for machine-to-machine communication.[4]

A well-designed API exposes only objects or actions needed by software or software developers. It hides details that have no use. Thisabstractionsimplifies programming.[5]

Metaphorically, APIs connect software like interlocking blocks.

Building software using APIs has been compared to using building-block toys, such asLegobricks. Software services or software libraries are analogous to the bricks; they may be joined together via their APIs, composing a new software product.[6]The process of joining is calledintegration.[3]

As an example, consider a weather sensor that offers an API. When a certain message is transmitted to the sensor, it will detect the current weather conditions and reply with a weather report. The message that activates the sensor is an APIcall,and the weather report is an APIresponse.[7]A weather forecasting app might integrate with a number of weather sensor APIs, gathering weather data from throughout a geographical area.

An API is often compared to acontract.It represents an agreement between parties: a service provider who offers the API and the software developers who rely upon it. If the API remains stable, or if it changes only in predictable ways, developers' confidence in the API will increase. This may increase their use of the API.[8]

History of the term

edit
A diagram from 1978 proposing the expansion of the idea of the API to become a general programming interface, beyondapplication programsalone[9]

The termAPIinitially described an interface only for end-user-facing programs, known asapplication programs.This origin is still reflected in the name "application programming interface." Today, the term is broader, including alsoutility softwareand evenhardware interfaces.[10]

The idea of the API is much older than the term itself. British computer scientistsMaurice WilkesandDavid Wheelerworked on a modularsoftware libraryin the 1940s forEDSAC,an early computer. Thesubroutinesin this library were stored onpunched paper tapeorganized in afiling cabinet.This cabinet also contained what Wilkes and Wheeler called a "library catalog" of notes about each subroutine and how to incorporate it into a program. Today, such a catalog would be called an API (or an API specification or API documentation) because it instructs a programmer on how to use (or "call" ) each subroutine that the programmer needs.[10]

Wilkes and Wheeler's bookThe Preparation of Programs for an Electronic Digital Computercontains the first published API specification.Joshua Blochconsiders that Wilkes and Wheeler "latently invented" the API, because it is more of a concept that is discovered than invented.[10]

Although the people who coined the term API were implementing software on aUnivac 1108,the goal of their API was to makehardware independentprograms possible.[11]

The term "application program interface" (without an-ingsuffix) is first recorded in a paper calledData structures and techniques for remotecomputer graphicspresented at anAFIPSconference in 1968.[12][10]The authors of this paper use the term to describe the interaction of an application—a graphics program in this case—with the rest of the computer system. A consistent application interface (consisting ofFortransubroutine calls) was intended to free the programmer from dealing with idiosyncrasies of the graphics display device, and to providehardware independenceif the computer or the display were replaced.[11]

The term was introduced to the field ofdatabasesbyC. J. Date[13]in a 1974 paper calledTheRelationalandNetworkApproaches: Comparison of the Application Programming Interface.[14]An API became a part of theANSI/SPARC frameworkfordatabase management systems.This framework treated the application programming interface separately from other interfaces, such as the query interface. Database professionals in the 1970s observed these different interfaces could be combined; a sufficiently rich application interface could support the other interfaces as well.[9]

This observation led to APIs that supported all types of programming, not just application programming. By 1990, the API was defined simply as "a set of services available to a programmer for performing certain tasks" by technologistCarl Malamud.[15]

Screenshot ofWeb APIdocumentation written byNASA

The idea of the API was expanded again with the dawn ofremote procedure callsandweb APIs.Ascomputer networksbecame common in the 1970s and 80s, programmers wanted to call libraries located not only on their local computers, but on computers located elsewhere. These remote procedure calls were well supported by theJavalanguage in particular. In the 1990s, with the spread of theinternet,standards likeCORBA,COM,andDCOMcompeted to become the most common way to expose API services.[16]

Roy Fielding's dissertationArchitectural Styles and the Design of Network-based Software ArchitecturesatUC Irvinein 2000 outlinedRepresentational state transfer(REST) and described the idea of a "network-based Application Programming Interface" that Fielding contrasted with traditional "library-based" APIs.[17]XMLandJSONweb APIs saw widespread commercial adoption beginning in 2000 and continuing as of 2021. The web API is now the most common meaning of the term API.[2]

TheSemantic Webproposed byTim Berners-Leein 2001 included "semantic APIs" that recast the API as anopen,distributed data interface rather than a software behavior interface.[18]Proprietaryinterfaces and agents became more widespread than open ones, but the idea of the API as a data interface took hold. Because web APIs are widely used to exchange data of all kinds online, API has become a broad term describing much of the communication on the internet.[16]When used in this way, the term API has overlap in meaning with the termcommunication protocol.

Types

edit

Libraries and frameworks

edit

The interface to asoftware libraryis one type of API. The API describes and prescribes the "expected behavior" (a specification) while the library is an "actual implementation" of this set of rules.

A single API can have multiple implementations (or none, being abstract) in the form of different libraries that share the same programming interface.

The separation of the API from its implementation can allow programs written in one language to use a library written in another. For example, becauseScalaandJavacompile to compatiblebytecode,Scala developers can take advantage of any Java API.[19]

API use can vary depending on the type of programming language involved. An API for aprocedural languagesuch asLuacould consist primarily of basic routines to execute code, manipulate data or handle errors while an API for anobject-oriented language,such as Java, would provide a specification of classes and itsclass methods.[20][21]Hyrum's law states that "With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody."[22]Meanwhile, several studies show that most applications that use an API tend to use a small part of the API.[23]

Language bindingsare also APIs. By mapping the features and capabilities of one language to an interface implemented in another language, a language binding allows a library or service written in one language to be used when developing in another language.[24]Tools such asSWIGand F2PY, aFortran-to-Pythoninterface generator, facilitate the creation of such interfaces.[25]

An API can also be related to asoftware framework:a framework can be based on several libraries implementing several APIs, but unlike the normal use of an API, the access to the behavior built into the framework is mediated by extending its content with new classes plugged into the framework itself.

Moreover, the overall program flow of control can be out of the control of the caller and in the framework's hands byinversion of controlor a similar mechanism.[26][27]

Operating systems

edit

An API can specify the interface between an application and theoperating system.[28]POSIX,for example, specifies a set of common APIs that aim to enable an application written for a POSIX conformant operating system to becompiledfor another POSIX conformant operating system.

LinuxandBerkeley Software Distributionare examples of operating systems that implement the POSIX APIs.[29]

Microsofthas shown a strong commitment to a backward-compatible API, particularly within itsWindows API(Win32) library, so older applications may run on newer versions of Windows using an executable-specific setting called "Compatibility Mode".[30]

An API differs from anapplication binary interface(ABI) in that an API is source code based while an ABI isbinarybased. For instance,POSIXprovides APIs while theLinux Standard Baseprovides an ABI.[31][32]

Remote APIs

edit

Remote APIs allow developers to manipulate remote resources throughprotocols,specific standards for communication that allow different technologies to work together, regardless of language or platform. For example, the Java Database Connectivity API allows developers to query many different types ofdatabaseswith the same set of functions, while theJava remote method invocationAPI uses the Java Remote Method Protocol to allowinvocationof functions that operate remotely, but appear local to the developer.[33][34]

Therefore, remote APIs are useful in maintaining the object abstraction inobject-oriented programming;amethod call,executed locally on aproxyobject, invokes the corresponding method on the remote object, using the remoting protocol, and acquires the result to be used locally as a return value.

A modification of the proxy object will also result in a corresponding modification of the remote object.[35]

Web APIs

edit
Main article:Web API

Web APIs are the defined interfaces through which interactions happen between an enterprise and applications that use its assets, which also is aService Level Agreement(SLA) to specify the functional provider and expose the service path or URL for its API users. An API approach is an architectural approach that revolves around providing a program interface to a set of services to different applications serving different types of consumers.[36]

When used in the context ofweb development,an API is typically defined as a set of specifications, such asHypertext Transfer Protocol(HTTP) request messages, along with a definition of the structure of response messages, usually in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format. An example might be a shipping company API that can be added to an eCommerce-focused website to facilitate ordering shipping services and automatically include current shipping rates, without the site developer having to enter the shipper's rate table into a web database. While "web API" historically has been virtually synonymous withweb service,the recent trend (so-calledWeb 2.0) has been moving away from Simple Object Access Protocol (SOAP) based web services andservice-oriented architecture(SOA) towards more directrepresentational state transfer(REST) styleweb resourcesandresource-oriented architecture(ROA).[37]Part of this trend is related to theSemantic Webmovement towardResource Description Framework(RDF), a concept to promote web-basedontology engineeringtechnologies. Web APIs allow the combination of multiple APIs into new applications known asmashups.[38] In the social media space, web APIs have allowed web communities to facilitate sharing content and data between communities and applications. In this way, content that is created in one place dynamically can be posted and updated to multiple locations on the web.[39]For example, Twitter's REST API allows developers to access core Twitter data and the Search API provides methods for developers to interact with Twitter Search and trends data.[40]

Design

edit

The design of an API has significant impact on its usage.[5]The principle ofinformation hidingdescribes the role of programming interfaces as enablingmodular programmingby hiding the implementation details of the modules so that users of modules need not understand the complexities inside the modules.[41]Thus, the design of an API attempts to provide only the tools a user would expect.[5]The design of programming interfaces represents an important part ofsoftware architecture,the organization of a complex piece of software.[42]

Release policies

edit

APIs are one of the more common ways technology companies integrate. Those that provide and use APIs are considered as being members of a business ecosystem.[43]

The main policies for releasing an API are:[44]

  • Private:The API is for internal company use only.
  • Partner:Only specific business partners can use the API. For example,vehicle for hirecompanies such asUberandLyftallow approved third-party developers to directly order rides from within their apps. This allows the companies to exercise quality control by curating which apps have access to the API, and provides them with an additional revenue stream.[45]
  • Public:The API is available for use by the public. For example,Microsoftmakes theWindows APIpublic, andApplereleases its APICocoa,so that software can be written for theirplatforms.Not all public APIs are generally accessible by everybody. For example, Internet service providers like Cloudflare or Voxility, useRESTfulAPIs to allow customers and resellers access to their infrastructure information, DDoS stats, network performance or dashboard controls.[46]Access to such APIs is granted either by “API tokens”, or customer status validations.[47]

Public API implications

edit

An important factor when an API becomes public is its "interface stability". Changes to the API—for example adding new parameters to a function call—could break compatibility with the clients that depend on that API.[48]

When parts of a publicly presented API are subject to change and thus not stable, such parts of a particular API should be documented explicitly as "unstable". For example, in theGoogle Guavalibrary, the parts that are considered unstable, and that might change soon, are marked with theJava annotation@Beta.[49]

A public API can sometimes declare parts of itself asdeprecatedor rescinded. This usually means that part of the API should be considered a candidate for being removed, or modified in a backward incompatible way. Therefore, these changes allow developers to transition away from parts of the API that will be removed or not supported in the future.[50]

Client code may contain innovative or opportunistic usages that were not intended by the API designers. In other words, for a library with a significant user base, when an element becomes part of the public API, it may be used in diverse ways.[51] On February 19, 2020,Akamaipublished their annual “State of the Internet” report, showcasing the growing trend of cybercriminals targeting public API platforms at financial services worldwide. From December 2017 through November 2019, Akamai witnessed 85.42 billion credential violation attacks. About 20%, or 16.55 billion, were against hostnames defined as API endpoints. Of these, 473.5 million have targeted financial services sector organizations.[52]

Documentation

edit

API documentation describes what services an API offers and how to use those services, aiming to cover everything a client would need to know for practical purposes.

Documentation is crucial for the development and maintenance of applications using the API.[53] API documentation is traditionally found in documentation files but can also be found in social media such as blogs, forums, and Q&A websites.[54]

Traditional documentation files are often presented via a documentation system, such as Javadoc or Pydoc, that has a consistent appearance and structure. However, the types of content included in the documentation differs from API to API.[55]

In the interest of clarity, API documentation may include a description of classes and methods in the API as well as "typical usage scenarios, code snippets, design rationales, performance discussions, and contracts", but implementation details of the API services themselves are usually omitted. It can take a number of forms, including instructional documents, tutorials, and reference works. It'll also include a variety of information types, including guides and functionalities.

Restrictions and limitations on how the API can be used are also covered by the documentation. For instance, documentation for an API function could note that its parameters cannot be null, that the function itself is notthread safe.[56]Because API documentation tends to be comprehensive, it is a challenge for writers to keep the documentation updated and for users to read it carefully, potentially yielding bugs.[48]

API documentation can be enriched with metadata information likeJava annotations.This metadata can be used by the compiler, tools, and by therun-timeenvironment to implement custom behaviors or custom handling.[57]

It is possible to generate API documentation in a data-driven manner. By observing many programs that use a given API, it is possible to infer the typical usages, as well the required contracts and directives.[58]Then, templates can be used to generate natural language from the mined data.

edit
Main article:Google LLC v. Oracle America, Inc.

In 2010, Oracle Corporation sued Google for having distributed a new implementation of Java embedded in the Android operating system.[59]Google had not acquired any permission to reproduce the Java API, although permission had been given to the similar OpenJDK project. JudgeWilliam Alsupruled in theOracle v. Googlecase that APIs cannot becopyrightedin the U.S. and that a victory for Oracle would have widely expanded copyright protection to a "functional set of symbols" and allowed the copyrighting of simple software commands:

To accept Oracle's claim would be to allow anyone to copyright one version of code to carry out a system of commands and thereby bar all others from writing its different versions to carry out all or part of the same commands.[60][61]

Alsup's ruling was overturned in 2014 on appeal to theCourt of Appeals for the Federal Circuit,though the question of whether such use of APIs constitutesfair usewas left unresolved.[62][63]

In 2016, following a two-week trial, a jury determined that Google's reimplementation of the Java API constitutedfair use,but Oracle vowed to appeal the decision.[64]Oracle won on its appeal, with the Court of Appeals for the Federal Circuit ruling that Google's use of the APIs did not qualify for fair use.[65]In 2019, Google appealed to theSupreme Court of the United Statesover both the copyrightability and fair use rulings, and the Supreme Court granted review.[66]Due to theCOVID-19 pandemic,the oral hearings in the case were delayed until October 2020.[67]

The case was decided by the Supreme Court in Google's favor.[68]

Examples

edit
Main category:Application programming interfaces

See also

edit

References

edit
  1. ^Reddy, Martin (2011).API Design for C++.Elsevier Science. p. 1.ISBN9780123850041.
  2. ^abLane, Kin (October 10, 2019)."Intro to APIs: History of APIs".Postman.RetrievedSeptember 18,2020.When you hear the acronym "API" or its expanded version "Application Programming Interface," it is almost always in reference to our modern approach, in that we use HTTP to provide access to machine readable data in a JSON or XML format, often simply referred to as "web APIs." APIs have been around almost as long as computing, but modern web APIs began taking shape in the early 2000s.
  3. ^abPedro, Bruno (2024).Building an API Product: Design, Implement, Release, and Maintain API Products that Meet User Needs.Packt Publishing. p. 4.ISBN9781837638536.
  4. ^Biehl, Matthias (2016).RESTful API Design.API-University Press. p. 10.ISBN9781514735169.
  5. ^abcClarke, Steven (2004)."Measuring API Usability".Dr. Dobb's.Retrieved29 July2016.
  6. ^Jin, Brenda; Sahni, Saurabh; Shevat, Amir (2018). "Preface".Designing Web APIs: Building APIs That Developers Love.O'Reilly Media.ISBN9781492026877.
  7. ^Geewax, JJ (2021).API Design Patterns.Manning. p. 6.ISBN9781638350330.
  8. ^Jacobson, Daniel; Brail, Greg; Woods, Dan (2011).APIs: A Strategy Guide.O'Reilly Media. p. 4.ISBN9781449321642.
  9. ^abDatabase architectures – a feasibility workshop(Report). Washington, DC: U.S. Department of Commerce, National Bureau of Standards. April 1981. pp. 45–47.hdl:2027/mdp.39015077587742.LCCN81600004.NBS special publication 500-76.RetrievedSeptember 18,2020.
  10. ^abcdBloch, Joshua(August 8, 2018).A Brief, Opinionated History of the API(Speech). QCon. San Francisco: InfoQ.RetrievedSeptember 18,2020.
  11. ^abCotton, Ira W.; Greatorex, Frank S. (December 1968)."Data structures and techniques for remote computer graphics".AFIPS '68: Proceedings of the December 9–11, 1968, Fall Joint Computer Conference.AFIPS 1968 Fall Joint Computer Conference. Vol. I. San Francisco, California: Association for Computing Machinery. pp. 533–544.doi:10.1145/1476589.1476661.ISBN978-1450378994.OCLC1175621908.
  12. ^"application program interface".Oxford English Dictionary(Online ed.).Oxford University Press.(Subscription orparticipating institution membershiprequired.)
  13. ^Date, C. J.(2019).E. F. Codd and Relational Theory: A Detailed Review and Analysis of Codd's Major Database Writings.Lulu. p. 135.ISBN978-1684705276.
  14. ^Date, C. J.; Codd, E. F. (January 1975)."The relational and network approaches: Comparison of the application programming interfaces".In Randall Rustin (ed.).Proceedings of 1974 ACM-SIGMOD Workshop on Data Description, Access and Control.SIGMOD Workshop 1974. Vol. 2. Ann Arbor, Michigan: Association for Computing Machinery. pp. 83–113.doi:10.1145/800297.811532.ISBN978-1450374187.OCLC1175623233.
  15. ^Carl, Malamud(1990).Analyzing Novell Networks.Van Nostrand Reinhold. p. 294.ISBN978-0442003647.
  16. ^abJin, Brenda; Sahni, Saurabh; Shevat, Amir (2018).Designing Web APIs.O'Reilly Media.ISBN9781492026877.
  17. ^Fielding, Roy (2000).Architectural Styles and the Design of Network-based Software Architectures(PhD).RetrievedSeptember 18,2020.
  18. ^Dotsika, Fefie (August 2010). "Semantic APIs: Scaling up towards the Semantic Web".International Journal of Information Management.30(4): 335–342.doi:10.1016/j.ijinfomgt.2009.12.003.
  19. ^Odersky, Martin; Spoon, Lex; Venners, Bill (10 December 2008)."Combining Scala and Java".artima.Retrieved29 July2016.
  20. ^de Figueiredo, Luiz Henrique;Ierusalimschy, Roberto;Filho, Waldemar Celes (1994)."The design and implementation of a language for extending applications".TeCGraf Grupo de Tecnologia Em Computacao Grafica:273–284.CiteSeerX10.1.1.47.5194.S2CID59833827.Retrieved29 July2016.
  21. ^Sintes, Tony (13 July 2001)."Just what is the Java API anyway?".JavaWorld.Retrieved2020-07-18.
  22. ^Winters, Titus; Tom Manshreck; Hyrum Wright, eds. (2020).Software engineering at Google: lessons learned from programming over time.Sebastopol, CA: O'Reilly Media.ISBN9781492082798.OCLC1144086840.
  23. ^Mastrangelo, Luis; Ponzanelli, Luca; Mocci, Andrea; Lanza, Michele; Hauswirth, Matthias; Nystrom, Nathaniel (2015-10-23). "Use at your own risk: the Java unsafe API in the wild".Proceedings of the 2015 ACM SIGPLAN International Conference on Object-Oriented Programming, Systems, Languages, and Applications.OOPSLA 2015. New York, New York, U.S.: Association for Computing Machinery. pp. 695–710.doi:10.1145/2814270.2814313.ISBN978-1-4503-3689-5.
  24. ^Emery, David."Standards, APIs, Interfaces and Bindings".Acm.org. Archived fromthe originalon 2015-01-16.Retrieved2016-08-08.
  25. ^"F2PY.org".F2PY.org.Retrieved2011-12-18.
  26. ^Fowler, Martin."Inversion Of Control".
  27. ^Fayad, Mohamed."Object-Oriented Application Frameworks".
  28. ^Lewine, Donald A. (1991).POSIX Programmer's Guide.O'Reilly & Associates, Inc. p. 1.ISBN9780937175736.Retrieved2 August2016.
  29. ^West, Joel; Dedrick, Jason (2001)."Open source standardization: the rise of Linux in the network era"(PDF).Knowledge, Technology & Policy.14(2): 88–112.doi:10.1007/PL00022278.Retrieved2 August2016.
  30. ^ Microsoft (October 2001)."Support for Windows XP".Microsoft. p. 4. Archived fromthe originalon 2009-09-26.
  31. ^"LSB Introduction".Linux Foundation. 21 June 2012.Retrieved2015-03-27.
  32. ^Stoughton, Nick (April 2005)."Update on Standards"(PDF).USENIX.Retrieved2009-06-04.
  33. ^Bierhoff, Kevin (23 April 2009)."API Protocol Compliance in Object-Oriented Software"(PDF).CMU Institute for Software Research.Retrieved29 July2016.
  34. ^Wilson, M. Jeff (10 November 2000)."Get smart with proxies and RMI".JavaWorld.Retrieved2020-07-18.
  35. ^Henning, Michi; Vinoski, Steve (1999).Advanced CORBA Programming with C++.Addison-Wesley.ISBN978-0201379273.Retrieved16 June2015.
  36. ^"API-fication"(PDF download).hcltech.August 2014.
  37. ^Benslimane, Djamal; Schahram Dustdar; Amit Sheth (2008)."Services Mashups: The New Generation of Web Applications".IEEE Internet Computing, vol. 12, no. 5.Institute of Electrical and Electronics Engineers. pp. 13–15. Archived fromthe originalon 2011-09-28.Retrieved2019-10-01.
  38. ^ Niccolai, James (2008-04-23),"So What Is an Enterprise Mashup, Anyway?",PC World
  39. ^Parr, Ben (21 May 2009)."The Evolution of the Social Media API".Mashable.Retrieved26 July2016.
  40. ^"GET trends/place".developer.twitter.Retrieved2020-04-30.
  41. ^Parnas, D.L. (1972)."On the Criteria To Be Used in Decomposing Systems into Modules"(PDF).Communications of the ACM.15(12): 1053–1058.doi:10.1145/361598.361623.S2CID53856438.
  42. ^Garlan, David; Shaw, Mary (January 1994)."An Introduction to Software Architecture"(PDF).Advances in Software Engineering and Knowledge Engineering.1.Retrieved8 August2016.
  43. ^de Ternay, Guerric (Oct 10, 2015)."Business Ecosystem: Creating an Economic Moat".BoostCompanies.Retrieved2016-02-01.
  44. ^Boyd, Mark (2014-02-21)."Private, Partner or Public: Which API Strategy Is Best for Business?".ProgrammableWeb.Retrieved2 August2016.
  45. ^Weissbrot, Alison (7 July 2016)."Car Service APIs Are Everywhere, But What's In It For Partner Apps?".AdExchanger.
  46. ^"Cloudflare API v4 Documentation".cloudflare.25 February 2020.Retrieved27 February2020.
  47. ^Liew, Zell (17 January 2018)."Car Service APIs Are Everywhere, But What's In It For Partner Apps".Smashing Magazine.Retrieved27 February2020.
  48. ^abShi, Lin; Zhong, Hao; Xie, Tao; Li, Mingshu (2011).An Empirical Study on Evolution of API Documentation.Lecture Notes in Computer Science. Vol. 6603. International Conference on Fundamental Approaches to Software Engineering. pp. 416–431.doi:10.1007/978-3-642-19811-3_29.ISBN978-3-642-19810-6.Retrieved22 July2016.
  49. ^"guava-libraries – Guava: Google Core Libraries for Java 1.6+ – Google Project Hosting".2014-02-04.Retrieved2014-02-11.
  50. ^Oracle."How and When to Deprecate APIs".Java SE Documentation.Retrieved2 August2016.
  51. ^Mendez, Diego; Baudry, Benoit; Monperrus, Martin (2013)."Empirical evidence of large-scale diversity in API usage of object-oriented software".2013 IEEE 13th International Working Conference on Source Code Analysis and Manipulation (SCAM).pp. 43–52.arXiv:1307.4062.doi:10.1109/SCAM.2013.6648183.ISBN978-1-4673-5739-5.S2CID6890739.
  52. ^Takanashi, Dean (19 February 2020)."Akamai: Cybercriminals are attacking APIs at financial services firms".Venture Beat.Retrieved27 February2020.
  53. ^Dekel, Uri; Herbsleb, James D. (May 2009). "Improving API Documentation Usability with Knowledge Pushing".Institute for Software Research, School of Computer Science.CiteSeerX10.1.1.446.4214.
  54. ^Parnin, Chris; Treude, Cristoph (May 2011)."Measuring API documentation on the web".Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering.pp. 25–30.doi:10.1145/1984701.1984706.ISBN9781450305952.S2CID17751901.Retrieved22 July2016.{{cite book}}:|journal=ignored (help)
  55. ^Maalej, Waleed; Robillard, Martin P. (April 2012)."Patterns of Knowledge in API Reference Documentation"(PDF).IEEE Transactions on Software Engineering.Retrieved22 July2016.
  56. ^Monperrus, Martin; Eichberg, Michael; Tekes, Elif; Mezini, Mira (3 December 2011). "What should developers be aware of? An empirical study on the directives of API documentation".Empirical Software Engineering.17(6): 703–737.arXiv:1205.6363.doi:10.1007/s10664-011-9186-4.S2CID8174618.
  57. ^"Annotations".Sun Microsystems.Archived fromthe originalon 2011-09-25.Retrieved2011-09-30..
  58. ^Bruch, Marcel; Mezini, Mira; Monperrus, Martin (2010). "Mining subclassing directives to improve framework reuse".2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010).pp. 141–150.CiteSeerX10.1.1.434.15.doi:10.1109/msr.2010.5463347.ISBN978-1-4244-6802-7.S2CID1026918.
  59. ^"Oracle and the End of Programming As We Know It".DrDobbs. 2012-05-01.Retrieved2012-05-09.
  60. ^"APIs Can't be Copyrighted Says Judge in Oracle Case".TGDaily. 2012-06-01.Retrieved2012-12-06.
  61. ^"Oracle America, Inc. vs. Google Inc"(PDF).Wired.2012-05-31.Retrieved2013-09-22.
  62. ^"Oracle Am., Inc. v. Google Inc., No. 13-1021, Fed. Cir. 2014".
  63. ^Rosenblatt, Seth (May 9, 2014)."Court sides with Oracle over Android in Java patent appeal".CNET.Retrieved2014-05-10.
  64. ^"Google beats Oracle – Android makes" fair use "of Java APIs".Ars Technica.2016-05-26.Retrieved2016-07-28.
  65. ^Decker, Susan (March 27, 2018)."Oracle Wins Revival of Billion-Dollar Case Against Google".Bloomberg Businessweek.RetrievedMarch 27,2018.
  66. ^Lee, Timothy (January 25, 2019)."Google asks Supreme Court to overrule disastrous ruling on API copyrights".Ars Technica.RetrievedFebruary 8,2019.
  67. ^vkimber (2020-09-28)."Google LLC v. Oracle America, Inc".LII / Legal Information Institute.Retrieved2021-03-06.
  68. ^"Supreme Court of the United States, No. 18–956, GOOGLE LLC, PETITIONER v. ORACLE AMERICA, INC"(PDF).April 5, 2021.

Further reading

edit
edit
Retrieved from "https://en.wikipedia.org/w/index.php?title=API&oldid=1252039384"