From 7f9832d82c20ce1263544cfcfccddc57d34bffa0 Mon Sep 17 00:00:00 2001 From: Mike Ralphson Date: Sat, 22 Feb 2020 10:25:39 +0000 Subject: [PATCH] gh-pages: don't mix https and http content (toc) --- oas/v3.0.3.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/oas/v3.0.3.html b/oas/v3.0.3.html index 42a69bce68..4e4535256c 100644 --- a/oas/v3.0.3.html +++ b/oas/v3.0.3.html @@ -1,4 +1,4 @@ -OpenAPI Specification
The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for REST APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interface descriptions have done for lower-level programming, the OpenAPI Specification removes guesswork in calling a service.

Status of This Document

The source-of-truth for the specification is the GitHub markdown file referenced above.
+OpenAPI Specification
The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for REST APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interface descriptions have done for lower-level programming, the OpenAPI Specification removes guesswork in calling a service.

Status of This Document

The source-of-truth for the specification is the GitHub markdown file referenced above.

OpenAPI Specification

Version 3.0.3

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 [[!RFC2119]] [[!RFC8174]] when, and only when, they appear in all capitals, as shown here.