search

w3c / wot-discovery

Repository for WoT discovery discussion
https://w3c.github.io/wot-discovery/
Other
19 stars 17 forks source link

TD Probing upon registration #229

Open egekorkan opened 2 years ago

egekorkan commented 2 years ago

Coming from https://github.com/w3c/wot-testing/issues/189 (also related to https://github.com/w3c/wot-thing-description/issues/1244).

A directory should do validation of the TD document according to the spec however nothing is said whether it should also test the Thing behind the TD. It could be that someone registers nonexisting Thing TDs which would confuse the Consumers of these TDs. I don't see this as a mandatory feature but if a directory tests the Things by probing them upon registration, I would trust this directory more as a consumer. When some directories do that, can they somehow mention this in their TDs? As in, "If you choose to register your TDs in this directory, all of their interactions will be tested by this endpoint".

farshidtz commented 2 years ago

This has similar challenges to polling of TDs by a directory or healthchecks; see #164 and https://github.com/w3c/wot-discovery/issues/18#issuecomment-643405732.

In particular:

egekorkan commented 2 years ago

These are all valid points. I think that this should be an optional feature anyway and only when the directory can invoke the endpoints successfully, it would put test failed or not. If no communication can be established, no need to enrich the TD, which is the current case. For our use case, the directory is in the same network as the devices (which never sleep) and can easily test all of them. The points above are valid but not necessarily blockers in 100% of the cases.