You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/oas.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -215,7 +215,7 @@ This allows Security Scheme Objects and Tag Objects to be defined next to the AP
215
215
The interface approach can also work for Discriminator Objects and Schema Objects, but it is also possible to keep the Discriminator Object's behavior within a single document using the relative URI-reference syntax of `mapping`.
216
216
217
217
There are no URI-based alternatives for the Operation Object's `tags` field.
218
-
This limitation is expected to be addressed in a future release.
218
+
OAD authors are advised to use external solutions such as the OpenAPI Initiative's Overlay Specification to simulate sharing [Tag Objects](#tag-object) across multiple documents.
219
219
220
220
See [Appendix F: Resolving Security Requirements in a Referenced Document](#appendix-f-resolving-security-requirements-in-a-referenced-document) for an example of the possible resolutions, including which one is recommended by this section.
221
221
The behavior for Discrimator Object non-URI mappings and for the Operation Object's `tags` field operate on the same principles.
0 commit comments