Apply naming constraint across all component definitions

Author: darrelmiller

versions/3.0.md

@@ -331,6 +331,7 @@ This object can be extended with [Specification Extensions](#specificationExtens
 Holds a set of reusable objects for different aspects of the OAS.
 All objects defined within the components object will have no effect on the API unless they are explicitly referenced from properties outside the components object.
 
+
 ##### Fixed Fields
 
 Field Pattern | Type | Description
@@ -343,8 +344,9 @@ Field Pattern | Type | Description
 <a name="linksDefinitionObject"></a> | [Link Definitions Object](#linksDefinitionsObject) | Link definitions to reuse across the specification.
 <a name="callbacksDefinitionObject"></a> | [Callback Definitions Object](#callbacksDefinitionsObject) | Callback definitions to reuse across the specification.
 
-TODO:  All objects that are children of the componentsObject use keys where following characters are legal in the `name`: `a-zA-Z0-9.-_\`.  All other characters, including extended ASCII characters, are not legal in the `definitionsName`.  The name may be used to namespace the definitions--it is the tooling Specification's job to ensure that the namespace is honored.
-
+All the fixed fields declared above are objects that MUST contain keys that only use the following characters: `a-zA-Z0-9.-_\`.
+Where it is necessary to namespace definition names the `.` character SHOULD be used to separate namespace segments of the name.
+This namespacing mechanism is simply a naming convention and this specification defines no special behavior on namespaced identifiers. 
 
 #### <a name="pathsObject"></a>Paths Object
 
@@ -2791,7 +2793,6 @@ These data types can be primitives, arrays or models.
 Field Pattern | Type | Description
 ---|:---:|---
 <a name="definitionsName"></a>{name} | [Schema Object](#schemaObject) | A single definition, mapping a "name" to the schema it defines.
-The following characters are legal in the `definitionsName`: `a-zA-Z0-9.-_\`.  All other characters, including extended ASCII characters, are not legal in the `definitionsName`.  The name may be used to namespace the definitions--it is the tooling Specification's job to ensure that the namespace is honored.
 
 Examples: