From b70b434f61447a01a4f3c14a276d79339f574320 Mon Sep 17 00:00:00 2001 From: lornajane <172607+lornajane@users.noreply.github.com> Date: Thu, 22 Aug 2024 16:16:44 +0000 Subject: [PATCH] Update ReSpec-rendered specification versions Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- oas/latest.html | 5 ++--- oas/v3.0.0.html | 3 +-- oas/v3.0.1.html | 5 ++--- oas/v3.0.2.html | 5 ++--- oas/v3.0.3.html | 3 +-- oas/v3.1.0.html | 5 ++--- 6 files changed, 10 insertions(+), 16 deletions(-) diff --git a/oas/latest.html b/oas/latest.html index 7fd14d1561..356f1f42f9 100644 --- a/oas/latest.html +++ b/oas/latest.html @@ -249,7 +249,6 @@

OpenAPI Specification v3.1.0

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A self-contained or composite resource which defines or describes an API or elements of an API. The OpenAPI document MUST contain at least one paths field, a components field or a webhooks field. An OpenAPI document uses and conforms to the OpenAPI Specification.

@@ -396,7 +395,7 @@

OpenAPI Specification v3.1.0

webhooks Map[string, Path Item Object | Reference Object] ] -The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the callbacks feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An example is available. +The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the callbacks feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An example is available. components @@ -2471,7 +2470,7 @@

OpenAPI Specification v3.1.0

{expression} Path Item Object | Reference Object -A Path Item Object, or a reference to one, used to define a callback request and expected responses. A complete example is available. +A Path Item Object, or a reference to one, used to define a callback request and expected responses. A complete example is available. diff --git a/oas/v3.0.0.html b/oas/v3.0.0.html index c4c686adae..4826a45715 100644 --- a/oas/v3.0.0.html +++ b/oas/v3.0.0.html @@ -234,7 +234,6 @@

OpenAPI Specification v3.0.0

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A document (or set of documents) that defines or describes an API. An OpenAPI definition uses and conforms to the OpenAPI Specification.

@@ -2445,7 +2444,7 @@

OpenAPI Specification v3.0.0

{expression} Path Item Object -A Path Item Object used to define a callback request and expected responses. A complete example is available. +A Path Item Object used to define a callback request and expected responses. A complete example is available. diff --git a/oas/v3.0.1.html b/oas/v3.0.1.html index cc5b076472..3fe674a015 100644 --- a/oas/v3.0.1.html +++ b/oas/v3.0.1.html @@ -174,7 +174,7 @@ "publishISODate": "2017-12-06T00:00:00.000Z", "generatedSubtitle": "06 December 2017" } -
+

OpenAPI Specification v3.0.1

Version 3.0.1

@@ -239,7 +239,6 @@

OpenAPI Specification v3.0.1

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A document (or set of documents) that defines or describes an API. An OpenAPI definition uses and conforms to the OpenAPI Specification.

@@ -2450,7 +2449,7 @@

OpenAPI Specification v3.0.1

{expression} Path Item Object -A Path Item Object used to define a callback request and expected responses. A complete example is available. +A Path Item Object used to define a callback request and expected responses. A complete example is available. diff --git a/oas/v3.0.2.html b/oas/v3.0.2.html index 82a2ec3d7b..75a5c76dc7 100644 --- a/oas/v3.0.2.html +++ b/oas/v3.0.2.html @@ -180,7 +180,7 @@ "publishISODate": "2018-10-08T00:00:00.000Z", "generatedSubtitle": "08 October 2018" } -
+

OpenAPI Specification v3.0.2

Version 3.0.2

@@ -249,7 +249,6 @@

OpenAPI Specification v3.0.2

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A document (or set of documents) that defines or describes an API. An OpenAPI definition uses and conforms to the OpenAPI Specification.

@@ -2469,7 +2468,7 @@

OpenAPI Specification v3.0.2

{expression} Path Item Object -A Path Item Object used to define a callback request and expected responses. A complete example is available. +A Path Item Object used to define a callback request and expected responses. A complete example is available. diff --git a/oas/v3.0.3.html b/oas/v3.0.3.html index f2a55f4bd4..a835171575 100644 --- a/oas/v3.0.3.html +++ b/oas/v3.0.3.html @@ -249,7 +249,6 @@

OpenAPI Specification v3.0.3

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A document (or set of documents) that defines or describes an API. An OpenAPI definition uses and conforms to the OpenAPI Specification.

@@ -2471,7 +2470,7 @@

OpenAPI Specification v3.0.3

{expression} Path Item Object -A Path Item Object used to define a callback request and expected responses. A complete example is available. +A Path Item Object used to define a callback request and expected responses. A complete example is available. diff --git a/oas/v3.1.0.html b/oas/v3.1.0.html index 7fd14d1561..356f1f42f9 100644 --- a/oas/v3.1.0.html +++ b/oas/v3.1.0.html @@ -249,7 +249,6 @@

OpenAPI Specification v3.1.0

2. Introduction

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

-

3. Definitions

3.1 OpenAPI Document

A self-contained or composite resource which defines or describes an API or elements of an API. The OpenAPI document MUST contain at least one paths field, a components field or a webhooks field. An OpenAPI document uses and conforms to the OpenAPI Specification.

@@ -396,7 +395,7 @@

OpenAPI Specification v3.1.0

webhooks Map[string, Path Item Object | Reference Object] ] -The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the callbacks feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An example is available. +The incoming webhooks that MAY be received as part of this API and that the API consumer MAY choose to implement. Closely related to the callbacks feature, this section describes requests initiated other than by an API call, for example by an out of band registration. The key name is a unique string to refer to each webhook, while the (optionally referenced) Path Item Object describes a request that may be initiated by the API provider and the expected responses. An example is available. components @@ -2471,7 +2470,7 @@

OpenAPI Specification v3.1.0

{expression} Path Item Object | Reference Object -A Path Item Object, or a reference to one, used to define a callback request and expected responses. A complete example is available. +A Path Item Object, or a reference to one, used to define a callback request and expected responses. A complete example is available.