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

Web of Things (WoT) Thing Description 1.1 2021-01-26 > 2021-04-15 #21

Open
sebastiankb opened this issue Jan 26, 2022 · 8 comments
Open
Labels
LC Working Draft approaching Candidate Recommendation REVIEW REQUESTED

Comments

@sebastiankb
Copy link

sebastiankb commented Jan 26, 2022

Other comments:
Currently the 2nd WD document is being prepared for publication. When this is done, I will update the link. Until then, the current editorial draft can be used for review.

Many thanks :-)

@sebastiankb sebastiankb added LC Working Draft approaching Candidate Recommendation pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED labels Jan 26, 2022
@sebastiankb sebastiankb changed the title Document_name 2021-01-26 > 2021-03-15 Web of Things (WoT) Thing Description 1.1 2021-01-26 > 2021-03-15 Jan 26, 2022
@michael-n-cooper michael-n-cooper removed the pending This issue needs to get a reviewer assigned to it label Feb 16, 2022
@michael-n-cooper
Copy link
Member

michael-n-cooper commented Mar 23, 2022

@sebastiankb sebastiankb changed the title Web of Things (WoT) Thing Description 1.1 2021-01-26 > 2021-03-15 Web of Things (WoT) Thing Description 1.1 2021-01-26 > 2021-04-15 Mar 30, 2022
@sebastiankb
Copy link
Author

May I ask about the status of the review? We saw there is a new entry at this wiki page. Would be great to get a rough idea when you would start the review. Many thanks

@michael-n-cooper
Copy link
Member

@sebastiankb I checked in APA today, it overlaps with other actions we had open and the plan is to circle back next Wednesday. I'll keep it on my pressure list with them.

@sebastiankb
Copy link
Author

@michael-n-cooper thanks for sharing the status.

@michael-n-cooper
Copy link
Member

APA discussed this today; there is a question that might lead to a comment, but the question isn't worded yet :P I'll keep pushing them.

@michael-n-cooper
Copy link
Member

The question reference above was sent last week, though not to WoT lists, let me know if it should be forwarded.

https://lists.w3.org/Archives/Public/public-apa/2022Apr/0032.html

@sebastiankb
Copy link
Author

Please note that I have updated the issue with a link to the results of the self-review for all Web of Things (WoT) deliverables which also involve Thing Description 1.1..

@mmccool
Copy link

mmccool commented May 12, 2022

We did discuss the question in the above email (which is about integration with voice assistants) and this was in the back of my mind during some of the updates to the accessibility questionnaire answers. However, there was no specific question about voice assistant integration in the questionnaire. What we probably should do is address this with some use cases in our Use Cases and Requirements document and consider how to support voice integration better in some future deliverables. I responded to the email and am copying my response below (I did update my mention of a specific voice assistant to a category since they all kind of work the same):

I looked into [voice assistant] integrations a while ago and my understanding is that some code needs to be written and uploaded to a [voice assistant] service to integrate [a voice assistant] with a cloud service supporting an IoT device for it to work. WoT TDs expose a standardized interface so in theory some “middleware” code could be written to allow ANY IoT device described with a WoT TD (aka Thing) to be integrated into [a voice assistant], and WoT Discovery allows TDs to be accessed via search mechanisms (which [voice assistant] middleware could, in theory, also support). However, we have not written up this use case or prototyped it, and doing it “properly” would involve some work, and it needs for the IoT device to be visible on the public internet (local connections alone are not sufficient; and there are security implications to making them visible on the internet); but it is possible. We should probably explore what it would take to do this in our next charter, and see if there are any gaps we need to fill (such as metadata in TDs supporting voice interactions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LC Working Draft approaching Candidate Recommendation REVIEW REQUESTED
Projects
None yet
Development

No branches or pull requests

3 participants