On 8/17/10 4:47 PM, "Michael Schlenker" <schl...@uni-oldenburg.de> wrote:
> Am 18.08.2010 um 01:16 schrieb Bryon Ruxton:
>
>> Sorry if lacked clarification,
>> I was referring to the "current" residents names (as capitalized), NOT the
>> new display name which will become the person's username as I understand it.
>>
>> Because of the added flexibility with Display Names, I see it a good
>> opportunity to enforce the official First and Last name both capitalized
>> when shown and possibly clean up the legacy database of "First & Last"
>> names.
>
> This will break content if it hits the scripting layer. E.g. i have some
> scripts
> that derive things from the current username (including upper/lowercase
> distinction),
> and if you simply capitalized names it would break. Same with the
> aformentioned scripted access control lists.
First and Last being unique I'd advise you lowercase them anyway before
processing as a general practice. It allows for partial names, typos, better
search etc...
>>
>> i.e. Someone named currently named "iama Linden" would be changed
>> automatically to Iama Linden as his display name which he can change to
>> lower case via his display name box he chooses so, like dahlia here does.
>>
>> Even if that was to apply to future usernames "when first chosen".
>> You could very well enforce a first capital and still allow for lowercase
>> display names after that, or even have a checkbox to prevent the automatic
>> JavaScript capitalization at registration. But it would fair to say that
>> lack of fist name capitalization due to users omission is much more common
>> than a deliberate intent coming from the user. So I view "initial
>> capitalization" as a default setting for that reason.
>>
>> And 2. you should also prevent anyone to use a display name baring the name
>> of an existing username in my opinion.
>
> NO. That would limit the usefulness for some kind of RP for sure. Might be
> okay if it was
> not allowed for IM or if IM always showed the old style name too.
It surely needs to be clearly identified if there are no restrictions at
all.
E.g. I don't mind if you use: "Philip Linden's Baby", "Philip Linden 1",
"Philip Linden©" or "«Philip Linden»" etc.. but not "Philip Linden". A 100%
match of the name (case insensitive) and even perhaps groups name should be
prevented for the best. As I interpret it you cannot use "Georges Clooney"
as display name unless perhaps you real name is indeed Georges Clooney, that
would be in breach of the rules. So is "Coca Cola" ("Cola Cola Fan" being
acceptable)
Rules being: When selecting a name, do not choose one that:
* violates a celebrity¹s right in their name, a trademarked brand name, or
any copyright or intellectual property right.
* deceives others regarding your identity or affiliation; or
* is vulgar, offensive, hateful or harassing.
I already see a lot of abuse reports claiming breach of the Display Name
rules should there be no preemptive enforcement. I think the one I am
suggesting is a minimum prevention and fits along those principles.
At LL's discretion to assess its merits against the projected caveats and
name confusions issues they'll have to deal with.
> And maybe you noticed that lowercase/uppercase transformation is not a
> lossless operation
> (okay, might be due to the restrictions on SL firstnames, but in general its a
> lossy operation).
> Michael
>
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
