I like the idea of *not* using the work 'framework' for any specific document. That way the whole suite could be called a framework or any other analogous term without confusion.<div><br></div><div>I've attached a simple initial map showing George's proposed naming - I made several assumptions that could likely be incorrect, let me know what's inaccurate.</div>
<div><ul><li>I put the JW* series outside the OpenID Connect realm, as I believe they are dependencies but not direct members</li><li>I added a separate dynamic client registration box, because I wasn't sure if George's proposal simply missed that doc or if the plan was to roll the doc into one of the other proposed titles</li>
</ul><div>The nice thing about this set is that it the additional value props of OpenID Connect are spelled right out in the titles. If you don't want to do the additional add-on in the title, just don't read/implement that doc.</div>
</div><div><br></div><div>I'm going to use this map as a placeholder in the summary doc for the real thing, to be updated when the decision is made, so style suggestions are also welcome :)</div><div><br></div><div><br>
<div class="gmail_quote">On Tue, Jul 12, 2011 at 10:06 AM, John Bradley <span dir="ltr"><<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">That is sounding better.<div><div></div><div class="h5"><div><br><div><div>On 2011-07-12, at 9:39 AM, Nat Sakimura wrote:</div><br><blockquote type="cite">To me, it sounds like a good idea. (Ok. I am not a marketing type so I may be completely off...) <div>
<br></div><div>Let us see what the community think. </div><div><br></div><div>=nat<br><br><div class="gmail_quote">On Tue, Jul 12, 2011 at 10:21 PM, George Fletcher <span dir="ltr"><<a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">I was wondering about
something like...<br>
<br>
OpenID Connect (HTTP Binding with normative references to OpenID
Connect Messages)<br>
OpenID Connect Session Management (with normative references to
OpenID Connect Messages)<br>
OpenID Connect Messages (contains all abstract messages both Basic
and Advanced)<br>
OpenID Discovery<br>
<br>
OpenID UserInfo <br>
<br>
If we need other profiles we can add them. Not sure if this breaks
the desired modularity, but from a developer perspective would be
easier for me to follow. I know what doc to start with and it can
reference another doc to provide message details as necessary.<br>
<br>
Thanks,<br>
George<br>
</font><div><div></div><div><br>
On 7/11/11 6:23 PM, Nat Sakimura wrote:
</div></div><blockquote type="cite"><div><div></div><div><br>
<br>
<div class="gmail_quote">On Tue, Jul 12, 2011 at 5:05 AM, Johnny
Bufu <span dir="ltr"><<a href="mailto:jbufu@janrain.com" target="_blank">jbufu@janrain.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 11-07-11 10:16 AM, Nat Sakimura wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. We should make sure to place HTTP Redirect Binding as
the Center Piece.<br>
This actually is the confusion that even Breno was
falling into. He<br>
was thinking that Core was something to be implemented.<br>
It is not. It is the HTTP Redirect Binding that the
developers<br>
should read. We may want to rename it to something more<br>
attractive and feel as the main spec. (Perhaps rename
core as<br>
"Messages" and let the HTTP Binding assume the name<br>
"Core" etc.?)<br>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>Just for the sake of the call: </div>
<div><br>
</div>
<div>Mike's suggestion: </div>
<div><br>
</div>
<div><span style="white-space:pre-wrap"> </span>Core
Messages</div>
<div><span style="white-space:pre-wrap"> </span>Core
Bindings</div>
<div><span style="white-space:pre-wrap"> </span>Framework
Messages</div>
<div><span style="white-space:pre-wrap"> </span>Framework
Bindings</div>
<div><br>
</div>
<div>My suggestions are </div>
<div><br>
</div>
<div> Basic Messages (for Connect)</div>
<div> Advanced Messages (for Connect)</div>
<div> Basic (HTTP bindings)</div>
<div> Advanced</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
<br>
</div>
I too feel that the current number of separate documents makes
it harder to get the big picture, even though I like modular
specs. I guess the modularization is not laid out in a way
that's easy to get. For example:<br>
<br>
- The separation between what is an "abstract" message and
what a binding is required/allowed to define is not very
clear.<br>
<br>
- ID Tokens are needed, one way or another (JWT encoded or
not) to complete a full OpenID-Connect authentication. I'd
rather learn about them from Core.<br>
<br>
- UserInfo endpoint seems to be covered by both UserInfo and
Framework specs.
<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2. Short names are unpopular.<br>
</blockquote>
</div>
[...]
<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Here are my suggestions:<br>
inf -> userinfo<br>
idt -> id_token<br>
clm -> claims<br>
fmt -> format<br>
mxa -> max_age<br>
eaa -> iso29115<br>
nor -> unsigned<br>
sig -> signed<br>
enc -> encrypted<br>
aat -> auth_time<br>
loc -> locale<br>
opt -> optional<br>
</blockquote>
<br>
</div>
+1 if there's no clear technical reason that prevents using
these slightly longer names.<br>
<font color="#888888">
<br>
Johnny<br>
</font></blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
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>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Openid-specs-ab mailing list
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Chief Architect AIM: gffletch
Identity Services Engineering Work: <a href="mailto:george.fletcher@teamaol.com" target="_blank">george.fletcher@teamaol.com</a>
AOL Inc. Home: <a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a>
Mobile: <a href="tel:%2B1-703-462-3494" value="+17034623494" target="_blank">+1-703-462-3494</a> Blog: <a href="http://practicalid.blogspot.com/" target="_blank">http://practicalid.blogspot.com</a>
Office: <a href="tel:%2B1-703-265-2544" value="+17032652544" target="_blank">+1-703-265-2544</a> Twitter: <a href="http://twitter.com/gffletch" target="_blank">http://twitter.com/gffletch</a>
</pre>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>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>
_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br></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>