Offer help with sreg + 3 AX type URI format interop

[http://blog.nerdbank.net/]

RPs currently have an awful task of having to do the grunt work of deciding whether to send an Sreg or an AX request for attributes, and which of the 3 AX attribute Type URI formats to use for a particular OP. DotNetOpenAuth should offer help in this area.

OPs could use some help as well, as they might receive any of four types (Sreg + 3 AX) of attribute requests.

The design of the solution will center on Sreg. A plug-in OpenID "behavior" class will make all attribute extensions and formats look like Sreg at the host level, but underneath it will play all tricks possible to make sure the extension is wire compatible with the remote party.

This will automatically make OpenIdTextBox and the other controls Just Work with various OPs if the behavior is turned on because they use Sreg, which will automatically be changed to AX for the OPs that may need it.

[http://blog.nerdbank.net/]

One way to implement this that would also benefit MVC sites is to have an extension method that spreads the AX well-known attributes to include the myopenid-style attributes and the sreg ones. Then another method to consolidate the many forms into one, so that host sites just have one consistent format to deal with.

[http://blog.nerdbank.net/]

Feature complete... just writing a few more tests.

[http://blog.nerdbank.net/]

master 79b2adcec5