Removed Links Object
MODIFY
versions/3.0.md
versions/3.0.md
@@ -50,7 +50,6 @@ Additional utilities can also take advantage of the resulting files, such as tes
- [Response Object](#responseObject)
- [Callback Object](#callbackObject)
- [Example Object](#exampleObject)
- - [Links Object](#linksObject)
- [Link Object](#linkObject)
- [Link Parameters Object](#linkParametersObject)
- [Header Object](#headerObject)
@@ -1638,7 +1637,7 @@ Field Name | Type | Description
<a name="responseDescription"></a>description | `string` | **Required.** A short description of the response. [CommonMark syntax](http://spec.commonmark.org/) can be used for rich text representation.
<a name="responseHeaders"></a>headers | Map[`string`, [Header Object](#headerObject) \| [Reference Object](#referenceObject)] | Maps a header name to its definition. Note that [RFC7230](https://tools.ietf.org/html/rfc7230#page-22) states header names are case insensitive. If a response header is defined with the name `"Content-Type"`, it SHALL be ignored.
<a name="responseContentObject"></a>content | [Content Object](#contentObject) | An object containing descriptions of potential response payloads.
-<a name="responseLinks"></a>links | [Links Object](#linksObject) | An object representing operations related to the response payload.
+<a name="responseLinks"></a>links | Map[`string`, [Link Object](#linkObject) \| [Reference Object](#referenceObject)] | A map of operations links that can be followed from the response. The key of the map is a short name for the link, following the naming constraints of the names for [Component Objects](#componentsObject).
This object can be extended with [Specification Extensions](#specificationExtensions).
@@ -1911,22 +1910,16 @@ schemas:
$ref: '#/components/examples/confirmation-success'
```
-#### <a name="linksObject"></a>Links Object
-The links object represents a set of possible design-time links for a response.
+
+#### <a name="linkObject"></a>Link Object
+
+The `Link object` represents a possible design-time link for a response.
The presence of a link does not guarantee the caller's ability to successfully invoke it, rather it provides a known relationship and traversal mechanism between responses and other operations.
As opposed to _dynamic_ links (links provided **in** the response payload), the OAS linking mechanism does not require that link information be provided in a specific response format at runtime.
For computing links, and providing instructions to execute them, [variable substitution](#variableSubstitution) is used for accessing values in a response and using them as values while invoking the linked operation.
-##### Patterned Fields
-Field Pattern | Type | Description
----|:---:|---
-<a name="linksName"></a> {name} | [Link Object](#linkObject) \| [Reference Object](#referenceObject) | A short name for the link, following the naming constraints of the names for [Component Objects](#componentsObject). The link SHALL reference a single Link Object, or a JSON Reference to a single link object.
-
-#### <a name="linkObject"></a>Link Object
-The `Link Object` is responsible for defining a possible operation based on a single response.
-
##### Fixed Fields
Field Name | Type | Description

Removed Links Object