I integrated the route into the WellKnownController controller and generalized the documentation a bit, covering both /.well-known/wot and /.well-known/core. Let me know if there is anything that should be changed :)
(Using this introduction method for HTTP does not make as much sense as it does for CoAP, since HTTP does not support multicast. However, it is a feature currently at risk in the Discovery specification, therefore I thought it would be nice if there was one (additional) implementation 🙂)
Hi everyone!
This PR adds support for the CoRE Link Format introduction method (see https://w3c.github.io/wot-discovery/#introduction-core-rd-sec), exposing the
/.well-known/wotresource as a single link under/.well-known/core(see RFC 6690).I integrated the route into the
WellKnownControllercontroller and generalized the documentation a bit, covering both/.well-known/wotand/.well-known/core. Let me know if there is anything that should be changed :)(Using this introduction method for HTTP does not make as much sense as it does for CoAP, since HTTP does not support multicast. However, it is a feature currently at risk in the Discovery specification, therefore I thought it would be nice if there was one (additional) implementation 🙂)
(Partially?) resolves #20.