Merge pull request #3880 from handrews/disc-backport-304

Backport (3.0.4) of merge resolution from #3846

Author: miqui

versions/3.0.4.md

@@ -163,6 +163,8 @@ When parsing an OAD, JSON or YAML objects are parsed into specific Objects (such
 
 If the same JSON/YAML object is parsed multiple times and the respective contexts require it to be parsed as _different_ Object types, the resulting behavior is _implementation defined_, and MAY be treated as an error if detected.  An example would be referencing an empty Schema Object under `#/components/schemas` where a Path Item Object is expected, as an empty object is valid for both types.  For maximum interoperability, it is RECOMMENDED that OpenAPI Description authors avoid such scenarios.
 
+#### <a name="resolvingImplicitConnections"></a>Resolving Implicit Connections
+
 ### <a name="dataTypes"></a>Data Types
 
 Primitive data types in the OAS are based on the types supported by the [JSON Schema Specification Wright Draft 00](https://tools.ietf.org/html/draft-wright-json-schema-00#section-4.2). 
@@ -2647,7 +2649,7 @@ components:
         ]
       },
       "Cat": {
-        "description": "A representation of a cat. Note that `Cat` will be used as the discriminator value.",
+        "description": "A representation of a cat. Note that `Cat` will be used as the discriminating value.",
         "allOf": [
           {
             "$ref": "#/components/schemas/Pet"
@@ -2674,7 +2676,7 @@ components:
         ]
       },
       "Dog": {
-        "description": "A representation of a dog. Note that `Dog` will be used as the discriminator value.",
+        "description": "A representation of a dog. Note that `Dog` will be used as the discriminating value.",
         "allOf": [
           {
             "$ref": "#/components/schemas/Pet"
@@ -2716,7 +2718,7 @@ components:
       required:
       - name
       - petType
-    Cat:  # "Cat" will be used as the discriminator value
+    Cat:  # "Cat" will be used as the discriminating value
       description: A representation of a cat
       allOf:
       - $ref: '#/components/schemas/Pet'
@@ -2732,7 +2734,7 @@ components:
             - aggressive
         required:
         - huntingSkill
-    Dog:  # "Dog" will be used as the discriminator value
+    Dog:  # "Dog" will be used as the discriminating value
       description: A representation of a dog
       allOf:
       - $ref: '#/components/schemas/Pet'
@@ -2750,12 +2752,14 @@ components:
 
 #### <a name="discriminatorObject"></a>Discriminator Object
 
-When request bodies or response payloads may be one of a number of different schemas, a Discriminator Object can be used to aid in serialization, deserialization, and validation by implicitly or explicitly associating the possible values of a named property with alternative schemas.
+When request bodies or response payloads may be one of a number of different schemas, a Discriminator Object gives a hint about the expected schema of the document.
+This hint can be used to aid in serialization, deserialization, and validation.
+The Discriminator Object does this by implicitly or explicitly associating the possible values of a named property with alternative schemas.
 
 ##### Fixed Fields
 Field Name | Type | Description
 ---|:---:|---
-<a name="propertyName"></a>propertyName | `string` | **REQUIRED**. The name of the property in the payload that will hold the discriminator value.
+<a name="propertyName"></a>propertyName | `string` | **REQUIRED**. The name of the property in the payload that will hold the discriminating value. This property SHOULD be required in the payload schema, as the behavior when the property is absent is undefined.
 <a name="discriminatorMapping"></a> mapping | Map[`string`, `string`] | An object to hold mappings between payload values and schema names or URI references.
 
 ##### Conditions for Using the Discriminator Object
@@ -2779,6 +2783,8 @@ However, the exact nature of such conversions are implementation-defined.
 
 ##### <a name="discriminatorExamples"></a>Examples
 
+For these examples, assume all schemas are in the entry OpenAPI document; for handling of `discriminator` in referenced documents see [Resolving Implicit Connections](#resolvingImplicitConnections).
+
 In OAS 3.0, a response payload MAY be described to be exactly one of any number of types:
 
 ```yaml
@@ -2829,7 +2835,7 @@ MyResponseType:
       monster: https://gigantic-server.com/schemas/Monster/schema.json
 ```
 
-Here the discriminator _value_ of `dog` will map to the schema `#/components/schemas/Dog`, rather than the default (implicit) value of `Dog`.  If the discriminator _value_ does not match an implicit or explicit mapping, no schema can be determined and validation SHOULD fail.
+Here the discriminating value of `dog` will map to the schema `#/components/schemas/Dog`, rather than the default (implicit) value of `#/components/schemas/dog`.  If the discriminating value does not match an implicit or explicit mapping, no schema can be determined and validation SHOULD fail.
 
 When used in conjunction with the `anyOf` construct, the use of the discriminator can avoid ambiguity where multiple schemas may satisfy a single payload.