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

Baseline - Introduction - feedback #25

Closed
gmuratk opened this issue May 12, 2023 · 2 comments
Closed

Baseline - Introduction - feedback #25

gmuratk opened this issue May 12, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@gmuratk
Copy link
Collaborator

gmuratk commented May 12, 2023

Problem description
Several text edit suggestions on Baseline doc PR #13 Introduction section

Expected action

  1. ‘Operator platform’ may unintentionally refer to GSMAs “Operator Platform Group” and reader implying a specific implementation (i.e. Open Gateway). In alignment with the architectural diagram, we can use “Exposure Gateway” instead.
  2. "This means that an API...” instead we can be specific a “CAMARA API exposed to Capability Consumers.”
  3. “Policy enforcement … access to a (set of) scopes” -- until this part Personal Information is used and there is no linkage to scope. We can help reader if we put ‘Personal Information (PI) resources that are referred to as scope’.

Additional context
n/a

@gmuratk gmuratk added the documentation Improvements or additions to documentation label May 12, 2023
@jpengar
Copy link
Collaborator

jpengar commented May 16, 2023

‘Operator platform’ may unintentionally refer to GSMAs “Operator Platform Group” and reader implying a specific implementation (i.e. Open Gateway). In alignment with the architectural diagram, we can use “Exposure Gateway” instead.

We originally included the term "Operator NaaS Platform" and were asked to change it to "Operator Platform" (#17). We are happy to change it to "Exposure Gateway" or something else, but we should all agree on the right term to move forward.

"This means that an API...” instead we can be specific a “CAMARA API exposed to Capability Consumers.”

Fine, we can review the content of the document to apply this change. Feel free to suggest this kind of specific change directly on the PR itself.

“Policy enforcement … access to a (set of) scopes” -- until this part Personal Information is used and there is no linkage to scope. We can help reader if we put ‘Personal Information (PI) resources that are referred to as scope’.

I don't quite understand your proposal here. The scope refers to resources (i.e. APIs/API operations in the case of the CAMARA use case) that may (or may not) provide access to personal information data. And if so, it is defined in the document as a PI scope that refers to a PI resource (i.e. API/API operation that provides access to personal information data).

In any case, the aim of this first PR is to create a first baseline document that will need to be edited and developed to document the final agreed solution.

@jpengar
Copy link
Collaborator

jpengar commented May 19, 2023

Fixed in #13 commit 4b76135
@gmuratk Please take a look.

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

No branches or pull requests

2 participants