grouping attributes in consent UI

[Rod Widdowson]

> My thinking is that it's of a piece with the overall problem of pulling out more of the attribute 
> "metadata" we want to have, for want of a
> better name call it an Attribute Service, and getting away from the "inline" configuration we have today.

Somewhat off topic for this thread, but absolutely on-topic for V4:  I'm keen to see this develop.  It starts (for me) with
encoding, but you then rapidly fall into the space-time-vortex that is the difference between Attributes from a DataConnector and
Attributes from AttributeDefinitions.  

Having display information in there to (to an arbitrary granularity) is another dimension that hadn't occurred to me.  Are there
other dimensions I've missed?  Filtering?

Also one you drop down from 100kft its not obvious what the dictionary looks like - I could postulate a few things but I'm unsure.
I suspect that's because I'm not Radius-aware....

I guess that the end goal is that the deployer "just" defines a few attributes with well known names and the Federation supplied
information controls the rest (encoding, display, filtering and so on). 

But in a way that allows for easy over-ride and local control.

/R