added explanation, fixes for
MODIFY
versions/3.0.md
versions/3.0.md
@@ -1867,17 +1867,19 @@ The `Link Object` is responsible for defining a possible operation based on a si
Field Name | Type | Description
---|:---:|---
-href | `string` | a relative or absolute URL to a linked resource. This field is mutually exclusive with the `operationId` field.
+operationRef | `string` | a relative or reference to an OAS operation. This field is mutually exclusive with the `operationId` field.
operationId | `string` | the name of an _existing_, resolvable OAS operation, as defined with a unique `operationId`. This field is mutually exclusive with the `href` field. Relative `href` values MAY be used to locate an existing [Operation Object](#operationObject) in the OAS.
parameters | [Link Parameters Object](#linkParametersObject) | an object representing parameters to pass to an operation as specified with `operationId` or identified via `href`.
headers | [Headers Object](#headersObject) | an object representing headers to pass to the linked resource. Where conflicts occur between these headers, and those defined in the related operation, these headers override.
description | `string` | a description of the link, supports [CommonMark syntax](http://spec.commonmark.org/).
+server | [Server Object](#serverObject) | a server object to be used by the target operation
This object can be extended with [Specification Extensions](#specificationExtensions).
-Locating a linked resource MAY be performed by either a `href` or `operationId`.
+Locating a linked resource MAY be performed by either a `operationRef` or `operationId`.
In the case of an `operationId`, it MUST be unique and resolved in the scope of the OAS document.
-Because of the potential for name clashes, consider the `href` syntax as the preferred method for specifications with external references.
+Because of the potential for name clashes, consider the `operationRef` syntax as the preferred
+method for specifications with external references.
##### <a name="responsePayload"></a>Response Payload Values

added explanation, fixes for #1039