Report TD under well-known URI

[danielpeintner]

see https://w3c.github.io/wot-discovery/#introduction-well-known

following path: /.well-known/wot-thing-description

[egekorkan]

would this return the TD of the servient? From what I understand by the usage of / in the beginning, it means at the root level of the server. Our root-level server is a servient that can host multiple Things. One possibility would be to modify the servient's API to look like a super basic TDD.

Also, does this apply to other protocols other than HTTP and CoAP?

[danielpeintner]

I just copied the information over from WoT Discovery. Having said that, I would assume that the TD is reported for each Thing.

e.g., the TD for the coffee machine is reported under
http://plugfest.thingweb.io:8083/smart-coffee-machine

It could (should?) be also reported under
http://plugfest.thingweb.io:8083/smart-coffee-machine/.well-known/wot-thing-description

Similarly we could report it under other well-known uris like under .well-known/... for CoAP etc.

[maxim-s-barabash]

It could (should?) be also reported under.

https://datatracker.ietf.org/doc/html/rfc8615#appendix-A

Why aren't per-directory well-known locations defined?
Allowing every URI path segment to have a well-known location
(e.g., "/images/.well-known/") would increase the risks of
colliding with a preexisting URI on a site, and generally these
solutions are found not to scale well because they're too
"chatty".

[egekorkan]

Well the problem is that if I need to know smart-coffee-machine relative URL, we lose the discovery function. From my point of view, nothing but the host URL would be needed to known in advance.

Another solution to the ones I have posted above, we can ask the discovery spec to change and allow having list of TDs under the well-known relative URI. In that case, http://plugfest.thingweb.io:8083 would need to be changed by http://plugfest.thingweb.io:8083/.well-known/wot-thing-description and everything else would simply continue working

[relu91]

There are recent updates regarding this point. Possibly the discovery task force will soon publish a clarification about how to handle .well-known also in our use case. Please see w3c/wot-discovery#249. I can volunteer to do a first implementation of the direction taken in w3c/wot-discovery#249

[egekorkan]

Also related #160

[danielpeintner]

BTW, the latest updates in https://w3c.github.io/wot-discovery/#introduction-well-known seem to propose a shorter version

/.well-known/wot