<html><body bgcolor="#FFFFFF"><div>CX does not and cannot carry information from multiple users. </div><div><br></div><div>The information model deals exclusively around a single subject. </div><div><br>=nat<span class="Apple-style-span" style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.231373); -webkit-composition-frame-color: rgba(77, 128, 180, 0.231373); ">@TOKYO via iPhone</span></div><div><br>On 2009/02/04, at 7:50, Dick Hardt <<a href="mailto:Dick.Hardt@microsoft.com">Dick.Hardt@microsoft.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Thanks for the feedback Breno!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Nat: can you provide some illumination? I see that CX would define
attribute types to be carried in AX. I’m confused about the scenario where
information from multiple users would be transmitted as that implies that the
protocol no longer is dealing with a single subject.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">-Dick <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Breno de Medeiros
[<a href="mailto:breno@google.com">mailto:breno@google.com</a>] <br>
<b>Sent:</b> Tuesday, February 03, 2009 2:39 PM<br>
<b>To:</b> Dick Hardt<br>
<b>Cc:</b> <a href="mailto:david@sixapart.com">david@sixapart.com</a>; Allen Tom; Martin Atkins; Nat Sakimura; OpenID
Specs Mailing List<br>
<b>Subject:</b> Re: Suggested scoping for AX 2.0 WG<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Feb 3, 2009 at 2:19 PM, Dick Hardt <<a href="mailto:Dick.Hardt@microsoft.com"><a href="mailto:Dick.Hardt@microsoft.com">Dick.Hardt@microsoft.com</a></a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">1) I'd prefer to NOT include SREG in the work, but am ok
with it being in if the scope is really to clarify issues in SREG and add
language directing people to AX. Anyone else have a strong opinion either way?
(SREG included in this WG or in a different one?)<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
I'm ok either way. <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
<br>
2) In the Scope section, I feel strongly that bulk exchange of attributes about
multiple users is out of scope. It is a very different design pattern then what
AX does now. I have not seen the background on why this is in scope, so perhaps
I can have a different view if someone cares to enlighten me.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><br>
When Nat Sakimura wrote the contract exchange CX proposal, he included scope
for exchanging validation/metadata about attributes, and it was felt that it
should belong here. CX also needs this bulk exchange functionality and again
because it pertained to attributes, it was believed that it would better fit
here.<br>
<br>
The advantage of keeping it in this WG is that we make sure that different
approaches to handling exchange of user attributes are viewed by the same
people, even if it ends up in a separate mini-spec.<br>
<br>
The counter-argument is that most members of this WG are not interested
primarily in this functionality, and it may distract both efforts (CX and AX),
and that AX is unlikely to directly support anything along these lines.<br>
<br>
<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<span style="color:#888888"><br>
-- Dick<br>
</span><br>
PS: please use my <a href="http://microsoft.com" target="_blank">microsoft.com</a>
address for any specs discussions.<o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><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)<o:p></o:p></p>
</div>
</div></blockquote></body></html>