<div>My +1 is really more like a +0.1 - not pushing for a suite name, just want to avoid confusion if we do decide to name the suite.</div><div><br></div><div>Nat, I'm fine with just defining the four endpoints you mentioned in core -- that helps with the confusion I initially had, which was that I had heard John Bradley refer to the Introspection Endpoint verbally as the "Token Introspection Endpoint", and had started to wonder whether in fact the Token Endpoint and Token Introspection Endpoint were actually the same thing (by the time I finished reading all the documents I think the separate nature of the endpoints was made clear).<br>
<br><div class="gmail_quote">On Tue, Jul 12, 2011 at 12:25 PM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Breno, <br><br><div class="gmail_quote"><div class="im">On Wed, Jul 13, 2011 at 2:45 AM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com" target="_blank">breno@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div><br>
>><br>
>> In general, I agree that the short names are confusing for beginners or<br>
>> people trying to discern meaning only from code. I found the specs very<br>
>> easy to read and understand, but tough to know whether some pieces were<br>
>> required to be developed or just optional.<br>
>> For example: Core section 4 (Serialization) states that messages can be<br>
>> serialized in either format (JSON or Query String) unless expressly<br>
>> forbidden on a per-message basis -- but nothing in section 4 answers the<br>
>> question of whether or not an implementer is required to support both<br>
>> serializations to be conformant, or whether they can only support one.<br>
><br>
> Actually, "core", which is likely to be called something like "Connect<br>
> Messages" are just listing all the possible variations on messages as a<br>
> reference, so it does not say anything about conformance. It should be<br>
> defined in the "Bindings" such as "OpenID Connect (was: HTTP Redirect<br>
> Binding)".<br>
>><br>
>> Another example is ID Token - it appeared in the session and userinfo<br>
>> specs but not in the core, http binding, or framework spec (unless I missed<br>
>> it).<br>
><br>
> Things were separated out due to some request from the community member, but<br>
> it proves to be more confusing than not. I suggest re-combining "core" and<br>
> "framework" and call it "Connect Messages".<br>
<br>
</div></div>I don't think there's agreement in our group to do so. All the<br></blockquote><div><br></div></div><div>No. That is why I have not touch the specs in this respect yet. </div><div>As far as I remember, it was the decision of the WG to wait the reorganization until we finish the current pass of the spec review. </div>
<div>The files that I sent earlier and is attaching now has not done anything wrt this. </div><div>(Just to make note of, I have not done any edit wrt the comment you made as George is working on it. )</div><div><br></div>
<div>However, it does not preclude a parallel discussion of the possible reorganization. </div><div>Current state is that George suggested a reorganization, and Pam, John, Johnny, and me +1ed. </div>
<div>Pam further suggested to call the entire suite as Framework, and Johnny +1ed, but Tony -1ed. </div><div class="im"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
feedback we get from developers is contrary to this.<br></blockquote><div><br></div></div><div>So they like the current organization? </div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The reason things are confusing right now has to do with the fact that<br>
the spec has been refactored many times and the writing did not keep<br>
up well. We need to fix the writing, not merge specs when we have<br>
evidence it will be damaging to the message of<br>
simplicity+extensibility we want to convey.<br></blockquote><div><br></div></div><div>Could you kindly explain the evidence so that I can understand better? </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div><br>
--<br>
</div></div><font color="#888888">--Breno</font></blockquote></div><br><font color="#888888">-- <br></font><div><div></div><div class="h5">Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
<a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><span style="font-family:'Lucida Grande', Tahoma, Arial, Verdana, sans-serif;font-size:10px;color:rgb(42, 42, 42)"><font color="#343634" face="Tahoma" style="color:rgb(52, 54, 52);font-size:12px"><strong><span>Pamela Dingle</span></strong> | <span>Sr. Technical Architect</span></font><br>
<font face="Arial" style="font-size:11px"><font color="#343634" face="Tahoma"><strong>Ping</strong></font><font color="#E71939" face="Tahoma"><strong>Identity</strong></font> | <a href="http://www.pingidentity.com" target="_blank">www.pingidentity.com</a><br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br><font color="#005568"><strong>O:</strong></font> <font color="#343634"><span>303-999-5890</span></font> <font color="#005568"><strong>M:</strong></font> <font color="#343634"><span>303-999-5890</span></font><br>
<font color="#005568"><strong>Email:</strong></font> <span><a href="mailto:pdingle@pingidentity.com" target="_blank">pdingle@pingidentity.com</a></span><br>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
<table cellpadding="0" cellspacing="0"><tbody><tr valign="top"><td nowrap><div style="float:left"><font face="Arial" style="font-size:11px"><font color="#005568"><strong>Connect with Ping</strong></font><br><font color="#000000">Twitter: @pingidentity</font><br>
<font color="#000000">LinkedIn Group: Ping's Identity Cloud</font> <br><font color="#000000">Facebook.com/pingidentitypage</font></font></div></td><td nowrap><div style="margin-left:20px"><font face="Arial" style="font-size:11px"><font color="#005568"><strong><span>Connect with me</span></strong></font><br>
<font color="#000000"><span>Twitter: @pamelarosiedee</span></font><br><font color="#000000"><span></span></font></font></div></td></tr></tbody></table></font></span><br>
</div>