-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Issues: OAI/OpenAPI-Specification
Open Community (TDC) Meeting, Thursday 20 March 2025
#4429
opened Mar 13, 2025 by
github-actions
bot
Open
11
Open Community (TDC) Meeting, Thursday 27 March 2025
#4473
opened Mar 20, 2025 by
github-actions
bot
Open
11
Open Community (TDC) Meeting, Thursday 03 April 2025
#4508
opened Mar 27, 2025 by
github-actions
bot
Open
1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Support for JOSE (JSON Signature and Encryption) Standards
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
Needs attention
The author has replied and people with triage rights should take action.
security: encryption
Support for encryption in headers, payloads, etc.
security
#1464
opened Jan 25, 2018 by
cyberphone
DRY Specifications via $ref
re-use: ref-everywhere
Requests to support referencing in more / all places
re-use: ref-group-combine
Re-use requests involving grouping components and combining groups
#1462
opened Jan 22, 2018 by
BenjamenMeyer
xml property and root schemas
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
xml
OpenAPI 3.x: Scope of API version in servers definition too course grained?
metadata
tags, info, license, contact, markdown usage, etc.
#1421
opened Nov 30, 2017 by
marwey
Security Requirement Consistency with Server Objects
security: config
The mechanics of severs and structure of security-related objects
security
#1416
opened Nov 20, 2017 by
stevendearborn
Request for API Version Chaining Feature
metadata
tags, info, license, contact, markdown usage, etc.
OAI-scope
versioning
describing versions of APIs/endpoints/operations
#1397
opened Nov 2, 2017 by
dberlind
Scopes for jwt-based security scheme
security: access ctrl
Permissions and controls distinct from authentication
security
#1393
opened Oct 30, 2017 by
muhmud
Components fields name too restrictive?
clarification
requests to clarify, but not change, part of the spec
examples
requests for more or better examples in the specification
#1387
opened Oct 23, 2017 by
PerthCharern
Is it possible to group parameters ?
re-use: ref-group-combine
Re-use requests involving grouping components and combining groups
#1364
opened Oct 4, 2017 by
starinfor
Inconsistency in runtime expression examples for request headers
clarification
requests to clarify, but not change, part of the spec
#1323
opened Aug 17, 2017 by
hkosova
Multiple 'Set-Cookie' headers in one response
headers
param serialization
Issues related to parameter and/or header serialization
JSON-LD
enhancement
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
#1100
opened May 11, 2017 by
niquola
Permit multiple externalDocs
enhancement
metadata
tags, info, license, contact, markdown usage, etc.
re-use: ref-group-combine
Re-use requests involving grouping components and combining groups
readOnly listed on object model level in addition to on fields because $ref overwrites
re-use: traits/merges
Selective or modified re-use
schema-object
Proposal: Having an example for an entire operation in one place (request + response)
example obj/keywords
Issues with the Example Object or exampel(s) keywords
Add optional field to the Operation object to indicate initial version containing the implementation
versioning
describing versions of APIs/endpoints/operations
#833
opened Nov 9, 2016 by
JamesMGreene
Enhanced Operation Deprecation and versioning
versioning
describing versions of APIs/endpoints/operations
Proposal: Support for HTTP compression
headers
http
Supporting HTTP features and interactions
OAI-scope
#738
opened Jul 18, 2016 by
michaelkourlas
Clarification on the purpose of the API license?
clarification
requests to clarify, but not change, part of the spec
editorial
Wording and stylistic issues
review
Ability to define a API-level and method-level timeouts
http
Supporting HTTP features and interactions
OAI-scope
#695
opened May 13, 2016 by
mm-gmbd
Structural improvements: enhance headers handling
headers
re-use: globals/defaults
Default or global components that can be overridden in some way
Make it easier to define link headers
headers
http
Supporting HTTP features and interactions
param serialization
Issues related to parameter and/or header serialization
How to represent XML elements with attributes
media and encoding
Issues regarding media type support and how to encode data (outside of query/path params)
xml
oauth and basic security are allowed to be used together.
clarification
requests to clarify, but not change, part of the spec
security: auth
Authentication including overlap with authorization
security
#620
opened Apr 4, 2016 by
jsdevel
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.