OAS 3.1 - The Big List of Possibilities

• OAS JSON SCHEMA 😃 !!! [Ron,Ron,Ron]
• Mutual Auth Certificate Support #1004 [Mike]
• Overlays [Uri, Jonathan) (POC Issue #1722 [Darrel/Mike]) Separate document that augments another API description
• Reusable groups #445 [Ron] e.g. $ref more than one component
• Alternative Schemas #1443 [Darrel, Ted] (Need community implementations to commit to 3.1)
• Clarify wording around root schemas and read-only/write-only, XML #1435 #1622 #1638 [Ted, Mike, Ron]
• “Scopes” on Security Requirements for schemes other than OAuth2 #1393 #1366
• Optional and Multi-segment Paths #1459 [Darrel, Jeremy] Priority?
• Disambiguating based on query #182 [Jeremy]
• Digital Signatures and Encryption #1464 [Mike] Followup with Isabelle on status
• Extensions in the discriminator object [Mike]

Out of scope for 3.1, but important for future

• Discovery mechanism for security credentials (jwt, apikey, etc) (Pilot?) #451 [Ron]
• Supporting Message Based APIs (Ask for demo from Fran and Uri)

[handrews]

@xiaoxiangmoe OAS 3.1 will support full JSON Schema compatibility, and while JSON Schema does not have a direct analogue of discriminator (for a whole bunch of reasons), it has several features that could be used to build a much better and more flexible discriminator-ish feature. Hopefully with that available, folks will experiment and then we can codify something that fits with JSON Schema more cleanly than the current discriminator and is more flexible.

[philsturgeon]

Can we close this and punt some issues over to 3.2 possibilities?