Further alignment of CAMARA-API-access-and-user-consent.md with CAMARA terms and definitions #280
Conversation
This file contains hidden or 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
…onsumer and API provider terms
|
@sebdewet @AxelNennker Please consider approving the PR to merge it and fix #279. |
|
If there are no further comments, I will merge this PR by next week. |
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.
What type of PR is this?
What this PR does / why we need it:
Update
CAMARA-API-access-and-user-consent.mdto achieve further alignment in the use of the terms "API Consumer" and "API Provider" (replacing other potential synonyms used) and to avoid the term "Telco" which has been reported in the past.Changes included:
NOTE: These changes will be only naming/wording changes and no technical information in the specification document is changed
Which issue(s) this PR fixes:
Fixes #279
Special notes for reviewers:
The term "Operator" has not been completely replaced by "API Provider", instead "Operator" is still used as the main and most common use case of "API Provider". In my opinion, trying to remove all references to the term "Operator" makes no sense and would require a much deeper document refactoring that I don't think is necessary.
Changelog input
Additional documentation
N/A