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

Allow for multiple EWP Hosts per manifest #7

Closed
wrygiel opened this issue Apr 19, 2016 · 7 comments
Closed

Allow for multiple EWP Hosts per manifest #7

wrygiel opened this issue Apr 19, 2016 · 7 comments
Assignees

Comments

@wrygiel
Copy link
Contributor

wrygiel commented Apr 19, 2016

@mikesteez wrote:

each individual HEI in the manifest will have to implement all APIs specified. For Sweden this will be the default case, but is it applicable to all countries?

If I understood you correctly, you're asking about the following scenario:

  • EWP Host H covers institution HEI 1 and HEI 2, and it implements API 1 for both institutions and API 2 for just HEI 1 (but not HEI 2). How to express it in the manifest file?
@wrygiel
Copy link
Contributor Author

wrygiel commented Apr 19, 2016

Currently, it is not possible to express it in a single manifest file. It is possible to express it with two separate manifest files though. In the most extreme case, you would have a separate manifest for each of your APIs (or each of your institutions).

Adding direct references to all such additional manifests would be cumbersome however. I believe we can introduce a new <include> element to the manifest files. The registry would find such references and parse all the manifest files referenced.

What do you think?

@wrygiel
Copy link
Contributor Author

wrygiel commented Apr 19, 2016

but is it applicable to all countries?

BTW, in Poland each HEI will be serving its own manifest file, and all the APIs will be hosted on HEI's servers. So, each HEI will be individually able to "switch EWP on", and all proper APIs will become available. My guess is that some APIs (such as Courses API or Institutions API) will probably be available even before EWP is "switched on" (although the exact behavior depends on @Awerin's implementation, so I'm not sure).

We can postpone adding the <include> for now, but I expect this topic to resurface in a couple of months.

@wrygiel
Copy link
Contributor Author

wrygiel commented Jun 28, 2016

Related to: erasmus-without-paper/ewp-specs-api-echo#3

If we pick A3 architecture, then each HEI will have its own separate API coverage.

@wrygiel wrygiel self-assigned this Jun 29, 2016
@wrygiel wrygiel changed the title How to handle scenarios where coverage of HEIs and APIs differ? Allow to describe multiple EWP Hosts in a single manifest file Feb 11, 2017
@wrygiel wrygiel changed the title Allow to describe multiple EWP Hosts in a single manifest file Allow for multiple EWP Hosts per manifest Feb 11, 2017
@wrygiel
Copy link
Contributor Author

wrygiel commented Dec 4, 2017

Resolved in 58930bc (currently part of draft-v5 branch, not yet merged to stable).

@wrygiel
Copy link
Contributor Author

wrygiel commented Dec 5, 2017

@erasmus-without-paper/all-members, you can review the changes here. The DEV Registry Service is already accepting Manifests in v5 format, so we encourage you to test it (especially SOP).

@wrygiel
Copy link
Contributor Author

wrygiel commented Jan 4, 2018

A month passed, but none of the partners have tested this. I'm not sure if I can release it as stable.

@georgschermann
Copy link

I hope to find the time to merge our manifests into one and test this next week.

@wrygiel wrygiel closed this as completed Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants