meta attributes (was: IdPv3 - eduPersonTargetedID - How to define and release this attribute?)

Michael A Grady mgrady at
Mon Apr 4 18:31:02 EDT 2016

> On Apr 4, 2016, at 4:31 PM, Nate Klingenstein <nate.klingenstein at> wrote:
> If anyone tries to tell me that Google Analytics or anything else is “one line of code” ever again, I’m going to come down with the mumps too.  1600 characters of minified Javascript is more of a one liner than one line.
> I would still vote in favor of URL-based attribute names as a work stream, though.  If I’m going to make bad suggestions, they’re at least consistently so.

I've never liked the OID names, although I understand why they were chosen -- unambiguous, and to minimize "naming wars", but I really think it was so everyone would equally dislike the naming. :-) I'm all in favor of URL names, have used them for newly defined attributes when I have the choice. On the other hand, with so much existing config using the current OID names, it seems ripe for more confusion to have "yet another name" for our current crop of attributes.

Michael A. Grady
IAM Architect, Unicon, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <>

More information about the users mailing list