<br><br><div class="gmail_quote">On Fri, Apr 3, 2009 at 5:35 PM, SitG Admin <span dir="ltr"><<a href="mailto:sysadmin@shadowsinthegarden.com">sysadmin@shadowsinthegarden.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
An alternative view to this is that front-loading the user account creation experience with requests to disclose a lot of information can lead to sending the user away. A better approach is for incremental disclosure, where requests for the user to disclose specific bits of information appear in the context of the stated need.<br>
</blockquote>
<br></div>
True . . . so the RP just needs some way of figuring out which feature the user was interested on, to send them to their OP with the corresponding attribute(s) marked as "required".</blockquote><div><br>Yes. If RPs do a good job of inferring the user's intent before sending them to the OP (the OP certainly has no ability to accomplish that) they can craft their requests such that there is a very high likelihood that the user will say 'yes' to everything requested. That will result in the maximum value being obtained from using AX to start with.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
-Shade<br>
</blockquote></div><br><br clear="all"><br>-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>