From eb921234af53995c73f9df84e2e67d106aee5d1e Mon Sep 17 00:00:00 2001 From: Mike Ralphson <mike.ralphson@gmail.com> Date: Thu, 18 Oct 2018 16:56:01 +0100 Subject: [PATCH] Note that specification extensions beginning x-oas- are reserved --- versions/3.1.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.1.0.md b/versions/3.1.0.md index 58d354f3fc..d887bf1796 100644 --- 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).