Open Community Working Meeting 2024-03-25 - 14:00 PT

[benjagm]

Open Community Working Meeting 2024-03-25 - 14:00 PT

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
How a specification or standardisation body can manage their resources given to users. Those resources include JSON Schemas among other things like ontologies, examples, test cases. Management means packaging, versioning and serving while maintaining consistency between the resources.	@egekorkan

Action items:

• @benjagm To upload to youtube an edited video of Greg's presentation about the stable release development.
• @benjagm To add to the documentation strategy a release adding docs to explain how to use JSON Schema at scale.

Notes:

Stable release development cycle presentation review
Greg's prior presentation on establishing a stable release cycle for JSON Schema was recapped, with no outstanding action items. Karen had since provided additional feedback and questions on the proposal threads.

Web of Things specification resources discussion
Ege outlined the WOT specification's use of JSON Schema and related artifacts like examples and ontologies, and the challenges of maintaining consistency across releases without tooling. Potential automation solutions were explored.

Versioning schemas and related challenges
Challenges of versioning complex JSON Schemas at scale were discussed. While a stable spec would help, guidelines were needed for practical schema management. Schema versioning best practices require further documentation.

JSON schema registry and conversion challenges
Juan outlined plans for an open source JSON Schema registry and noted conversion limitations between formats. Schema complexity impacts transformations; errors may occur.

Using JSON Schema at scale
Discussants agreed documentation to guide how to use JSON Schema at scale will really beneficial. Miguel offered to create an issue to share his organization's approach to spark guidelines development.

Attendees:

Account
@gregsdennis
@jdesrosiers
@Julian
@miqui
@benjagm
@Relequestual
@jviotti
@egekorkan

[egekorkan]

I will be there today :)

[benjagm]

I will be there today :)

Thanks Ege!

[davinash97]

Greetings! Looking forward to it.

[benjagm]

The documentation strategy has been modified as agreed to add an item to publish a guide on how to use JSON Schema at scale. json-schema-org/website#158

[egekorkan]

I am not sure if this is the best place to share this but here is the W3C WoT Working Group's message regarding the support for stand-alone standardization: w3c/strategy#108 (comment)

[github-actions]

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️

[github-actions]

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️

[github-actions]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the main branch has fixed it. Please, create a new issue if the issue is not fixed.