Jump to content

OpenAPI Specification

From Wikipedia, the free encyclopedia
(Redirected from OpenAPI Initiative)
OpenAPI
OpenAPI Specification
Year started2010 (2010)
First published10 August 2011 (2011-08-10)
Latest version3.1.0
15 February 2021 (2021-02-15)
Websiteopenapis.org

The OpenAPI Specification, previously known as the Swagger Specification, is a specification for a machine-readable interface definition language for describing, producing, consuming and visualizing web services.[1] Originally developed to support the Swagger framework, it became a separate project in 2015, overseen by the OpenAPI Initiative, an open-source collaboration project of the Linux Foundation.[2][3]

An OpenAPI Description (OAD)[4] represents a formal description of an API that tools can use to generate code, documentation, test cases, and more.

History

[edit]

Swagger development began in early 2010 by Tony Tam, who was working at online dictionary company Wordnik.[5]

In March 2015, SmartBear Software acquired the open-source Swagger API specification from Reverb Technologies, Wordnik's parent company.[6]

In November 2015, SmartBear announced that it was donating the Swagger specification to a new organization called the OpenAPI Initiative, under the sponsorship of the Linux Foundation. Other founding member companies included 3scale, Apigee, Capital One, Google, IBM, Intuit, Microsoft, PayPal, and Restlet.[7][8]

On 1 January 2016, the Swagger specification was renamed the OpenAPI Specification (OAS) and was moved to a new GitHub repository.[9]

In July 2017, the OpenAPI Initiative released version 3.0.0 of its specification.[10]

In February 2021, the OpenAPI Initiative released version 3.1.0.[11] Major changes in OpenAPI Specification 3.1.0 include JSON schema vocabularies alignment, new top-level elements for describing webhooks that are registered and managed out of band, support for identifying API licenses using the standard SPDX identifier, allowance of descriptions alongside the use of schema references and a change to make the PathItems object optional to simplify creation of reusable libraries of components.[12][13][14]

Consolidation of Formats

[edit]

Two somewhat similar technologies, MuleSoft's RESTful API Modeling Language (RAML) and Apiary's API Blueprint, had been developed around the same time as what was then still called the Swagger Specification.

The producers of both formats later joined the OpenAPI Initiative: Apiary in 2016[15] and MuleSoft in 2017.[16] Both have added support for the OAS.[17][16]

Release dates

[edit]
Version Date Notes[18]
3.1.0 2021-02-15 Release of the OpenAPI Specification 3.1.0
3.0.3 2020-02-20 Patch release of the OpenAPI Specification 3.0.3
3.0.2 2018-10-08 Patch release of the OpenAPI Specification 3.0.2
3.0.1 2017-12-06 Patch release of the OpenAPI Specification 3.0.1
3.0.0 2017-07-26 Release of the OpenAPI Specification 3.0.0
2.0 2014-09-08 Release of Swagger 2.0
1.2 2014-03-14 Initial release of the formal document
1.1 2012-08-22 Release of Swagger 1.1
1.0 2011-08-10 First release of the Swagger Specification

Usage

[edit]

The OAS describes the format for OpenAPI Descriptions (OADs),[4] which can be used by a variety of applications, libraries, and tools.

Applications can use OADs to automatically generate documentation of methods, parameters and data models. This helps keep the documentation, client libraries and source code in sync.[19]

When an OAD is used to generate source code stubs for servers, the process is called scaffolding.

Relationships to software engineering practices

[edit]

The paradigm of agreeing on an API contract first and then programming business logic afterwards, in contrast to coding the program first and then writing a retrospective description of its behavior as the contract, is called contract-first development. Since the interface is determined before any code is written, downstream developers can mock the server behavior and start testing right away.[20] In this sense, contract-first development is also a practice of shift-left testing.

Features

[edit]

The OpenAPI Specification is language-agnostic. With OpenAPI's declarative resource specification, clients can understand and consume services without knowledge of server implementation or access to the server code.[1]

Tools that work with OpenAPI

[edit]

The OpenAPI Initiative maintains a list of implementations for version 3.0 of the specification.[21]

Annual conference

[edit]

The OpenAPI Initiative sponsors an annual API Specifications Conference (ASC). The event has its origins in the API Strategy and Practice Conference (APIStrat) that ran for many years and became part of the OpenAPI Initiative in 2016.

See also

[edit]

References

[edit]
  1. ^ a b "OpenAPI Documentation: Getting Started". Learn OpenAPI. The OpenAPI Initiative. Retrieved 17 September 2024.
  2. ^ "New Collaborative Project to Extend Swagger Specification for Building Connected Applications and Services". Archived from the original on 31 October 2023.
  3. ^ "OpenAPI Initiative Charter". OpenAPI Initiative. Retrieved 12 November 2019.
  4. ^ a b "OpenAPI Documentation: Glossary". Learn OpenAPI. The OpenAPI Initiative. 2023. Retrieved 17 September 2024.
  5. ^ "Swagger creator joins SmartBear". Retrieved 6 August 2019.
  6. ^ "SmartBear Assumes Sponsorship of Swagger API Open Source Project". SmartBear. Retrieved 25 March 2015.
  7. ^ "FAQ". OpenAPI Initiative. Retrieved 12 November 2019.
  8. ^ "New Collaborative Project to Extend Swagger Specification for Building Connected Applications and Services". linuxfoundation.org. Archived from the original on 27 April 2016. Retrieved 22 April 2016.
  9. ^ OpenAPI Initiative. "OpenAPI Specification". GitHub. Retrieved 12 November 2019.
  10. ^ "The OAI Announces the OpenAPI Specification 3.0.0". OpenAPIs. 26 July 2017. Retrieved 19 April 2018.
  11. ^ "OpenAPI Specification 3.1.0 Available Now". Linux.com. 26 April 2021. Retrieved 26 April 2021.
  12. ^ Charboneau, Tyler (7 April 2021). "What's New in OpenAPI 3.1.0?". Nordic APIs. Retrieved 7 April 2021.
  13. ^ "OpenAPI Specification 3.1.0 Released". OpenAPI Initiative. 18 February 2021. Retrieved 18 February 2021.
  14. ^ Sturgeon, Phil (16 February 2021). "Migrating from OpenAPI 3.0 to 3.1.0". OpenAPI Initiative. Retrieved 16 February 2021.
  15. ^ Lensmar, Ole (23 February 2016). "OAI Update – new members, OpenAPI Spec 3.0 progress, and more!". The OpenAPI Initiative. Retrieved 13 October 2024.
  16. ^ a b Avram, Abel (6 May 2017). "The HTTP API space is Consolidating around OAS". InfoQ. Retrieved 14 May 2017.
  17. ^ Nesetril, Jakub (18 January 2016). "We've got Swagger". Oracle Apiary. Retrieved 13 October 2024.
  18. ^ "OpenAPI Specification Version 3.1.0". GitHub. Retrieved 7 November 2023.
  19. ^ "OpenAPI Documentation: Introduction". Learn OpenAPI. The OpenAPI Initiative. 2023. Retrieved 17 September 2024.
  20. ^ Preibisch, Sascha (2018). API Development: A Practical Guide for Business Implementation Success. [Berkeley, CA]: Apress. ISBN 978-1-4842-4140-0. OCLC 1076234393. Having the Swagger (or for that matter, any other machine-readable) document available, team members can start working on their part of the project at the same time.
  21. ^ "OpenAPI Tooling". OpenAPI Tooling. The OpenAPI Initiative. Retrieved 17 September 2024.

Bibliography

[edit]
[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=OpenAPI_Specification&oldid=1251028241"