Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Process] Not accepting Use Cases if there is no hint of a gap #259

Open
egekorkan opened this issue Jan 17, 2024 · 1 comment
Open

[Process] Not accepting Use Cases if there is no hint of a gap #259

egekorkan opened this issue Jan 17, 2024 · 1 comment

Comments

@egekorkan
Copy link
Contributor

In https://github.com/w3c/wot-usecases/blob/main/Process.md, it is not clear whether we accept any use case, even if the submitter knows that the use case is achievable with the current standard(s). My opinion is that we should not accept the use case in that case since it cannot be used for driving the standardization process. If there is a new way to use WoT that already works with the current standards, that should go into the architecture document, e.g. https://w3c.github.io/wot-architecture/#utilities .

One compromise solution is to move a use case to architecture document if we find no gap in the process.

@egekorkan egekorkan changed the title Not accepting Use Cases if there is no hint of a gap [Process] Not accepting Use Cases if there is no hint of a gap Jan 17, 2024
@chachamimm
Copy link
Collaborator

I don't think no gap is no accepting. So We should need to clarify what "Gap Analysis" is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants