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.
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.