Hey,
We have a use case for a scope that's more fine-grained/flexible than what you could explain in a set of space-delimited keywords. We would like to encode things like the precision with which some data can be accessed, and the scope sounds like the reasonable place to do that. Of course we can cheat by encoding eg JSON and escaping all the spaces to "\u0020" but that seems like an ugly workaround. Considering the spec says that the actual values of a scope are determined by the server, why does it dictate the *format*? Thanks in advance Laurens _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
