Looking at the "Proposed database model" I see an "Access Range Table" with oar_key and oar_description.
- The real name is not "Access Range" but "Scope".
- And there is no way we're storing the description of a scope in the database when we already have an i18n system for that.
Considering these points it's becoming clear that the proposed database setup was just blindly created without an understanding of OAuth or the requirements we have of an OAuth implementation. So if nobody minds I'm just going to delete that section of the page till someone actually starts brainstorming an actual OAuth implementation.