-
Notifications
You must be signed in to change notification settings - Fork 8
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
device categories - initial draft #70
Closed
Closed
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -595,6 +595,32 @@ <h3 id="profile-description-methodology">Methodology</h3> | |
</section> | ||
</section> | ||
|
||
<section id="device-categoriesdevices"> | ||
<h2>Device Categories</h2> | ||
<p> | ||
In a deployment of WoT conforming to the <a href="https://www.w3.org/TR/wot-architecture/#architecture-abstract">WoT Abstract Architecture</a> | ||
we see different device types with typical characteristics. | ||
They range (sorted in the order of footprint and capabilities) | ||
from small embedded <em>node</em> devices to <em>gateways</em> or <em>hubs</em> | ||
to powerful <em>edge</em> devices and <em>cloud</em> servers. | ||
Interoperability between these devices implies that a core set of features and functionalities | ||
is available on <em>all</em> of them. | ||
</p> | ||
|
||
<p>The following device categories describe the footprint and characteristics of typical representants of these classes. | ||
This is used to identify the possible features and use cases for these device classes. | ||
|
||
<ul> | ||
<li>Node - endpoint with typically 64-128 KB of RAM</li> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. node only is unspecific. resource constrained node
I'm not sure about such a range. I would simple say typically KB of RAM |
||
<li>Gateway/Hub - intermediate node, typically a few MB of RAM</li> | ||
<li>Edge - </li> | ||
<li>Cloud - multiple CPUs, virtualisation, large storage</li> | ||
</ul> | ||
|
||
</p> | ||
</section> | ||
|
||
|
||
|
||
<!-- <a>Core Profile</a> --> | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small does not imply resource constrained. Constrained or resource constrained embedded devices (like field devices) is more common.