Closed
Description
Open Community Working Meeting 2022-03-04 - 12:00 PT
Zoom Meeting link: https://postman.zoom.us/meeting/register/tZYtfuqurD4tGNR1mNO01r171rLCylRbDYEu
Agenda:
Topic | Owner | Decision/NextStep |
---|---|---|
Review last call's action items | @Relequestual | |
Website wishlist #154 | @Relequestual | - Agreed it should be simple an performant. - Concern for comment over design. - Should be accessible. |
Mission statement json-schema-org/json-schema-org.github.io#423 | @Relequestual | @jdesrosiers "A declartive domain specific language" Tony Fast "declarative grammar" @Relequestual After discussing with a friend, also considering "grammar and syntax" |
"Clarify things about Canonical URIs" json-schema-org/json-schema-spec#1104 | @Relequestual |
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.
- ambiguous behaviour of additionalProperties when invalid json-schema-spec#1172 - @jdesrosiers
"What are we going to do for the patch release, if anything?" - @jdesrosiers
A partial fix foradditionalProperties
would not also fixunevaluatedProperties
. Having dispartiy would be bad.
"Could we change the language to not mention previous version?" - @Relequestual
"We could say that multiple output results are possible and OK. After all, it's a patch release, and we want to avoid breaking changes" - @jdesrosiers
Action items:
- Make changes to Include mission statement on the home page json-schema-org.github.io#423 based on discussions - @Relequestual
- Reply regarding question over design The website rebuild wishlist! #154 - @Relequestual
- Create new PR for ambiguous behaviour of additionalProperties when invalid json-schema-spec#1172 based on @jdesrosiers suggestion above - Anyone!
Notes:
Agenda Items rolling over:
Recording: link