-
Notifications
You must be signed in to change notification settings - Fork 43
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
Comments
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. |
Discussion in Arch call on 1. Sept: |
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: |
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)
The text was updated successfully, but these errors were encountered: