Hello everyone, my name is Steve Mekkelsen Madden, or Steven Michael Mekkelsen Madden if you want my full legal name. :-) So why am I being formal here of all places? The answer is quite simple actually, I am creating this blog so that I can get all my fellow software engineers comments and opinions on a very real life software problem; the "name" fields and then make a decision to change the world, or at least a standard anyways.

As you can probably surmise, this subject has to do with changing some of our standards and ways we view/think about what we set name type fields to be in our software applications. Are we using a 1970's, a 21st Century standard or something in between them? I've spent a considerable amount of time fighting with organizations to support our name in their business applications, only to be told, sorry Steve, we just don't have enough spaces for your last name or we can't put a space in a last name field. This is just one sad story after another and it is now time that "we" set a new Global Software Standard for Names!

User Name Standards Proposal to Association of Software Professionals


Overview: When the computing era began to hit the retail markets and consumers back in the 1970's, disk space was at a premium cost for each byte/character used. As a result, some field names were set extremely short like AN (account name), or AcctN (account name). There were also restrictions on the number of bytes allocated for the values of these fields and hence a name field could be as short as 15 characters for both the first and last names.

At the time, world travel was still in its infancy and our standards were not compromised. When all the new airlines came in and started offering round trip flights to most parts of the world, this also led the U.S. into a new era of foreigners coming to the U.S. and staying either on VISA's or as new citizens. So what's the issue you may ask? Well first, let's think about what our most common names were at the time. We didn't have many personal computers in the market place, so we didn't have to worry about how long names were. But even in the 1970's, a name like Steve Madden, Tom Jones, Albert Einstein and Bill Cosby would fit in our 15 character values for whatever software may have been available at that time. Unfortunately, other countries citizens names didn't quite follow our standards because their culture included family names and some on both spouses families which makes for a very long name.

So flash forward to today where personal computers are in almost every household in the U.S. and abroad. Now the standard short 15 character name field becomes a serious limitation to the software. Now let's consider businesses and what services they have to offer for their customers. There are fields like account_name, customer_name, legal_name, billing_name, mailing_name, etc. There are many fields which attempt to cover what is needed for today's marketplace. Unfortunately, we still fall short even with the field names and values. With "disk cost" being at its all time low, we still as software developers, restrict the amount of spaces to be used and what is worse, what the default validation on those field values impose. Some software restrict the use of dashes "-" or spaces in a name field value. Well, as you may or may not know, the name field values can contain spaces and dashes in them and are perfectly legal. Did you know that you can go to a court in the U.S. and request a name change to virtually anything you want (within reason, and not to escape debts of any kind)? The judge will speak with you during the name change process and approve or deny the request. This is very common when citizens get married and want to include their name in some way or for other reasons. If our software cannot accommodate these scenarios, then we have failed as software professionals.

An example is the use of my legal name "Steven Michael Mekkelsen Madden" where "Steven" is my first name, "Michael" is my middle name and "Mekkelsen Madden" is my last name(s). My maiden name (name prior to marriage or name change) is "Madden". When my wife and I married, I added her last name before my last name and she added my last name after hers resulting in SherriLee Mekkelsen Madden. So that gives me 31 characters for my name and 26 for my wife's. Sounds simple right? Not so! We have issues with State and Local Government Offices, Healthcare Professionals (Insurance, Hospitals, Doctors and Specialists), Utility Companies like Telephone, Cable, Satellite, HVAC's and as well as Department Stores and Banks who provide a credit/debit/store card of some kind where our names just does not fit. Our youngest daughter also has two middle name "Violet Mary" so when she is asked to provide her middle initial she is not happy when the software only allows one middle initial.

That's the overview behind this proposal to correct our series of name issues across all markets and once and for all provide an industry standard for "name" fields and values to support organizations and individuals on a Global Scale! The table below describes each field name, value and validation imposed. Supporting this new standard may require programmatic changes to support increased field widths on a variety of displayed data and/or printed data on forms, pdf files, cards, etc.

		** The Character width can be NO SMALLER than stated **
		** Field Names are not a requirement, only a suggestive representation thereof the actual field name.  **
		** Variants of the same are allowed. **

Personal Name Fields - variants of field names & lengths assumed to support multiples and fieldname restrictions in software. It will be now assumed, any name requiring a legal name or first, middle & last shall be a minimum of 107 characters.

Field Name Characters Description Validation
firstname 35 First Name(s) Allow spaces & dashes
middlename 35 Middle Name(s) Allow spaces & dashes
midinitial 4 Middle Initial(s) - can be more than one middle name No spaces & dashes
lastname 35 Last Name(s) Allow spaces & dashes
legalname 107 Legal Name - includes firstname,middlename & lastname plus two spaces Allow spaces & dashes
maidenname 35 Maiden Name(s) before marriage or name change Allow spaces & dashes
nickname 35 Nick Name - a shorter version of firstname or family name provided. (i.e. Betsy for Elizabeth or Stevie for Steven or Stephen) Allow spaces & dashes
spousefname 35 Spouse First Name(s) Allow spaces & dashes
spousemidname 35 Spouse Middle Name(s) Allow spaces & dashes
spousemidinit 4 Spouse Middle Initial(s) - can be more than one middle name/initial No spaces & dashes
spouselastname 35 Spouse Last Name(s) Allow spaces & dashes
spouselegalname 107 Spouse Legal Name - includes spousefname,spousemidname,spouselastname plus two spaces Allow spaces & dashes
spousemaidenname 35 Spouse Maiden Name(s) before marriage or name change Allow spaces & dashes
spousenickname 35 Spouse Nick Name - a shorter version of firstname or family name provided. (i.e. Betsy for Elizabeth or Stevie for Steven or Stephen) Allow spaces & dashes
parentname 107 Parent's Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes
grparentname 107 Grandparent's Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes
siblingname 107 Sibling's Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes

Commercial Name Fields - variants of field names & lengths assumed to support multiples and fieldname restrictions in software. It will be now assumed, any name requiring a legal name or first, middle & last shall be a minimum of 107 characters.

Field Name Characters Description Validation
accountname 107 Account Name(s) - same as legalname Allow spaces & dashes
billingname 107 Billing Name(s) - same as legalname Allow spaces & dashes
cardholdername 50 Card Holder Name(s) - names to appear on dept store, debit or credit card. May require use of two lines Allow spaces & dashes
clientname 107 Client Name(s) - same as legalname Allow spaces & dashes
customername 107 Customer Name(s) - same as legalname Allow spaces & dashes
shippingname 107 Shipping Name(s) - includes firstname,middlename (optional),lastname plus two spaces; can be different than legalname on account. Allow spaces & dashes
registername 107 Registration Name(s) - same as legalname Allow spaces & dashes
beneficiaryname 107 Beneficiary Full Name(s) - same as legalname Allow spaces & dashes
insuredname 107 Insured Name(s) - same as legalname Allow spaces & dashes
policyholdername 107 Policy Holder Name(s) - includes firstname,middlename,lastname plus two spaces and can be different than legalname on account. Allow spaces & dashes
patientname 107 Patient Name(s) - same as legalname Allow spaces & dashes
subscribername 107 Subscriber Name(s) - includes firstname,middlename (optional),lastname plus two spaces; can be different than legalname on account. Allow spaces & dashes
ownername 107 Owner's Name(s) - same as legalname Allow spaces & dashes
coownername 107 Co-Owner's Name(s) - includes firstname,middlename,lastname plus two spaces; can be legalname or different. Allow spaces & dashes
guardianname 107 Legal Guardian's Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes
sponsorname 107 Sponsor's Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes
billresponsname 107 Billing Responsible Party Name(s) - includes firstname,middlename,lastname plus two spaces Allow spaces & dashes
othername 107 All other names where a legal name of full name is required Allow spaces & dashes


Name Standard Created on June 7, 2013 by Steve Mekkelsen Madden of Madden Software Service
to help support the cause for It's Not Your Name - It's my name, so don't change it! project.