Unify local communication Terminology #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ibelem
approved these changes
Feb 11, 2024
There was a problem hiding this comment.
Many thanks @backkem for unifing local communication terminology and adding them into the spec.
https://wicg.github.io/local-peer-to-peer/#local-communication
https://wicg.github.io/local-peer-to-peer/#local-communication-medium
https://wicg.github.io/local-peer-to-peer/#communication-medium-topology
LGTM. Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #41. @ibelem please validate that this matches your vision for the nomenclature.
I kept the notion of "nearby" when used in the context of UX. I think it still makes sense in this context as it is less technical and more easy to grasp by an end-user of a user agent.
Preview | Diff