Update 3.1.0.md

Author: maksyutin

versions/3.1.0.md

@@ -66,7 +66,7 @@ OpenAPI Specification (с англ. — «OpenAPI Спецификация»
 
 <!-- /TOC -->
 
-## Definitions
+## Определения
 
 ##### <a name="oasDocument"></a>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](#pathsObject) field, a [components](#oasComponents) field or a [webhooks](#oasWebhooks) field. An OpenAPI document uses and conforms to the OpenAPI Specification.
@@ -95,21 +95,21 @@ Some examples of possible media type definitions:
   application/vnd.github.v3.diff
   application/vnd.github.v3.patch
 ```
-##### <a name="httpCodes"></a>HTTP Status Codes
+##### <a name="httpCodes"></a>HTTP коды статусов ответа (HTTP Status Codes)
 The HTTP Status Codes are used to indicate the status of the executed operation. 
 The available status codes are defined by [RFC7231](https://tools.ietf.org/html/rfc7231#section-6) and registered status codes are listed in the [IANA Status Code Registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml).
 
-## Specification
+## Спецификация
 
-### Versions
+### Версии
 
 The OpenAPI Specification is versioned using a `major`.`minor`.`patch` versioning scheme. The `major`.`minor` portion of the version string (for example `3.1`) SHALL designate the OAS feature set. *`.patch`* versions address errors in, or provide clarifications to, this document, not the feature set. Tooling which supports OAS 3.1 SHOULD be compatible with all OAS 3.1.\* versions. The patch version SHOULD NOT be considered by tooling, making no distinction between `3.1.0` and `3.1.1` for example.
 
 Occasionally, non-backwards compatible changes may be made in `minor` versions of the OAS where impact is believed to be low relative to the benefit provided.
 
 An OpenAPI document compatible with OAS 3.\*.\* contains a required [`openapi`](#oasVersion) field which designates the version of the OAS that it uses.
 
-### Format
+### Формат
 
 An OpenAPI document that conforms to the OpenAPI Specification is itself a JSON object, which may be represented either in JSON or YAML format.
 
@@ -134,13 +134,13 @@ In order to preserve the ability to round-trip between YAML and JSON formats, YA
 
 **Note:** While APIs may be defined by OpenAPI documents in either YAML or JSON format, the API request and response bodies and other content are not required to be JSON or YAML.
 
-### <a name="documentStructure"></a>Document Structure
+### <a name="documentStructure"></a>Структура документа
 
 An OpenAPI document MAY be made up of a single document or be divided into multiple, connected parts at the discretion of the author. In the latter case, [`Reference Objects`](#referenceObject) and [`Schema Object`](#schemaObject) `$ref` keywords are used.
 
 It is RECOMMENDED that the root OpenAPI document be named: `openapi.json` or `openapi.yaml`.
 
-### <a name="dataTypes"></a>Data Types
+### <a name="dataTypes"></a>Типы данных
 
 Data types in the OAS are based on the types supported by the [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00#section-4.2.1).
 Note that `integer` as a type is also supported and is defined as a JSON number without a fraction or exponent part. 
@@ -173,22 +173,22 @@ If a URI contains a fragment identifier, then the fragment should be resolved pe
 
 Relative references in [`Schema Objects`](#schemaObject), including any that appear as `$id` values, use the nearest parent `$id` as a Base URI, as described by [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00#section-8.2).  If no parent schema contains an `$id`, then the Base URI MUST be determined according to [RFC3986](https://tools.ietf.org/html/rfc3986#section-5.1).
 
-### <a name="relativeReferencesURL"></a>Relative References in URLs
+### <a name="relativeReferencesURL"></a>Относительные ссылки в URL-адресах
 
 Unless specified otherwise, all properties that are URLs MAY be relative references as defined by [RFC3986](https://tools.ietf.org/html/rfc3986#section-4.2).
 Unless specified otherwise, relative references are resolved using the URLs defined in the [`Server Object`](#serverObject) as a Base URL. Note that these themselves MAY be relative to the referring document.
 
-### Schema
+### Схема
 
 In the following description, if a field is not explicitly **REQUIRED** or described with a MUST or SHALL, it can be considered OPTIONAL.
 
-#### <a name="oasObject"></a>OpenAPI Object
+#### <a name="oasObject"></a>OpenAPI Объект
 
 This is the root object of the [OpenAPI document](#oasDocument).
 
-##### Fixed Fields
+##### Фиксированные (зарезервированные) поля
 
-Field Name | Type | Description
+Имя поля | Тип | Описание
 ---|:---:|---
 <a name="oasVersion"></a>openapi | `string` | **REQUIRED**. This string MUST be the [version number](#versions) of the OpenAPI Specification that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling to interpret the OpenAPI document. This is *not* related to the API [`info.version`](#infoVersion) string.
 <a name="oasInfo"></a>info | [Info Object](#infoObject) | **REQUIRED**. Provides metadata about the API. The metadata MAY be used by tooling as required.
@@ -224,7 +224,7 @@ Field Name | Type | Description
 
 This object MAY be extended with [Specification Extensions](#specificationExtensions).
 
-##### Info Object Example
+##### Пример хранения информации о спецификации (Info Object)
 
 ```json
 {
@@ -260,7 +260,7 @@ license:
 version: 1.0.1
 ```
 
-#### <a name="contactObject"></a>Contact Object
+#### <a name="contactObject"></a>Контактная информация (Contact Object)
 
 Contact information for the exposed API.
 
@@ -290,21 +290,21 @@ url: https://www.example.com/support
 email: [email protected]
 ```
 
-#### <a name="licenseObject"></a>License Object
+#### <a name="licenseObject"></a>Информация о лицензии (License Object)
 
 License information for the exposed API.
 
-##### Fixed Fields
+##### Фиксированные (зарезервированные) поля
 
-Field Name | Type | Description
+Имя поля | Тип | Описание
 ---|:---:|---
 <a name="licenseName"></a>name | `string` | **REQUIRED**. The license name used for the API.
 <a name="licenseIdentifier"></a>identifier | `string` | An [SPDX](https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60) license expression for the API. The `identifier` field is mutually exclusive of the `url` field.
 <a name="licenseUrl"></a>url | `string` | A URL to the license used for the API. This MUST be in the form of a URL. The `url` field is mutually exclusive of the `identifier` field.
 
 This object MAY be extended with [Specification Extensions](#specificationExtensions).
 
-##### License Object Example
+##### Пример информация о лицензии (License Object)
 
 ```json
 {
@@ -318,7 +318,7 @@ name: Apache 2.0
 identifier: Apache-2.0
 ```
 
-#### <a name="serverObject"></a>Server Object
+#### <a name="serverObject"></a>Информация о серверах (Server Object)
 
 An object representing a Server.
 
@@ -3447,9 +3447,9 @@ Two examples of this:
 2. The [Path Item Object](#pathItemObject) MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different from hiding the path itself from the [Paths Object](#pathsObject), because the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see.
 
 
-## <a name="revisionHistory"></a>Appendix A: Revision History
+## <a name="revisionHistory"></a>Appendix A: История версий
 
-Version   | Date       | Notes
+Версия   | Дата       | Замечания
 ---       | ---        | ---
 3.1.0     | 2021-02-15 | Release of the OpenAPI Specification 3.1.0 
 3.1.0-rc1 | 2020-10-08 | rc1 of the 3.1 specification