the current text in section 5.2.2 sounds like even existing error codes invalid_scope, invalid_client etc are defined from scratch by this specification. it would be much cleaner to differentiate which error codes are new and which ones are extending the existing ones. a structure like below:
The error response follows the rules as defined in [RFC6749], with the following additional clarifications:
< clarifications about how error codes that are already defined in other oauth specs are extended by this document >
This document also defines the following additional error codes and error descriptions:
< new error codes >
the current text in section 5.2.2 sounds like even existing error codes invalid_scope, invalid_client etc are defined from scratch by this specification. it would be much cleaner to differentiate which error codes are new and which ones are extending the existing ones. a structure like below: