I have added a lot of descriptions, the API's themselves, had a go at the scopes and how it splits the sensitive data from not.
@niesink I have modified the entities a bit, mostly to include related entities - e.g. if you ask for a student you should also be able to get their classes and subjects in the same response to save lots of API calls for related data.
I have separated out the sensitive information into a new entity, that is only accessible by a specific API call to really section it off, and avoid having entities where information appears or dissapears based on scopes.
Easiest to read and review via the Stoplight interface; you can view it in this specific branch:
@niesink @EvanderVeen @edwinverwoerd @mcginkel
Easiest to read and review via the Stoplight interface; you can view it in this specific branch:
https://stichtingsem.stoplight.io/docs/sem-technology-prototype/branches/sis-api-definition/reference/sisdata.v1.yaml
Some of my questions I left, so feel free to comment here on them.