You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@gregsdennis presented the new spec development process including adding version numbers and a feature lifecycle model to minimize breaking changes. Questions were raised on terminology and next steps.
Feature lifecycle proposal: Greg proposed a detailed feature lifecycle model with stages from concept to removal. @miqui and @benjagm praised the work but sought clarification on applying existing issues and versioning experimental proposals.
Extracting incomplete features: Property dependencies and vocabularies will enter the proposal stage as incomplete features while output formats become a separate specification to improve human readability.
Implementation support requirements: Supporting a release requires all stable features, while experimental support is optional. Documentation must clarify support for proposals and deprecated features may remain required for some time.
Questions: Questions were raised on terminology, stalled proposals, versioning proposals, deprecated feature handling, and incentivizing experimental support. Clarification and discussion of these details will be important.
Next steps for documentation: Benjamin emphasized starting work on documentation for new extensibility features. The existing documentation strategy issue can be used to coordinate improving docs step-by-step based on feedback as the proposals progress.
I would be interested in discussing a topic but I am not sure if I can join due to some travels I am doing that day and that it is a bit late in my time zone. The topic is 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. This is coming from the W3C Web of Things but I really think that it is relatable to others and I want to get as many opinions as possible :)
Open Community Working Meeting 2024-03-18 - 14:00 PT
📺 See Recording
⏪ Go To Previous Meeting
Agenda:
Notes:
@gregsdennis presented the new spec development process including adding version numbers and a feature lifecycle model to minimize breaking changes. Questions were raised on terminology and next steps.
Feature lifecycle proposal: Greg proposed a detailed feature lifecycle model with stages from concept to removal. @miqui and @benjagm praised the work but sought clarification on applying existing issues and versioning experimental proposals.
Extracting incomplete features: Property dependencies and vocabularies will enter the proposal stage as incomplete features while output formats become a separate specification to improve human readability.
Implementation support requirements: Supporting a release requires all stable features, while experimental support is optional. Documentation must clarify support for proposals and deprecated features may remain required for some time.
Questions: Questions were raised on terminology, stalled proposals, versioning proposals, deprecated feature handling, and incentivizing experimental support. Clarification and discussion of these details will be important.
Next steps for documentation: Benjamin emphasized starting work on documentation for new extensibility features. The existing documentation strategy issue can be used to coordinate improving docs step-by-step based on feedback as the proposals progress.
Agenda Items rolling over:
Attendees:
The text was updated successfully, but these errors were encountered: