OAI sig-moonwalk Ideas Discussions
Ideas Discussions
Share ideas for new features
-
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Supporting Retry Policy and Timeout configuration for each Operation
API ShapesModeling HTTP interfaces -
You must be logged in to vote Replace or remove discriminator
Data ModelingModeling any kind of data (media, grammar, code, etc.) -
You must be logged in to vote Functional Areas
IRI RetrievalMapping IRIs to URLs and retrieving the located resource Parse / Edit / SerializeReading, manipulating, and writing OADs Data ModelingModeling any kind of data (media, grammar, code, etc.) API ShapesModeling HTTP interfaces DeploymentConnecting shapes, security, and servers SecurityAuthentication, authorization, etc. Organization & MetadataMetadata for organizing, filtering, and displaying the OAD -
You must be logged in to vote Proposal: a consumer-optimized form of OpenAPI descriptions
Parse / Edit / SerializeReading, manipulating, and writing OADs -
You must be logged in to vote Consideration for moving from objects to arrays.
Organization & MetadataMetadata for organizing, filtering, and displaying the OAD -
You must be logged in to vote Open API Path Templating vs WHATWG URL Pattern
Data ModelingModeling any kind of data (media, grammar, code, etc.) API ShapesModeling HTTP interfaces -
You must be logged in to vote Improvements for links in v4
Data ModelingModeling any kind of data (media, grammar, code, etc.) API ShapesModeling HTTP interfaces -
You must be logged in to vote Imports proposal
IRI RetrievalMapping IRIs to URLs and retrieving the located resource Parse / Edit / SerializeReading, manipulating, and writing OADs -
You must be logged in to vote Use cases for OpenAPI
ProcessHow should we create this version of this spec? -
You must be logged in to vote Modularity: Rich text formatting
Parse / Edit / SerializeReading, manipulating, and writing OADs -
You must be logged in to vote Structural improvements: inheritance on paths and its sublevels
API ShapesModeling HTTP interfaces -
You must be logged in to vote Schema/Parameter default value
Data ModelingModeling any kind of data (media, grammar, code, etc.) API ShapesModeling HTTP interfaces -
You must be logged in to vote -
You must be logged in to vote Arithmetic and relational inter-parameter dependencies and readability concerns
Data ModelingModeling any kind of data (media, grammar, code, etc.) -
You must be logged in to vote Support for parameter interdependencies
Data ModelingModeling any kind of data (media, grammar, code, etc.) -
You must be logged in to vote Indicate the signature mechanism for the API
API ShapesModeling HTTP interfaces -
You must be logged in to vote Modeling HTTP fields (headers/trailers) as a starting point for modeling all the things
Data ModelingModeling any kind of data (media, grammar, code, etc.) -
You must be logged in to vote Versioning is not always at the API granularity
DeploymentConnecting shapes, security, and servers -
You must be logged in to vote Add support for newer HTTP versions (2/3)
API ShapesModeling HTTP interfaces -
You must be logged in to vote -
You must be logged in to vote Improve OAuth scope documentation
SecurityAuthentication, authorization, etc. -
You must be logged in to vote Separation of concerns: Auth
DeploymentConnecting shapes, security, and servers SecurityAuthentication, authorization, etc. -
You must be logged in to vote Deprecate security schemes
SecurityAuthentication, authorization, etc.
