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

incorporating accepted requirements #175

Merged
merged 2 commits into from
Feb 23, 2022
Merged

Conversation

mlagally
Copy link
Contributor

@mlagally mlagally commented Feb 16, 2022

Copy link
Member

@benfrancis benfrancis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content is fine (except for typos and one bad example).

However, as with my feedback on the use cases PR I can't find other examples of W3C specifications with the requirements for the specification included in the specification text itself. I suggest the requirements should be stored in the GitHub repository in a REQUIREMENTS.md file (or a separate Use Cases & Requirements document).

<ul>
<li>Implementation complexity on a thing and consumer, e.g. eliminating the need of RDF processing,
but still permitting semantic annotations.</li>
<li>simplifying thing description to have less variations.</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capital S

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

less -> fewer

<li>Implementation complexity on a thing and consumer, e.g. eliminating the need of RDF processing,
but still permitting semantic annotations.</li>
<li>simplifying thing description to have less variations.</li>
<li>limiting the effort for JSON implementation.</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capital L

Comment on lines +514 to +515
individually only satisfies one profile. For example, a Smart Building may need to use both "home" devices and
"industrial" devices. A gateway consuming TDs should be able to ingest TDs designed for both the home and industrial
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"home" vs. "industrial" devices is a bad example, please remove or change (e.g. to constrained vs. unconstrained).

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

Successfully merging this pull request may close these issues.

2 participants