Closed
Description
Open Community Working Meeting 2023-03-20 - 14:00 PT
Agenda: Compiling!
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | [facilitator] | |
| Discussion on how the avoid confusion with the old JSON Schema github org | @jviotti | Reach out to OpenJS to verify the status of trademark, logo and the old org to mitigate any possible risk |
| Having in mind what we know about our docs I think we should apply to Google Season of Docs | @benjagm | Proceed with the application for Google Season of Docs with the purpose of re-architect our docs |
| Open PRs (see below) | @gregsdennis | Feedback and reviews required |
Action items:
- @Relequestual will reach out to the OpenJS Foundation to clarify the legal aspects of Trademark, logo and the old github org.
- Review required for The JSON Schema Charter #325 PR.
- @benjagm to submit the GSoD application.
- @benjagm to open an issue for working the vision of our docs.
Notes:
- We had a great discussion about the current results of the Survey for how to continue supporting unknown keywords and this new alternative. After a lengthy discussion, some participants shared their reservations with this alternative because of the implications for metaschemas and the risk of making them context-dependent.
- @benjagm suggested reaching out to JSON LD looking for alignment on this topic but it seems unnecessary.
- @jviotti Shared his proposal of claiming the control of the old github org to avoid confusion. @Julian suggested getting feedback from OpenJS legal team making sure there are no open risks and everyone agreed as the right thing to do.
- @benjagm shared a proposal to apply to Google Season of Docs as a first step to re-architect our docs. Diastaxis framework was suggested as a great docs framework (@gregsdennis is using it for his project). Everyone agreed on the current problem with our docs, the need to define o common vision and the GSoD application as the best first step in that direction. Aditionally, @gregsdennis suggested openning an issue to work together on the common vision for our docs.
- @gregsdennis shared an update about these PRs and asked for feedback:
- Regarding splitting of outputs, @awwright suggested format it in XML but @gregsdennis suggested as Markdown(the variant used by JSON Path) to make it easy to read.
- @awwright will be in attending IETF 116 in Japan to talk to the HTTP API's working group about the spec he is working on, and for the next 3 weeks most of the interactions will be on Github.
- In the next week, @awwright will provide more feedback on the unknown keywords discussion because it is connected with how to classify keywords issue.
Attendees
| Account |
|---|
| @awwright |
| @gregsdennis |
| @jviotti |
| @Relequestual |
| @benjagm |
| @Julian |