[OpenID] Configuration file for OpenID libraries?

[SitG Admin]

>proposal tries to introduce a new concept to the existing OpenID
>software stack - a configuration file (in contrast to 'it is up to the
>calling application to make interesting decisions from the data
>provided by OpenID libraries') and thus also change the API a bit.

Alternately - one could give this config file itself the power of a 
proposal, and let it set an optional string that would offer mere 
suggestions* as to what to do with the login. This would still leave 
complete control in the hands of the application calling it, but give 
the OpenID process a way of exporting slightly more information to 
whatever called it.

*Such as,
Action=>Deny
Reason=>Blacklisted
Detail=>Spammer
But of course, other items might be desired later. If the 
config-reading code's place in each library is sufficiently isolated 
(or is the word modular?), such items could be added later on by 
individual programmers, with ease. This would counter any attempt to 
standardize the config-file format, though. Consistency for the specs 
or freedom to tinker?

-Shade