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

Review the Business Layer of the RAM wrt Intermediaries and service providers #246

Open
ssteinbuss opened this issue Mar 14, 2023 · 2 comments
Assignees
Labels
discussion This is open for discussion to solve the issue

Comments

@ssteinbuss
Copy link
Member

Based on the discussion in the working group architecture on 2023-03-14 we need to rediscuss the role model:

  • Service provider is not perfectly clear
  • is a vocabulary provider an intermediary or a service provider?
@ssteinbuss ssteinbuss added the discussion This is open for discussion to solve the issue label Mar 14, 2023
@ssteinbuss
Copy link
Member Author

  • Ahmad Hemid with experience on the topic of the Vocabulary Provider

@vdb-david
Copy link

I do not entirely agree with the above views.
Looking at the definition of "Service Provider" in RAM 3 page 24, I think we are jumping to conclusions here. Imho RAM 4 does not explain that definition clearly enough, or at least leaves too much room for interpretation that could make this role seem redundant.

I also note that the ‘transfer Data’ arrow between ‘Data Provider’ & ‘Service provider’ as shown on RAM 4 Interaction_of_Roles is in the wrong direction. See RAM 3 pg 26.

=> a Service Provider can be considered a Data Provider and a Data Consumer at the same time (e.g., as a Data Consumer, it receives data from a Data Provider, then provides its specific service, and then turns into a Data Provider itself and offers the data in the International Data Spaces).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This is open for discussion to solve the issue
Projects
None yet
Development

No branches or pull requests

3 participants