-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consider renaming links to spans #83
Comments
Agree that |
We've not heard any feedback on this yet and I'm reluctant to make a fundamental change to terminology without further input so I'm going to take this out of the beta milestone for now. |
Span has always been the more apt term from my perspective as 'link' is used in so many different ways in various access technologies. Link layer, link budget, etc. |
Adding back into the beta milestone! |
To avoid clashes with
links
, we've had to choose alternative names for properties that should be calledlinks
in both #75 and #51This issue is to consider whether we should revert to the 'spans' terminology initially suggested by the technical working group.
I'm putting this issue in the beta milestone as I don't think we'll have time to make such a change for the alpha release.
The text was updated successfully, but these errors were encountered: