Skip to content
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

link example seems confused #4

Open
mcr opened this issue Aug 2, 2022 · 3 comments
Open

link example seems confused #4

mcr opened this issue Aug 2, 2022 · 3 comments

Comments

@mcr
Copy link

mcr commented Aug 2, 2022

  For resources discovered via CoAP's discovery interface,
  a hosting statement is typically provided by the defaults implied by {{?RFC6690}}
  where a link like `</sensor/temp>` is implied to have the relation "hosts" and the anchor `/`,
  such that a statement "coap://hostname hosts coap://hostname/sensor/temp" is implied in the link.

I don't understand this statement. It feels like something is unstated, or maybe there are 6690 stuff I don't get.

@chrysn
Copy link
Member

chrysn commented Aug 2, 2022

Link format has default values for both rel and anchor.

If a resource registers its working resource </sensor/temp>, and in addition a generic statement about proxying (that there is a proxy for </>), then all that is needed to make the connection, i.e., that </sensors/temp>;rel=hosts;anchor="/", are already in place due to these defaults, and never need to be written down.

@mcr
Copy link
Author

mcr commented Aug 2, 2022

It's the "coap://hostname hosts coap://hostname/sensor/temp" that I'm having problems with.

@chrysn
Copy link
Member

chrysn commented Aug 2, 2022

It doesn't have any meaning on its own, it's just something 6690 defined. It evokes all kinds of associations, but really it's just a label associating these with each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants