<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Hmm... Behemoth (although very memorable) is not quite the image I would like to portray ;)</div><div><br class="webkit-block-placeholder"></div><div><blockquote type="cite">And speaking frankly, WSF is too unknown to developers to call it "Possum" and just say "yeah, that's the WSF library". Liberty at least has a known name.</blockquote></div><div><br class="webkit-block-placeholder"></div><div>One could use the same argument for naming it Possum. Maybe PossumID.</div><div><br></div><div>Ha-neh-al-enji -- Navajo for "making talk" -- world war II code talkers used it to mean "communication"</div><div><br></div><div>It has a good back story, and we are facilitating private</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>How about "enji" </div><div><br class="webkit-block-placeholder"></div><div>enji-j</div><div>enji-r</div><div>enji-c</div><div>enji-n</div><div><br></div><div>Really the challenge is getting the product in-front of developers, into developers hearts, and living in some serious use cases. There need to be business reasons for developers to get involved. Anyone who is looking around for identity based web services will find liberty and openliberty, and then find Possum/enji/openLiberty/Behemoth/Yeti</div><div><br class="webkit-block-placeholder"></div><div>The identity market is filled with things that have ID/Ident/Open/Identity/Services in their names.</div><div><br></div><div>asa</div><div><br></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><br><div><div>On Feb 26, 2008, at 3:36 PM, Pulkit Singhal wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I agree with Scott about:<br>====<br>WSF is too unknown to developers to call it "Possum" and just say "yeah, that's the WSF library"<br>====<br><br>But just for kicks, in case it ends up flying, I'd like nominate the name: "Behemoth". Yes I understand the connotation about being large and overbearing but I just couldn't keep quiet after reading the discussion ... its been floating around in my head since I started working with web services. Just a pet-peeve feel free to ignore.<br> <br>Cheers!<br><br><div class="gmail_quote">On Tue, Feb 26, 2008 at 10:44 AM, Scott Cantor <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</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 class="Ih2E3d">> OpenLiberty-J sounds good, I also like the uppercase "O" -- makes<br> > it look stronger.<br> <br> </div>That one happened while I wasn't looking, and I tend to interchange them<br> because I like OpenLiberty more than openLiberty.<br> <div class="Ih2E3d"><br> > The differentiation between wsc and wsp is<br> > important, however, as we have discussed many times before, the lines<br> > are very blurry. The tooling that we have done for WSC would be re-<br> > useable for a WSP.<br> <br> </div>Which is why I don't make the distinction. Another example...Axis doesn't<br> come in a SOAP client and server version. It's just different parts of the<br> package.<br> <div class="Ih2E3d"><br> > The only problem is that openLiberty covers more than ID-WSF at then<br> > moment.<br> <br> </div>My scope of ID-WSF is everything Liberty does that's not SAML. Admittedly<br> overly broad. My point is kind of that even if other non-WSF stuff is in the<br> pot, who cares?<br> <div class="Ih2E3d"><br> > org.openliberty.xmltooling<br> > -- where the base package for all of the java objects that represent<br> > the xml elements of the spec currently exist, eg,<br> > org.openliberty.xmltooling.disco<br> <br> </div>Just a personal opinion, but I would have turned it around and put the XML<br> classes inside the disco package.<br> <div class="Ih2E3d"><br> > On the level of documentation, creating clear segregation between<br> > client and server is critical. I imagine this would be done with use<br> > case sample code.<br> <br> </div>Yes, that's a different issue.<br> <div class="Ih2E3d"><br> > Ideally we could get identity into the name in some way, and web<br> > services for that matter. And it should be catchy. OpenLiberty-J is<br> > catchy.<br> <br> </div>Well, it's not super catchy, but it's better than something with WSF in it.<br> You're not talking to somebody in marketing. To me Shibboleth is "catchy"<br> and I've been told it sucks, so...(in fairness I didn't come up with that<br> name either).<br> <div class="Ih2E3d"><br> > Since ID-* is shorthand for ID-WSF, ID-SIS, ID-FF:<br> <br> </div>ID-FF is superseded, and I lump all the rest into ID-WSF, as I said.<br> <br> > idSTAR-J<br> <br> I think I would avoid anything like STAR.<br> <br> > OpenLID-J<br> <br> There was an OpenID competitor called LID, best to avoid that.<br> <br> The basic problem is that there's no catchy name for ID-WSF. Unless you just<br> make up a name that's unrelated, it just doesn't lend itself to anything.<br> And speaking frankly, WSF is too unknown to developers to call it "Possum"<br> and just say "yeah, that's the WSF library". Liberty at least has a known<br> name.<br> <div><div></div><div class="Wj3C7c"><br> -- Scott<br> <br> <br> <br> _______________________________________________<br> Wsf-dev mailing list<br> <a href="mailto:Wsf-dev@lists.openliberty.org">Wsf-dev@lists.openliberty.org</a><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></div></blockquote></div><br><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Wsf-dev mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:Wsf-dev@lists.openliberty.org">Wsf-dev@lists.openliberty.org</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org">http://lists.openliberty.org/mailman/listinfo/wsf-dev_lists.openliberty.org</a></div> </blockquote></div><br></body></html>