Góðan dag TAG！

I'm requesting a TAG review of:

• Name: Web of Things (WoT) Thing Description
• Specification URL: https://w3c.github.io/wot-thing-description
• Explainer, Requirements Doc, or Example code: https://github.com/w3c/wot-thing-description/blob/TD-TAG-review/explainer/Explainer.md
• Tests: https://w3c.github.io/wot-thing-description/testing/report.html
• Primary contacts: @sebastiankb, @takuki, @mmccool, @vcharpenay

Further details (optional):

• Relevant time constraints or deadlines:

  • TAG review feedback need by April 5th
  • CR transition planned for April 9th
    • last possible date to make June 25 deadline for REC
    • end of WG charter is June 30

• I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here; this assessment is shared with all Web of Things documents.

• I have reviewed the TAG's API Design Principles

You should also know that...

In the Thing Description specification, text and table entries highlighted with a yellow background indicates a feature associated with an at-risk assertion for which insufficient implementation experience exists. When an entire section is at-risk the words "This section is at risk." will be placed at the start of the section and highlighted with a yellow background.

• The WoT Security and Privacy Considerations document provides extra discussion of security with an IoT focus.
• The related WoT Architecture document is being submitted for TAG review at the same time.
• The WoT Binding Templates informative WG note describes an optional WoT building block.
• The WoT Scripting API informative WG note describes an optional WoT building block.

During the TAG review period, we plan to update the test results to reduce the number of at-risk assertions as much as possible before CR submission. The link above refers to the master branch of the repository, not the TAG-review branch.

We'd prefer the TAG provide feedback as (please select one):

• open issues in our Github repo for each point of feedback
• open a single issue in our Github repo for the entire review
• leave review feedback as a comment in this issue and @-notify [github usernames]