Description
Open Community Working Meeting 2021-11-05 - 20:00 UTC
Zoom Meeting link: https://postman.zoom.us/j/82037276001
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items #68 | @Relequestual | |
| Rolled over: Check in on status of #57 | @Relequestual | Follow up with @karenetheridge on if she still plans to create a PR for Community Discussion #57 - Add to agenda for next call |
| Review updates to HyperSchema meta-schemas and merge PR json-schema-org/json-schema-org.github.io#419 | @jdesrosiers | Merged |
| Review and merge PR to update docs to use HTTPS URLs json-schema-org/json-schema-org.github.io#355 | @Relequestual | @jdesrosiers to review |
| Review our application to join the OpenJS Foundation #93 | @Relequestual | No further comments beyond existing review from @jdesrosiers - @Relequestual to review and update |
| Case study questions #95 | @Relequestual | Kevin (@kevinswiber) asked if we have connections at large companies. We have some but could always have more! Kevin said it looks like we have enough to start with. Kevin commented that there is often a lot of attention required to complete case studied and wondered if work could be delegated. Ben mentioned that it feels like the interested organisations are quite keen, but we would re-evlauate delegation if it becomes problematic. We will continue with thecase study questions, but with a primer for each organisation and an invite to discuss over video. Chatting is often useful to help tease out difficult questions |
| What should be on the JSON Schema site home page? #75 | @Relequestual | There were no comments regarding the list of proposed updates to the home page. Jason suggested we should a single "getting started" guide, but agreed that we don't have the time to do that right now. @Relequestual to add an issue |
| Proposed home page update json-schema-org/json-schema-org.github.io#420 and json-schema-org/json-schema-org.github.io#421 | @Relequestual | Jason thought the links to community update (json-schema-org/json-schema-org.github.io#420) looked good. Jason thought that we should re-phrase "twice yearly release cycle" to avoid making it look like we do two major updates a year. Ben noted there is clarification, but agreed that people often don't read details. We agreed to see if this could be re-phrased to make it clearer, such as saying we do one major release a year, and another release which is a patch release. @Relequestual to update PR. Jason noted the "path to standardization" section was out of date. @Relequestual to add an issue to review and update |
AOB?
From @jdesrosiers
- Support for IRI references json-schema-spec#1137 - IRI - Merged!
- Remove bookending requirement for dynamicRef json-schema-spec#1139 - Dynamic reference updates
- Add propertyDependencies keyword json-schema-spec#1143 - propertyDependencies
- Add requireAllExcept keyword json-schema-spec#1144 - requireAllExcept
- Add section on unevaluatedProperties understanding-json-schema#179 - unevaluatedProperties documentation
Notes regarding AOB PRs
json-schema-org/json-schema-spec#1139 - Jason to review the PR and resolve conflicts. Jason wanted to make sure people didn't get suprised by this changed. Ben to raise the profile of this change to make it less suprising. Ben suggested Jason could write a blog article. Jason commented there wouldn't be more to say than is in the issue.
json-schema-org/json-schema-spec#1143 - This would sort of be "discriminator done properly". Greg (in the related issue) didn't have enough power. Ben and Jason felt the simplicity was good and solved the most common problems. Ben noted (as Greg had) that you cannot use non-string values. Ben suggested another structure, however Jason commented that other options were considered and documented in the issue (json-schema-org/json-schema-spec#1082 (comment)). Ben suggested an approach, but it was hard to communicate. @Relequestual to read spec issue json-schema-org/json-schema-spec#1082, feedback, and show an example of his proposed structure.
Action items:
- Follow up with @karenetheridge re The meaning of "additionalProperties" has changed #57 - @Relequestual
- Review Change http links to https for links to json-schema.org in documentation json-schema-org.github.io#355 - @jdesrosiers
- Update PR Add OpenJS Foundation application for JSON Schema #93 based on review - @Relequestual
- Add website issue to unify "getting started" guide - @Relequestual
- Merge Highlight our community and activities json-schema-org.github.io#420 - @Relequestual
- Revise State that we have a release process and what phase we are in json-schema-org.github.io#421 based on feedback - @Relequestual
- Add website issue to review and update "path to standardization" section - @Relequestual
- Review conflicts for Remove bookending requirement for dynamicRef json-schema-spec#1139 - @jdesrosiers
- Promote the change of Remove bookending requirement for dynamicRef json-schema-spec#1139 - @Relequestual
- Read Issue Proposal: Add propertyDependencies keyword (aka discriminator) json-schema-spec#1082 and show example of proposal - @Relequestual
- Review Add requireAllExcept keyword json-schema-spec#1144 - @Relequestual
- Review Add section on unevaluatedProperties understanding-json-schema#179 - @Relequestual
Notes:
Agenda Items rolling over:
- Check in on status of The meaning of "additionalProperties" has changed #57
- Is anyone willing to take ownership over Issues and PRs in the 2020-12 draft-patch milestone?
Recording: Full recording