+1, I'll change "formal" to "full" throughout the code. I don't think it was exposed to the user anywhere obvious.
Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:registry-dev- > [EMAIL PROTECTED] On Behalf Of Glen Daniels > Sent: Monday, December 17, 2007 10:44 AM > To: [email protected] > Subject: Re: [mashup-dev] RE: [Registry-dev] svn commit r11161 - > trunk/registry/modules/core/src/main/java/org/wso2/registry/jdbc > > Jonathan Marsh wrote: > > I agree it's harsh, but if I search for services by John Smith I > > might get back a mix of services by upstanding citizen jsmith (John > > Smith) and convicted felon johns (John Smith). They currently all > > look like they have the same author. > > See below, but I definitely would -1 any attempt to require uniqueness > across "human" names. > > > Another approach is to make both the formal name and the username > > more visible, for instance by adding the username alongside the other > > name in mashup lists ala email: > > > > John Smith (jsmith) > > Or the other way around "jsmith (John Smith)" to make it crystal clear > that the username is paramount. > > > I think I'll do that for now rather than yank formal names... > > +1 > > Also, "Formal" name seems a bit of a strange term, since it has > connotations of both "this is the canonical/legal name" (as in formal > declarations) and "this is very stuffy-uppity" (as in a formal dance). > "Full name" seems to be what a lot of sites use for this. > > --Glen > > _______________________________________________ > Registry-dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/registry-dev _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
