Building a composite attribute from sets of attributes

[Rod Widdowson]

> Correct me if I'm wrong, but the IdP's resolver groups all found
> attribute values without any particular ordering guarantee. 

Absolutely not.  AttributeValues ordering within an Attribute is guaranteed, this is required to make templating make sense.  By extension this is why we have Null attribute value types. 

 In V4 we have tightened things up to that the ordering is embedded in the API contract (which is a pompouse way of saying that I replaced Collection<Value> with list<Value>.

The ordering *does* break down after filtering.

> Moreover,
> LDAP doesn't provide an ordering on returned attribute values. 

That’s 'unfortunate'...