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

Add new use cases for smart agriculture-Milking #200

Merged
merged 11 commits into from
Jan 10, 2023
Merged

Conversation

mhchoi76
Copy link
Contributor

@mhchoi76 mhchoi76 commented Nov 8, 2022

Propose new use case for automatic milking system for dairy farm


Preview | Diff

- Propose new use case for automatic milking system for dairy farm
Add new use cases for smart agriculture
fixed markup error
@mhchoi76
Copy link
Contributor Author

mhchoi76 commented Nov 8, 2022

This PR is related with issue #195 . @mmccool , @mlagally, Could you review this.

@mhchoi76 mhchoi76 changed the title Add new use cases for smart agriculture Add new use cases for smart agriculture-Milking Nov 8, 2022
This is a new use case related to UAV assisted smart agriculture for pest control.
Add UAV assisted smart agriculture use case
This use case is need to have internal discussion further.
@mhchoi76
Copy link
Contributor Author

@mmccool , @mlagally, @ashimura , Could you review this new use case, smart agriculture-milking?

Modify markup for readability
@mlagally
Copy link
Contributor

mlagally commented Dec 6, 2022

UC call on Dec 6th:
We reviewed the use case description and consider it very relevant for inclusion into the next version of the document.

A few suggestions:

  • security requirement should be elaborated: for example key management on the LAN to support TLS
  • RFID tags are only one example, other options are QR or bar codes
  • gaps: latencies of control systems are also an aspect of motivation for an edge device

Can you please update the draft, we plan to revisit this in the next UC call on December 20th.

The three requests received from @mlagally for updating this document were modified as follows.
o 'Security consideration' section was modified. But, this document deals with an use case, so I think that it is undesirable to include specific technical details for sercurity consideration.
o 'Expected devices' setion and 'Description' section were modified to reflect the 2nd update suggestion from @mlagally.
o 'gap' section was modified to reflect the 3rd updata suggestioin from @mlagally.

And, I received on mote request from @egekorkan to add a section decsribing new Requirement including protocol, content type, platform, and authentication in relation to pull requrest w3c#193. However, this request is currenlty under discussion to improve the WoT use case template. So, I will review it again when the discussion on this is complete.
Uptate the document based on comments from meeting on 20 December.
- Delete nnecessary content such as 'reviewer', 'Tracker Issue ID', and 'Status'.
- Add 2 author names in the section of Acknowledgements.
@mhchoi76
Copy link
Contributor Author

Updated the texts of this use case according to the comments from yesterday meeting.
@mlagally, @mmccool, @ashimura, Could you please check and review this updated use case?

Thank you so much.

@mlagally
Copy link
Contributor

UC call on Jan 10th: Agree to merge

@mlagally mlagally merged commit 69632be into w3c:main Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants