a scripted attribute definition example from the wiki

[Peter Schober]

* Mark K. Miller <max at psu.edu> [2016-07-27 20:47]:
> So, Peter, thank you for the examples (especially if you also
> provided "Varinat 2"!)

I did.  Personally I just found variant 1 (2 attribute definitions,
with dependencies) much cleaner, only requiring minimal scripting: You
just do in code what you specifically want to achieve, without having
to handle the "other" cases, and let dependencies between (themselfs)
simple definitions take care of the rest.
Too bad showcasing that feature comes at a price of introducing
warnings and may potentitially cause unindended behavior (from what
Scott said).

While I find that simple example practically useful myself (either
variant) of course it also has a certain danger of causing changed
ePPN values if one is not careful: By falling back on uid unless ePPN
exists in LDAP the ePPN value will chang to that in LDAP once
someone/something adds an ePPN attribute there that's not identical to
uid + scope. So there are other issues with that approach. As such
other examples should maybe replace those at some point (and examples
should be moved to their own child page).

Anyway, there's now additional text about the warning (and the missing
sourceAttributeID was added), so others shouldn't run into those
issues in the future.
-peter