Open Community Working Meeting 2022-02-04

[Relequestual]

Open Community Working Meeting 2022-02-04 - 20:00 UTC
(The 2022-01-21 did not have suffeciant attendance to conduct business)

Zoom Meeting link: https://postman.zoom.us/j/82093625720

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	@Relequestual	@Relequestual to review json-schema-org/json-schema-spec#1143
Proposal to change both meeting times to 20:00 GMT OR 12:00 PST	@Relequestual @jdesrosiers	Agreed to change to 12 PST
Schemas and other data are public domain (PR / Issue)	@awwright @karenetheridge	Could we stick with the current licences rather than re-licence? - Some concerns over what the current licence/s actually IS. Should be investigated.
Website rebuild and merge?	@Relequestual	We agreed it should be kept simple and use markdown for content as much as feasable. Create an issue to capture requirements and wishes - @Relequestual
Patch Release Milestone PRs json-schema-org/json-schema-spec#1155	@Relequestual @karenetheridge	Re-reviewed, approved, and merged.
2022 Q1 OKRs update and discussion #134	@Relequestual

AOB?

We discussed ietf-wg-httpapi/mediatypes#7

Action items:

• Update Open Community Working Meeting times on GH Discussion - @Relequestual
• ... on website - @Relequestual
• ... and notify on Slack and Twitter - @Relequestual
• Propose we stick with current licence (if we can determine what that is specifically) for main repo source material re explicit licence needed in schema files and all repositories json-schema-spec#1160 - @Relequestual
• Check with OpenJSF about license of meta-schema situation - @Relequestual -explicit licence needed in schema files and all repositories json-schema-spec#1160 (comment)
• Create an issue to capture requirements and wishes for the website rebuild - Done - @Relequestual
• Review and follow up on IETF HTTP-API WG mediatype registration - Done - @jdesrosiers

Notes:

Pre meeting note regarding the website rebuild and merge item:
Our website and content is spread over 3 repos. Wouldn't it be great to move them all in to the same repo and use a modern tech stack?
We have a financial sponsor for the work, and so far one potential candidate to do the work (from our community).
We should compile a wish list.
I want to see if anyone has any comments about what they would like to see, or any other thoughts or considerations to share.
An issue needs to be created to house the work and child issues.

Recording: link

[jdesrosiers]

Additional discussion topics

• IETF media-type registration. Fix: #7. Add jsonschema ietf-wg-httpapi/mediatypes#14
  • To yaml or not to yaml?
  • What to do with "schema" media-type parameter? Remove remaining media-type param references json-schema-spec#1181
• resolve contradictions in the described behaviour of "additionalProperties" and "items" json-schema-spec#1154
• Add propertyDependencies keyword json-schema-spec#1143
• Add requireAllExcept keyword json-schema-spec#1144
• Proposal: Remove initial resolution step for dynamic references json-schema-spec#1140
• Discuss $id, embedded schema, canonical URI topics that have been coming up a lot (Edit from @Relequestual: Partly this issue Remove the notion of "canonical URIs" in favour of boundaried schema resources json-schema-spec#1183)
• Forward compatibility with must-understand keywords #119
• Restructuring Output Formats #63

[karenetheridge]

json-schema-org/json-schema-spec#1155

[benjagm]

Closing this issue as all tasks are completed. Thanks for your contributions!