Closed
Description
Open Community Working Meeting 2021-10-01 - 20:00 UTC
Zoom Meeting link: https://postman.zoom.us/j/82037276001
Agenda: Taking suggestions / compiling!
(WIP)
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items #45 | @Relequestual | We tried to get feedback on json-schema-org/json-schema-spec/issues/1120 (HyperSchema meta-schema problems), but had no comments from new individuals. Agreed to proceed as @jdesrosiers sees fit. It's not clear there IS a general consensus to be had, other than it is broken. |
| How was API Specification Conference 2021 JSON Schema Open Discussion? #59 | @jdesrosiers | The most common question was "when will JSON Schema be 'done'?". This is mainly because we still publish to IETF and prefix release versions with "draft". We discussed and agreed we would prefer to self publish and drop the "draft" versioning, as each release we publish is something we consider production worthy. Jason also noted the vocabulary repo didn't include the OpenAPI vocabulary, which we agreed should be added. |
| Final call on PR "Add ADR for Code of Conduct" #41 | @Relequestual | There were no further comments and the PR was merged. |
| The meaning of "additionalProperties" has changed (draft-07 to 2019-09) #57 | @Relequestual / @marksparkza | We agreed that a strict reading of 2019-09 did not align with the intent, and was a bug. We agreed that fixing the bug would be a change, but only one that provides clarification. @karenetheridge suggested that the clarification/change would most likely align with how implementations work, and they likely would be not strictly following as written in 2020-12. @jdesrosiers's implementation handles situation as intended using a different interpretation to that outlined in the issue, so we can justify a clarification change. @jdesrosiers agreed to write up an explanation for how his implementation handles this situation. We did not reach consensus, so we need to revisit this at a future meeting after Jason has provided his write up. |
| Is anyone willing to take ownership over Issues and PRs in the 2020-12 draft-patch milestone? | @Relequestual | @jdesrosiers felt he was already too busy. @karenetheridge saw she was already assigned to one item, and would look to review it. This agenda item will be recurring till resolved. |
AOB?
If you want to discuss any other business not on the agenda, please add comments during the meeting.
If we do not complete the agenda, your discussion item will likely be rolled over to the next call.
Action items:
- Propose solution for JSON Hyper-Schema Needs Schema Version Parity json-schema-spec#1120 - @jdesrosiers
- Create GH Discussion proposing dropping the "draft" version prefix, and self publishing the next release (2020-12 patch, aka 2021-NN) - @Relequestual - Consider self publishing specifications and dropping "draft" prefix #69
- Create a discussion that explains an approach to handling
additionalPropertiesas intended and as per the spec, as interprited by @jdesrosiers in his implementation - @jdesrosiers
Notes: None
Agenda Items rolling over: None
Sticky agenda items:
- Is anyone willing to take ownership over Issues and PRs in the 2020-12 draft-patch milestone? - @Relequestual
Full recording link - Highlights link
(Or use the first link, and click the "highlights" toggle in the bottom left of the video player. There is an issue where the highlights only video does not show the speakers name on the transcript.)