[Openid-specs-ab] Claims Registry

Mike Jones Michael.Jones at microsoft.com
Wed Aug 13 00:48:39 UTC 2014


The intent is that it will used to build up a standard claims vocabulary for JWT claims.  However, the registry won’t actually come into existence until the JWT spec becomes an RFC, which could be up to a year away.

                                                                Best wishes,
                                                                -- Mike

From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of Glenn Grant
Sent: Tuesday, August 12, 2014 5:47 PM
To: openid-specs-ab at lists.openid.net
Subject: [Openid-specs-ab] Claims Registry

Heya,

I've been pondering over the Claims Registry (http://openid.net/specs/openid-connect-core-1_0.html#ClaimsRegistry , http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-25#section-10.1) a bit lately. In particular, what's the general consensus on how this will be used/grow?

Currently there seems to be a lot of fragmentation around a 'common language' for things (eg. firstName, address, etc) for personal data stores and interoperability among different service. Arguably I could see the ClaimsRegistry (or similar) growing to fulfill that need (if people were to adopt it, which, being part of a standard could be easier)

Is there somewhere currently to see an aggregated view of what exists in the registry? (without digging through individual specs)

Cheers,

Glenn 'devalias' Grant

White Label Personal Clouds / Welcomer
___________________________________________________
glenn at welcomer.me<mailto:glenn at welcomer.me>
LinkedIn<http://au.linkedin.com/in/glenndevaliasgrant>  |  Twitter<http://twitter.com/_devalias>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20140813/4c5667b6/attachment-0001.html>


More information about the Openid-specs-ab mailing list