> I think so too. But I whould not try to explain a PAU (pluggable
> authentication utility) without to use the word principal. I think
> using the words user or participant for a principal in this case is
> not a good idea.
Perhaps the scope of the PUA can be extended to have a plug-in factory
for User objects, and to make the current User easily available inside
page templates and other presentation code.
People who wish to use the PUA would define their own User class,
which could be as simple as taking the principal id, but would often be
more complex according to the needs of their application.
 Desperately trying to avoid using the term "user" there.
Zope3-dev mailing list