If Phil has the premise correct -- i.e. if all the WSF projects do actually breakdown neatly into Toolkit, AppKit, and ProviderKit -- then how about..<br><br>option A:<br>OpenLiberty TrustFed ToolKit<br>OpenLiberty TrustFed AppKit<br>
OpenLiberty TrustFed ProviderKit<br><br>option B: (I'm just throwing something out there... it seems the heart of WSF is the concept of "my services")<br>OpenLiberty MyServices ToolKit<br>OpenLiberty MyServices AppKit<br>
OpenLiberty MyServices ProviderKit<br><br>option C (already one vote against this from Phil, but let's just keep the options on the table until we get a decision):<br>OpenLiberty OpenWSF ToolKit<br>OpenLiberty OpenWSF AppKit<br>
OpenLiberty OpenWSF ProviderKit<br><br>option D: (noting one vote for this from Phil... maybe)<br>OpenLiberty Panda ToolKit<br>OpenLiberty Panda AppKit<br>OpenLiberty Panda ProviderKit<br><br>option E ??<br><br>But I have a meta-question... who should be making this decision anyway? I think with Sampo, Conor and AOL (presumably George Fletcher) signing CLA's (any day now?) we finally have an official independent group of contributors to take over "governance" of this project. And since this naming does impact the other IGF project we need to add Phil and Prateek to that list. So maybe only Phil, Prateek, Asa, Sampo, Conor, and George need to make this decision? Gentlemen, are we at that point yet?<br>
<br><div>
Brett McDowell | <a href="http://www.projectliberty.org">Liberty Alliance</a> | <a href="http://www.ictprojects.com/Brett_McDowell_LAP.vcf">vCard</a> | <a href="http://www.google.com/calendar/hosted/ictprojects.com/embed?src=brett%40ictprojects.com&ctz=America/New_York">Calendar</a>
</div><br><br><div class="gmail_quote">On Thu, Mar 20, 2008 at 8:06 PM, Asa Hardcastle <<a href="mailto:asa.openliberty@zenn.net">asa.openliberty@zenn.net</a>> 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 style=""><div>So to give others some context: OpenLiberty/J turns out to be a little short sighted. Since OpenLiberty has numerous projects, to which we are now adding regularly, we need to find a name that does not confuse this point. So we are back in the naming game.</div>
<div><br></div><div>It may or may not be useful for us to have a convention across all projects. There is certainly something to be said for continuity. So, any ideas? </div><div><br></div><div>Phil has made it clear that he does not like the idea of using "open" or "liberty" in the names, and has built an argument for this in the email I am responding too.</div>
<div class="Ih2E3d"><div><br></div><div>asa</div><div><br></div><div><br></div><br><div> <span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="">
<div><div>--</div><div>Asa Hardcastle, Technical Lead, openLiberty ID-WSF ClientLib</div><div>Tel: +1.413.429.1044 Skype: subsystem7</div></div></div></span> </div><div><br></div><div><br></div><br></div><div><div><div></div>
<div class="Wj3C7c"><div>On Mar 20, 2008, at 4:53 PM, Phil Hunt wrote:</div><br></div></div><blockquote type="cite"><div><div></div><div class="Wj3C7c"><div style="">Asa,<div><br></div><div>I have copied both lists since this discussion thread applies to both projects.</div>
<div><br></div><div>I think we should avoid the use of Liberty or Open Liberty, or Open. Since the parent organization is OpenLiberty, reusing the name Liberty, OpenLiberty, or even Open in the "product" or "project" name causes repitition. E.g. OpenLiberty OpenWSF seems a little redundant.</div>
<div><br></div><div><div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="">
<span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div>
Looking at the WSF stuff you are building, it is a lot bigger than I first thought. I thought it was just the client! </div><div><br></div><div>Leaving the development language issue aside, it almost looks like you are building a "WSF Toolkit" and re-packing it into a couple of open source products (e.g. WSF Client, WSF Server).</div>
<div><br></div><div>I'd almost go for WSF-J Toolkit (for people re-using the code), WSF-J Client and WSF-J Server for customers deploying as final products.</div><div><br></div><div>That still seems a little dry. Going back to Chuck Mortimore's comment about customers buy houses and not plumbing, I'd look for a higher level name. I'm not sure if this is any better, but how about Trust Fed. So the full name would be something like:</div>
<div>openLiberty TrustFed-J ToolKit</div><div>openLiberty TrustFed-J AppKit</div><div>openLIberty TrustFed-J ProviderKit</div><div><br></div><div>That said, now that I have typed it out, "TrustFed" seems a little dry. I'd still like to see something a little open source like. Project Panda or something goofy like that. ;-)</div>
<div><br></div><div>Phil Hunt</div><div>Oracle</div><br></span></span></span></span></span></span></span></span></div></span> </div><div><br>Begin forwarded message:<br><blockquote type="cite"><div><div style="margin: 0px;">
<font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>From: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">Asa Hardcastle <<a href="mailto:asa.openliberty@zenn.net" target="_blank">asa.openliberty@zenn.net</a>></font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>Date: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">March 20, 2008 12:51:59 PM PDT (CA)</font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>To: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">Phil Hunt <<a href="mailto:phil.hunt@oracle.com" target="_blank">phil.hunt@oracle.com</a>></font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>Cc: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">PRATEEK MISHRA <<a href="mailto:prateek.mishra@oracle.com" target="_blank">prateek.mishra@oracle.com</a>></font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>Subject: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3"><b>Re: Naming of WSF and IGF</b></font></div>
<div style="margin: 0px; min-height: 14px;"><br></div> </div>Good idea Phil. Here is a start from me:<br><br>An open source ID-WSF 2.0 implementation.<br><br>Objectives:<br><span style="white-space: pre;"> </span>* a complete XML tooling of the entire ID-WSF 2.0 specifications including ID-SIS<br>
<span style="white-space: pre;"> </span>* a client library that enables any application to easily take part in an existing ID-WSF environment<br><span style="white-space: pre;"> </span>* a basic ID-WSF WSP along with libraries that are the basis for creating new ID-WSF services (Conor's work, Sampo's work)<br>
<span style="white-space: pre;"> </span>* a pattern that enables the establishment of an ID-SIS based or ID-WSF based service clients<br><span style="white-space: pre;"> </span>* providing multiple software language versions of the above (to date we have java WSP, java WSC client lib, C based WSP and WSC)<br>
<span style="white-space: pre;"> </span>* sample service and service consumer applications<br><span style="white-space: pre;"> </span>* a running and available ID-WSF environment for the purposes of learning and testing<br>
<br>That said, I'd like to bring the naming discussion back onto the wsf list.<br><br>Could the two of you join the id-wsf list temporarily so we can do this together?<br><br><a href="http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org" target="_blank">http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org</a><br>
<br>Maybe the use of "Liberty" could work:<br><br>LibertyIGF<br>LibertyWSF<br><br>LFrameIGF/J<br>LFrameWSF/J<br><br><br>talk soon,<br><br>asa<br><br>--<br>Asa Hardcastle, Technical Lead, openLiberty ID-WSF ClientLib<br>
Tel: +1.413.429.1044 Skype: subsystem7<br><br>On Mar 20, 2008, at 11:46 AM, Phil Hunt wrote:<br><br><blockquote type="cite">I've been thinking about this naming business. Before we name something, it would be nice to describe what are the "products" we are building in open source.<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">For example, my understanding is that you are building the libraries a RP can use to participate in an ID-WSF system correct? Or better, how would you describe it.<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">For my part, in order to demonstrate the use of IGF, I actually have to create, and then use declarations across a set of protocols. So I'm building an attribute services API kinda like JNDI or JDBC that allows the developers to access data. However because of the benefits of pre-declaration, we can leave configuration out of the application code. So probably the key cool benefit of the new API is abstraction. So if I were to describe the IGF Attr Svc API as a product I would say it:<br>
</blockquote><blockquote type="cite">* An API using layered architecture that allowing applications to access data via multiple protocols (LDAP, SAML, ID-WSF, WS-Fed, etc) without having to set special parameters for those protocol implementations at compile time. Individual protocols are configured exclusively at deployment time.<br>
</blockquote><blockquote type="cite">* Allows use of standardized and industry vertical schemas<br></blockquote><blockquote type="cite">* Declarative API allows service providers to understand data and transaction requirements of an application -- a very generic client WSDL if you like.<br>
</blockquote><blockquote type="cite">* Declarative API allows for easier Privacy Impact Assessments.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We could also run through some other thought exercises...but starting with the qualities of our products might be a good place.<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Phil Hunt<br></blockquote><blockquote type="cite">Oracle<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote>
<br></blockquote></div><br></div></div></div></div>_______________________________________________<br>Wsf-dev mailing list<br><a href="mailto:Wsf-dev@lists.openliberty.org" target="_blank">Wsf-dev@lists.openliberty.org</a><div class="Ih2E3d">
<br><a href="http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org" target="_blank">http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org</a><br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Igf-dev mailing list<br>
<a href="mailto:Igf-dev@lists.openliberty.org">Igf-dev@lists.openliberty.org</a><br>
<a href="http://lists.openliberty.org/mailman/listinfo/igf-dev_lists.openliberty.org" target="_blank">http://lists.openliberty.org/mailman/listinfo/igf-dev_lists.openliberty.org</a><br>
<br></blockquote></div><br>