OpenAPI-Specification
OpenAPI-Specification copied to clipboard
OAI
Community (TDC) Meeting Agenda backlog
@OAI/tsc please add items here for future discussion.
| Topic | Owner | Date Discussed/Issues/PRs - recording link |
|---|---|---|
| Presentation on SLA4OAI work | @pjmolina | 2021-02-25 |
links, backlinks and requestBody properties #1594 |
@mkistler / @luckybroman5 | 2021-03-04 |
overlays |
@darrelmiller / @MikeRalphson | 2021-04-01 / 2021-04-22 |
| "Housekeeping" of existing issues | @webron | 2021-04-15 |
| Codegen vocabulary #2542 | @mkistler | 2021-04-22 |
| Big list of post 3.1 possibilities | @earth2marsh | 2021-05-13 |
discriminator deprecate or improve? |
@Relequestual / @philsturgeon | 2021-05-20 |
format and extension registry |
@MikeRalphson | 2021-05-27 |
| Diversity & Inclusion training | @ncaidin | 2021-06-10 |
| Discriminator improvements and bundling | TDC | 2021-06-17 |
$ref in pathItem Objects |
@char0n | 2021-07-08 |
| Optional and multi-segment path parameters | @darrelmiller | 2021-07-15 |
| SIG reports and milestone review | @darrelmiller | 2021-07-22 |
discriminator next steps |
@OAI/tsc | 2021-07-29 |
| SIG updates, schema PR reviews | @OAI/tsc | 2021-08-19 |
Wider TDC, please comment below with items you'd like us to cover on future TDC calls.
@MikeRalphson Simply put, that was an amazing presentation. Things were very well thought out, and the feedback was unimaginably intelligent.
For the item you have listed for me and @mkistler above, what sort of preparation work might I do to have a similar conversation around that improvement?
Thank you kindly,
We're not always that focussed, i.e. with a presentation, but any examples you might want to put together of link improvements either as new syntax or a proposal/extension would be welcome. It's always good to have something concrete to look at. Sorry we didn't get to introductions this week, we normally give new attendees a bit of floor space at the top of the meetings.
@MikeRalphson No problem, I was just glad to listen in. I will work on preparing something such that when the time comes and there is availability we'll be ready.
@luckybroman5 There is a formal "proposal process" that the TSC put together a while back. I don't see it described in the repo but the basic idea is to create a proposal from this template:
https://github.com/OAI/OpenAPI-Specification/blob/master/proposals/000_OAS-proposal-template.md
The idea is to use the proposal process to get general consensus a feature change before trying to put together a PR to spec itself. I think this is probably the path we should take with improvements to links.
Thanks @mkistler, I am working on putting something together now and will post here when complete, unless you all ready have something?
I had the best intentions to start on this but life got in the way, so I'll gladly yield to you to get things rolling.
@MikeRalphson Simply put, that was an amazing presentation
bummer, I missed it -- was it recorded?
bummer, I missed it -- was it recorded?
Sorry it's not obvious, see the dated link above or in last week's agenda issue.
@mkistler It took me some time, but here is my proposal. Any feedback is welcomed from anyone willing to give it.
@MikeRalphson I'm planning on attending the TSC meeting tomorrow, however it's very understandable if it's too late to get this into this week's agenda. When there is time and if desired, I'm happy to go over the proposal whenever the TSC deems fit.
@luckybroman5 Thanks. This looks like a great "strawman" to get the discussion started. I do have some feedback and will try to organize my thoughts for today's meeting or, if we don't get to it today, will give feedback directly.
Let's devote the next meeting to discussing what might be radically different (or not) in v4! Here's a repo called Moonwalk that serves as a starting point.
@luckybroman5 There is a formal "proposal process" that the TSC put together a while back. I don't see it described in the repo but the basic idea is to create a proposal from this template:
https://github.com/OAI/OpenAPI-Specification/blob/master/proposals/000_OAS-proposal-template.md
The idea is to use the proposal process to get general consensus a feature change before trying to put together a PR to spec itself. I think this is probably the path we should take with improvements to links.
@MikeRalphson , @Relequestual , @philsturgeon
in this one there is the mentionned of discriminator , is there any clarification toward the statement
discriminator deprecate or improve?
my personal opinion this should be fully dropped , and push to a json schema concern it would be even cleanner to have data modeling in JSon Schema (we could even have think about XSD! ) and keep OAS specification to Path / Body / header and so on
this would have also avoid the issue about XML mapping than none of the linter / gateway support (Redocly / Spectral / Vaccum etc)
https://github.com/Redocly/redocly-cli/issues/1276#issuecomment-1738760467
When there is time, can we discuss this issue?
Proposal: Create new repo for openapi tests, similar to json schema test suite
https://github.com/OAI/OpenAPI-Specification/issues/3486
Closing this issue since we rarely check it, and it would be better to bring items to the weekly meeting, for whichever week you would most like your suggestion to be discussed.
