Merge pull request #1715 from MikeRalphson/specext-oas

Note that specification extensions beginning x-oas- are reserved
OAI · Oct 18, 2018 · 3083f1a · 3083f1a
2 parents 77f86eb + eb92123
commit 3083f1a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/versions/3.1.0.md b/versions/3.1.0.md
@@ -3379,7 +3379,7 @@ The extensions properties are implemented as patterned fields that are always pr
 
 Field Pattern | Type | Description
 ---|:---:|---
-<a name="infoExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. Can have any valid JSON format value.
+<a name="infoExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. Field names beginning `x-oas-` are reserved for uses defined by the [OpenAPI Initiative](https://www.openapis.org/). The value can be `null`, a primitive, an array or an object. Can have any valid JSON format value.
 
 The extensions may or may not be supported by the available tooling, but those may be extended as well to add requested support (if tools are internal or open-sourced).