Closed wrygiel closed 6 years ago
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?
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.
Related to: https://github.com/erasmus-without-paper/ewp-specs-api-echo/issues/3
If we pick A3 architecture, then each HEI will have its own separate API coverage.
Resolved in 58930bc35856abd1c527fc0243bdc4ff354ec425 (currently part of draft-v5
branch, not yet merged to stable).
@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).
A month passed, but none of the partners have tested this. I'm not sure if I can release it as stable.
I hope to find the time to merge our manifests into one and test this next week.
@mikesteez wrote:
If I understood you correctly, you're asking about the following scenario:
H
covers institutionHEI 1
andHEI 2
, and it implementsAPI 1
for both institutions andAPI 2
for justHEI 1
(but notHEI 2
). How to express it in the manifest file?