[OpenID-specs-EAP] URI v. string for acr values?

[Mike Schwartz]

Yeah, I guess...

If you look at Google's API scopes, they are using URI's (except for 
OIDC scopes):
   
https://developers.google.com/identity/protocols/googlescopes?linkId=17886206

Also, UMA uses a URI for the scopes it defines.

Maybe it's not necessary. But on the other hand, maybe using a URI will 
encourage others to do so.

I don't have a strong opinion, but I think it's worth posing the 
question...

- Mike



On 2016-08-08 14:10, Dominick Baier wrote:
> Sorry, that's xml namespaces and ws* all over.
> 
> Sent from my iPad
> 
>> On 08 Aug 2016, at 20:06, Mike Schwartz <mike at gluu.org> wrote:
>> 
>> 
>> I'm wondering if the acr's might be better as URI's in the openid.net 
>> domain?
>> 
>> Maybe something like "https://openid.net/connect/acrs/phr"
>> 
>> Wouldn't it make the origin of these acr's a little more clear, and 
>> reduce the risk of collision?
>> 
>> - Mike
>> 
>> -------------------------------------
>> Michael Schwartz
>> Gluu
>> http://gluu.org
>> 
>> _______________________________________________
>> Openid-specs-eap mailing list
>> Openid-specs-eap at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-eap