Hi Mike, On Oct 14, 2011, at 6:42 PM, Mike Jones wrote:
> 2. Scope – I was planning to allow a broader set of ASCII characters than > the “token” set, as these characters are inadequate for the use of URIs/URLs > as scope elements. In particular, scope elements need to permit the full > sets of “reserved” and “unreserved” characters in RFC 3986. The draft I am > working on will say that scope is a space separated set of elements, where > the elements consist of one or more characters from the union of the > “reserved” and “unreserved” sets. Wouldn't it be more useful to say that you either want some plaintext values for the scope or URLs but not both? Also, if you want to introduce "standardized" (or reserved values) then you have to a) specify them now (with no ability to change them), or b) prefix them. Ciao Hannes _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
