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

Compatibility in the ecosystem [TAG feedback] #814

Closed
rhiaro opened this issue Jul 25, 2022 · 3 comments
Closed

Compatibility in the ecosystem [TAG feedback] #814

rhiaro opened this issue Jul 25, 2022 · 3 comments
Labels
answered close tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on.

Comments

@rhiaro
Copy link
Member

rhiaro commented Jul 25, 2022

We can see a lot of work to survey the current (and, presumably, ever-changing) landscape of IoT devices, and the effort to bring fragmented ways of operating together. Can you summarise, or link to a summary of, what the compatibility story looks like in practice? Eg. what widely used devices would be compatible with this architecture out of the box? Or what would needed to be added to make them compatible? What is practically possible with what is out there today, if this suite of specs are published as-is? A few concrete examples would be really nice to help give us a better picture of the ecosystem.

(from w3ctag/design-reviews#736)

@mlagally mlagally added the tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on. label Aug 4, 2022
@mlagally
Copy link
Contributor

mlagally commented Aug 4, 2022

Out of the box interoperability is the primary goal of the Profile specification. We should highlight that in the introduction section and provide more information in the profile section, once the profile specification is finalized.

@mlagally
Copy link
Contributor

mlagally commented Sep 1, 2022

Discussion in Arch call on 1. Sept:
Devices that use HTTP, CoAP or MQTT can be described with a Thing Description (TD).
Given a suitable TD, a consumer can interact with these devices out of the box.
There are other IoT devices that are more challenging, and need extensions beyond that, e.g. OPC-UA devices, but we are working with the OPC foundation to make this possible. This is planned for the next charter.
There are also protocol translators (gateways) for HTTP to other protocol standards, so the number of devices we can interact with is much larger because of this.

@mlagally
Copy link
Contributor

mlagally commented Oct 13, 2022

Arch call on Oct13th:

This kind of information rather belongs to, and is already provided in the explainer document.

Calling out particular devices for the ecosystem does not belong into the architecure document. We have anecdotal evidence of several systems adopting the specification, but putting this evidence as a snapshot of today's adoption would be outdated very quickly.

During the WoT activity we did surveys and created a technical landscape document, did several workshops, did investigations on specific areas and concluded what kind of documents to create.

For examples see:
http://w3c.github.io/wot/tech-landscape/
https://www.w3.org/WoT/IG/wiki/Discovery_Categories_and_Tech_Landscape

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered close tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

3 participants