You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replaces references to Swagger UI or Swagger CodeGen with more generic descriptions.
Also updates swagger.io URLs in examples to example.com URLs
Signed-off-by: Rob Dolin <[email protected]>
Copy file name to clipboardExpand all lines: versions/3.0.md
+30-30Lines changed: 30 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The OpenAPI Specification (OAS) is a project used to describe and document RESTf
12
12
13
13
14
14
The OpenAPI Specification defines a set of files required to describe such an API.
15
-
These files can then be used by the Swagger-UI project to display the API and Swagger-Codegen to generate clients in various programming languages.
15
+
These files can then be used by documentation generation tools to display the API and code generation tools to generate clients in various programming languages.
16
16
17
17
Additional utilities can also take advantage of the resulting files, such as testing tools.
18
18
@@ -203,7 +203,7 @@ In subsequent versions of the OpenAPI Specification, care will be given such tha
203
203
#### <aname="infoObject"></a>Info Object
204
204
205
205
The object provides metadata about the API.
206
-
The metadata can be used by the clients if needed, and can be presented in the Swagger-UI for convenience.
206
+
The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.
207
207
208
208
##### Fixed Fields
209
209
@@ -223,13 +223,13 @@ This object can be extended with [Specification Extensions](#specificationExtens
223
223
224
224
```json
225
225
{
226
-
"title": "Swagger Sample App",
226
+
"title": "Sample Pet Store App",
227
227
"description": "This is a sample server for a pet store.",
228
-
"termsOfService": "http://swagger.io/terms/",
228
+
"termsOfService": "http://example.com/terms/",
229
229
"contact": {
230
230
"name": "API Support",
231
-
"url": "http://www.swagger.io/support",
232
-
"email": "support@swagger.io"
231
+
"url": "http://www.example.com/support",
232
+
"email": "support@example.com"
233
233
},
234
234
"license": {
235
235
"name": "Apache 2.0",
@@ -240,13 +240,13 @@ This object can be extended with [Specification Extensions](#specificationExtens
240
240
```
241
241
242
242
```yaml
243
-
title: Swagger Sample App
243
+
title: Sample Pet Store App
244
244
description: This is a sample server for a pet store.
@@ -272,15 +272,15 @@ This object can be extended with [Specification Extensions](#specificationExtens
272
272
```json
273
273
{
274
274
"name": "API Support",
275
-
"url": "http://www.swagger.io/support",
276
-
"email": "support@swagger.io"
275
+
"url": "http://www.example.com/support",
276
+
"email": "support@example.com"
277
277
}
278
278
```
279
279
280
280
```yaml
281
281
name: API Support
282
-
url: http://www.swagger.io/support
283
-
email: support@swagger.io
282
+
url: http://www.example.com/support
283
+
email: support@example.com
284
284
```
285
285
286
286
#### <a name="licenseObject"></a>License Object
@@ -576,7 +576,7 @@ Describes a single API operation on a path.
576
576
Field Name | Type | Description
577
577
---|:---:|---
578
578
<a name="operationTags"></a>tags | [`string`] | A list of tags for API documentation control. Tags can be used for logical grouping of operations by resources or any other qualifier.
579
-
<a name="operationSummary"></a>summary | `string` | A short summary of what the operation does. For maximum readability in the swagger-ui, this field SHOULD be less than 120 characters.
579
+
<a name="operationSummary"></a>summary | `string` | A short summary of what the operation does. For maximum readability in editing or documentation generation tools, this field SHOULD be less than 120 characters.
580
580
<a name="operationDescription"></a>description | `string` | A verbose explanation of the operation behavior. [CommonMark syntax](http://spec.commonmark.org/) can be used for rich text representation.
581
581
<a name="operationExternalDocs"></a>externalDocs | [External Documentation Object](#externalDocumentationObject) | Additional external documentation for this operation.
582
582
<a name="operationId"></a>operationId | `string` | Unique string used to identify the operation. The id MUST be unique among all operations described in the API. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is recommended to follow common programming naming conventions.
@@ -717,13 +717,13 @@ This object can be extended with [Specification Extensions](#specificationExtens
0 commit comments