diff --git a/oas/latest.html b/oas/latest.html index af76b350b1..343b4f94e5 100644 --- a/oas/latest.html +++ b/oas/latest.html @@ -180,7 +180,7 @@ "publishISODate": "2021-02-15T00:00:00.000Z", "generatedSubtitle": "15 February 2021" } -
+

OpenAPI Specification v3.1.0

Version 3.1.0

@@ -1585,7 +1585,7 @@

OpenAPI Specification v3.1.0

string -> "blue" array -> ["blue","black","brown"] - object -> { "R": 100, "G": 200, "B": 150 } + object -> { "R": 100, "G": 200, "B": 150 }

The following table shows examples of rendering differences for each value.

diff --git a/oas/v3.0.0.html b/oas/v3.0.0.html index 970fc697e9..ffb5b305bf 100644 --- a/oas/v3.0.0.html +++ b/oas/v3.0.0.html @@ -1562,7 +1562,7 @@

OpenAPI Specification v3.0.0

string -> "blue" array -> ["blue","black","brown"] - object -> { "R": 100, "G": 200, "B": 150 } + object -> { "R": 100, "G": 200, "B": 150 }

The following table shows examples of rendering differences for each value.

@@ -2765,10 +2765,10 @@

OpenAPI Specification v3.0.0

"query." name path-reference = "path." name body-reference = "body" ["#" fragment] - fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) + fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) name = *( char ) - char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) - token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6) + char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) + token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6)

The name identifier is case-sensitive, whereas token is not.

The table below provides examples of runtime expressions and examples of their use in a value:

@@ -3428,10 +3428,10 @@

OpenAPI Specification v3.0.0

MUST be present in the response payload, and the value will correspond to the name of a schema defined in the OAS document. Thus the response payload:

-
{
-  "id": 12345,
-  "pet_type": "Cat"
-}
+
{
+  "id": 12345,
+  "pet_type": "Cat"
+}
 

 
Will indicate that the Cat schema be used in conjunction with this payload.

 
In scenarios where the value of the discriminator field does not match the schema name or implicit mapping is not possible, an optional mapping definition MAY be used:

@@ -3490,16 +3490,16 @@ 
OpenAPI Specification v3.0.0 
 
{
-  "pet_type": "Cat",
-  "name": "misty"
-}
+
{
+  "pet_type": "Cat",
+  "name": "misty"
+}
 

 
will indicate that the Cat schema be used.  Likewise this schema:

-
{
-  "pet_type": "cachorro",
-  "bark": "soft"
-}
+
{
+  "pet_type": "cachorro",
+  "bark": "soft"
+}
 

 
will map to Dog because of the definition in the mappings element.

 
4.7.27 XML Object

diff --git a/oas/v3.0.1.html b/oas/v3.0.1.html
index ac228c9945..b5c464ac48 100644
--- a/oas/v3.0.1.html
+++ b/oas/v3.0.1.html
@@ -174,7 +174,7 @@
   "publishISODate": "2017-12-06T00:00:00.000Z",
   "generatedSubtitle": "06 December 2017"
 }
-

+

     

     
OpenAPI Specification v3.0.1 
 
Version 3.0.1

@@ -1567,7 +1567,7 @@ 
OpenAPI Specification v3.0.1 
 
   string -> "blue"
    array -> ["blue","black","brown"]
-   object -> { "R": 100, "G": 200, "B": 150 }
+   object -> { "R": 100, "G": 200, "B": 150 }
 

 
The following table shows examples of rendering differences for each value.

@@ -2770,10 +2770,10 @@

OpenAPI Specification v3.0.1

"query." name path-reference = "path." name body-reference = "body" ["#" fragment] - fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) + fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) name = *( char ) - char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) - token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6) + char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) + token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6)

The name identifier is case-sensitive, whereas token is not.

The table below provides examples of runtime expressions and examples of their use in a value:

@@ -3375,10 +3375,10 @@

OpenAPI Specification v3.0.1

MUST be present in the response payload, and the value will correspond to the name of a schema defined in the OAS document. Thus the response payload:

-
{
-  "id": 12345,
-  "pet_type": "Cat"
-}
+
{
+  "id": 12345,
+  "pet_type": "Cat"
+}
 

 
Will indicate that the Cat schema be used in conjunction with this payload.

 
In scenarios where the value of the discriminator field does not match the schema name or implicit mapping is not possible, an optional mapping definition MAY be used:

@@ -3437,16 +3437,16 @@ 
OpenAPI Specification v3.0.1 
 
{
-  "pet_type": "Cat",
-  "name": "misty"
-}
+
{
+  "pet_type": "Cat",
+  "name": "misty"
+}
 

 
will indicate that the Cat schema be used.  Likewise this schema:

-
{
-  "pet_type": "cachorro",
-  "bark": "soft"
-}
+
{
+  "pet_type": "cachorro",
+  "bark": "soft"
+}
 

 
will map to Dog because of the definition in the mappings element.

 
4.7.26 XML Object

diff --git a/oas/v3.0.2.html b/oas/v3.0.2.html
index c1ba3a6137..d23e80bd12 100644
--- a/oas/v3.0.2.html
+++ b/oas/v3.0.2.html
@@ -1586,7 +1586,7 @@ 
OpenAPI Specification v3.0.2 
 
   string -> "blue"
    array -> ["blue","black","brown"]
-   object -> { "R": 100, "G": 200, "B": 150 }
+   object -> { "R": 100, "G": 200, "B": 150 }
 

 
The following table shows examples of rendering differences for each value.

@@ -2788,10 +2788,10 @@

OpenAPI Specification v3.0.2

"query." name path-reference = "path." name body-reference = "body" ["#" fragment] - fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) + fragment = a JSON Pointer [RFC 6901](https://tools.ietf.org/html/rfc6901) name = *( char ) - char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) - token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6) + char = as per RFC [7159](https://tools.ietf.org/html/rfc7159#section-7) + token = as per RFC [7230](https://tools.ietf.org/html/rfc7230#section-3.2.6)

The name identifier is case-sensitive, whereas token is not.

The table below provides examples of runtime expressions and examples of their use in a value:

diff --git a/oas/v3.0.3.html b/oas/v3.0.3.html index 9eefc3fa7e..f5e6ab9ed5 100644 --- a/oas/v3.0.3.html +++ b/oas/v3.0.3.html @@ -180,7 +180,7 @@ "publishISODate": "2020-02-20T00:00:00.000Z", "generatedSubtitle": "20 February 2020" } -
+

OpenAPI Specification v3.0.3

Version 3.0.3

@@ -1588,7 +1588,7 @@

OpenAPI Specification v3.0.3

string -> "blue" array -> ["blue","black","brown"] - object -> { "R": 100, "G": 200, "B": 150 } + object -> { "R": 100, "G": 200, "B": 150 }

The following table shows examples of rendering differences for each value.

diff --git a/oas/v3.1.0.html b/oas/v3.1.0.html index af76b350b1..343b4f94e5 100644 --- a/oas/v3.1.0.html +++ b/oas/v3.1.0.html @@ -180,7 +180,7 @@ "publishISODate": "2021-02-15T00:00:00.000Z", "generatedSubtitle": "15 February 2021" } -
+

OpenAPI Specification v3.1.0

Version 3.1.0

@@ -1585,7 +1585,7 @@

OpenAPI Specification v3.1.0

string -> "blue" array -> ["blue","black","brown"] - object -> { "R": 100, "G": 200, "B": 150 } + object -> { "R": 100, "G": 200, "B": 150 }

The following table shows examples of rendering differences for each value.