Handling a multi-value attribute question

[Peter Schober]

* David Bantz <dabantz at alaska.edu> [2012-12-06 19:11]:
> A service that makes the simplifying assumption that any value of
> eduPerson or of givenName can be used as though it were the only
> value is imposing a constraint that is not part of the attribute
> definition.

Well, given the other constraints that's simply unavoidable.
(You get several values and can only make use of one in the
application, sensibly. You're lacking any qualifiying information
which to use and cannot even rely on order.)
-peter