Skip to content

Commit 9c0b337

Browse files
authored
Merge pull request OAI#1241 from OAI/dm/link-fix
Updated Link Object to ensure OperationRef or OperationId
2 parents 9634623 + dd0f1f2 commit 9c0b337

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versions/3.0.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1971,7 +1971,7 @@ The presence of a link does not guarantee the caller's ability to successfully i
19711971

19721972
Unlike _dynamic_ links (i.e. links provided **in** the response payload), the OAS linking mechanism does not require link information in the runtime response.
19731973

1974-
For computing links, and providing instructions to execute them, a [runtime expression](#runtimeExpression) is used for accessing values in an operation and using them as parameters while invoking the linked operation.
1974+
For computing links, and providing instructions to execute them, a [runtime expression](#runtimeExpression) is used for accessing values in an operation and using them as parameters while invoking the linked operation.
19751975

19761976
##### Fixed Fields
19771977

@@ -1986,7 +1986,7 @@ Field Name | Type | Description
19861986

19871987
This object can be extended with [Specification Extensions](#specificationExtensions).
19881988

1989-
Locating a linked resource MAY be performed by either a `operationRef` or `operationId`.
1989+
A linked operation MUST be identified using either an `operationRef` or `operationId`.
19901990
In the case of an `operationId`, it MUST be unique and resolved in the scope of the OAS document.
19911991
Because of the potential for name clashes, the `operationRef` syntax is preferred
19921992
for specifications with external references.

0 commit comments

Comments
 (0)