-
Notifications
You must be signed in to change notification settings - Fork 63
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
Using the New Use Case Template and Gathering Experience #2039
Comments
Find below a first try to fill out the new use case template. What I missed while filling out the template:
IntroductionAt the moment the TD does not provide a way to indicate whether writing a property returns a value. There are many possible reasons why writing a property may return a value, e.g.,:
Note: There are also scenarios (maybe most of them) were "no" value is returned when writing. Hence, we should not forget about that common use-case. WoT UsageThing Descriptions are used. Technical EnvironmentHTTP, CoAP, Philips HUE, .. ProblemAt the moment the TD specification misses to describe what is "practice" in many environments. ExpectationThe TD should allow do describe what is used/done in practice. Solution ProposalAdd
Other CommentsNone |
Below you can find a potential submission of the form for the use cases described in #757 and #300. Besides the points mentioned by @danielpeintner above, I was also wondering if we should add a form field for implementation experience, e.g., if a submitter has already implemented a proposed feature because they needed it to cover the use case they are describing.
IntroductionAt the moment, TDs require both a The mandatory split into Both changes together can make TDs less verbose and more compact, which not only makes them easier to read but also more efficient when it comes to their size on the wire. WoT UsageTDs are being used. Technical EnvironmentThis use case applies to most protocols, devices, data types, and standards, if not all. Problem
Expectation
Solution ProposalThe potential solution for this problem is two-fold. Make both fields optional in the WoT TD specificationThat would allow for the definition of this minimal TD: {
"@context": "https://www.w3.org/wot/td/next",
"title": "Minimalistic Thing"
} Introduce a way to define
|
From the TD Call 18.09:
|
Updating my user story examples for TPAC based on the above. I thought there were three examples but I'm only seeing two. Am I overlooking one? If so, please point me at it. Anyway, this is how I am writing the requirements user stories for the two I see above:
|
The third one is w3c/wot-usecases#303 Just on the first user story, it is also to show or deliver any information at all to the user application. So far, it is underspecified. |
We can use the text at the of this comment to fill and reply to each issue linked here.
Here is the template to use:
For the issues we have distributed, this template can be too verbose. Think of someone from the outside submitting this as a request.
The text was updated successfully, but these errors were encountered: