Library design and how it differs from badgekit api client #6
Description
WIP: this is a brain dump, pretty much
Even though this library is modelled on the badgekit-api client, it differs from it in a number of aspects, mostly because the Badgr API seems to be much simpler (and restrictive) than the badgekit api.
So far I don't see a 'Systems' classification in Badgr as it exists in Open Badges. It seems that all a user can do through the API is related to their permissions.
A Context as in badgekit could still be useful, not for the higher systems level, but for lower levels such as issuer/badge. Think about it.
So far I have removed all the code from contexts, filters, and queries.
Models are also something I am avoiding, at least until I really need to introduce them, if ever.
I also don't see Programs as in badgekit.