From f961bfa0d7c16ad681d6aa7ef41b68b6bcd67cfb Mon Sep 17 00:00:00 2001 From: Karen Etheridge Date: Sun, 6 Sep 2026 19:49:25 -0700 Subject: [PATCH] warn that multiple document logic may change tags, servers and securitySchemes really ought to resolve to the referring document, not the entry document, for consistency when creating different combinations of documents in an OAD; we may clarify or fix this in 3.3 --- src/oas.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/oas.md b/src/oas.md index 1d400236f4..bfd0fb878a 100644 --- a/src/oas.md +++ b/src/oas.md @@ -176,6 +176,8 @@ In some cases, an unambiguous URI-based alternative is available, and OAD author For resolving [Components Object](#components-object) and [Tag Object](#tag-object) names from a referenced (non-entry) document, it is RECOMMENDED that tools resolve from the entry document, rather than the current document. For resolving an [Operation Object](#operation-object) based on an `operationId`, it is RECOMMENDED to consider all Operation Objects from all parsed documents. +These recommendations may be revisited in a subsequent version of the specification. + Note that no aspect of implicit connection resolution changes how [URIs are resolved](#relative-references-in-api-description-uris), or restricts their possible targets. See [Appendix G: Parsing and Resolution Guidance](#appendix-g-parsing-and-resolution-guidance) for more details, including a list of Objects and fields using implicit connections.