Remove the "from future "compatibility idea

If we want to do this sort of thing it is probably best discussed
separately.

Author: handrews

versions/3.1.1.md

@@ -214,8 +214,8 @@ In this approach, each document is self-contained and resolves components to its
 When resolving an `operationId`, all Path Item Objects from all parsed documents are considered.
 This requires ensuring that all referenced documents have been parsed prior to determining an `operationId` to be unresolvable.
 
-Security Requirement Objects do not support a URI-based mechanism for connecting to Security Scheme Objects, which means that in this approach, they can only connect to Security Schemes within the same document.
-For forward-compatibility with the OAS version 3.2, implementations MAY provide an _opt-in_ configuration setting to support treating Security Requirement Object property names that do not match the component name syntax as URIs for the required Security Scheme Objects.
+**Note:** Currently, Security Requirement Objects do not support a URI-based mechanism for connecting to Security Scheme Objects, which means that in this approach, they can only connect to Security Schemes within the same document.
+This limitation is expected to be addressed in the next minor version of this specification.
 
 ##### OADs With Only One OpenAPI Object