-
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
arch-id-correlation
: An identifier in the WoT Thing Description MUST allow for the correlation of multiple TDs representing the same original Thing or ultimately unique physical entity.
#635
Comments
From #625 (comment)...
I personally don't really agree with this assertion because in my opinion, as far as a WoT Consumer is concerned, two different Thing Descriptions hosted at two different URLs for the same physical device should be treated as two separate Web Things. However, the Thing Description specification does define an I do think the term "correlation" in this assertion is a bit ambiguous. Conclusion: ❌ I don't really agree with this assertion, but let's continue the discussion. Suggested action: Remove the assertion. |
It we make it mandatory to be able to correlate IDs, there is a concern about privacy issues. |
I think, the task of the TD is to provide the option for identification when required.
Yes and I think this is the task of an ecosystem which manages the Things and provides potential IDs. This should not be specified by a standard. |
from today's TD call
|
Arch call on 25:11: |
Arch call on 16.12: |
Arch call on 19.5.: |
In the past, we've discussed this in length in w3c/wot-discovery#190. IMO, since Thing.id is the
The only way to let |
@farshidtz |
Please follow the process in #641
The text was updated successfully, but these errors were encountered: